Bounty read API

The current Rust API provides read-only access to bounty-engine proposal and evaluation state. It is useful for operations dashboards and services that need a bounded HTTP interface instead of reading engine state files directly.

List proposals

GET /v1/bounty-proposals?limit=25&offset=0

The implementation defaults limit to 25, clamps it between 1 and 100, and defaults offset to 0. For a local process using the default bind:

curl -s 'http://127.0.0.1:46331/v1/bounty-proposals?limit=25&offset=0'

Use the deployed gateway URL when the service sits behind a reverse proxy or authenticated edge.

List evaluations

GET /v1/bounty-evaluations?limit=25&offset=0

curl -s 'http://127.0.0.1:46331/v1/bounty-evaluations?limit=50&offset=0'

The same pagination bounds apply.

Health

GET /health

The health handler attempts to read configured bounty state, so it checks more than whether the HTTP server is accepting connections. If state is unavailable, the service returns 503 with:

{
  "error": {
    "code": "bounty_state_unavailable"
  }
}

A load balancer or process monitor should treat that as unhealthy.

Client pagination

A client can advance offset until a returned page contains fewer records than the requested limit. Adapt the exact collection field to the response type in the deployed bounty_api model.

async function readPage(path: string, limit = 100, offset = 0) {
  const url = new URL(path, API_BASE_URL);
  url.searchParams.set("limit", String(limit));
  url.searchParams.set("offset", String(offset));

  const response = await fetch(url);
  if (!response.ok) throw await toApiError(response);
  return response.json();
}

Read-only means read-only

The router explicitly rejects unsupported mutation methods. Do not build an administration client around an undocumented POST request. Bounty creation, claim, approval and settlement belong to their authorized engine and protocol paths.

Operations use case

An internal dashboard can read evaluations, group them by trigger class, show proposals awaiting funding and link each record back to the relevant Capsule. It can remain read-only while higher-risk mutations stay behind separate authority. That boundary reduces the blast radius of a public or broadly accessible monitoring interface.

Start Here

Build Your First App

Network

Identity & Roles

Capsules

Evidence

Verification

Provenance

PRESS Economy

Bounties

Data Model

API

RPC

PressKey

SDK & Integration

Operations & Security

Reference

Bounty Read API

Bounty read API

List proposals

List evaluations

Health

Read-only means read-only

Operations use case

​Bounty read API

​List proposals

​List evaluations

​Health

​Client pagination

​Read-only means read-only

​Operations use case

Bounty read API

List proposals

List evaluations

Health

Client pagination

Read-only means read-only

Operations use case