# Bounty Engineer Agent Run Ledger

> Bounty Engineer Agent Run Ledger is a paid API for AI agents from bounty-engineer-x402-prod.onrender.com, paid per call via x402, $0.005/call, status unknown (last checked 2026-10-10).

Append, checkpoint, or read structured state events for an autonomous agent run, enabling durable in-progress state tracking across agent execution sessions.

## Facts

- Endpoint: POST https://bounty-engineer-x402-prod.onrender.com/v1/run-ledger?utm_source=zero.xyz
- Price: $0.005/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-10
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/bounty-engineer-agent-run-ledger-bbef39ff
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_84MhEEjiG47reAr4ykh51

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability bounty-engineer-agent-run-ledger-bbef39ff -d '<json body>'
```

Example prompt: Append a new event of type 'tool_call_result' to agent run 'run-abc123' in the 'payments' namespace, keeping state for 300 seconds, and then checkpoint the current progress so I can resume if the run is interrupted.

## When to prefer this

Choose this endpoint when an autonomous agent needs durable, scoped, per-run state storage with append-log semantics — particularly within the Bounty Engineer x402 ecosystem where runs are already paying per-call via USDC micropayments. Prefer over generic KV stores when you need event-type tagging, TTL-based expiry, stream identity, and cryptographic data hashes per event.

## Known failure modes

- Missing or invalid run_id returns an error
- op enum value not in [append, checkpoint, read] causes validation failure
- ttl_seconds below 30 rejected
- limit above 100 rejected
- Run not found when reading returns empty or 404-equivalent
- Payment not included or insufficient USDC triggers x402 payment-required response
- Expired ledger entries may not be returned on read

## How this service works

Machine-buyable infrastructure for autonomous agents: API cost routing, margin optimization, funding-rate data, webpage extraction, result verification, spend controls, retry planning, state, tender search and GitHub bounty intelligence.

## Output

Returns a JSON object with ok: true, the operation name (append/checkpoint/read), mode set to 'agent_run_ledger', a data_hash of the stored payload, and a stream_id identifying the ledger stream for this run.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "op": {
   "enum": [
    "append",
    "checkpoint",
    "read"
   ],
   "type": "string"
  },
  "data": {},
  "limit": {
   "type": "integer",
   "maximum": 100,
   "minimum": 1
  },
  "run_id": {
   "type": "string"
  },
  "event_id": {
   "type": "string"
  },
  "event_type": {
   "type": "string"
  },
  "ttl_seconds": {
   "type": "integer",
   "minimum": 30
  },
  "namespace_key": {
   "type": "string"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "ok": true,
  "op": "append",
  "mode": "agent_run_ledger",
  "data_hash": "...",
  "stream_id": "..."
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/bounty-engineer-agent-run-ledger-bbef39ff/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from bounty-engineer-x402-prod.onrender.com](https://www.zero.xyz/host/bounty-engineer-x402-prod.onrender.com/llms.txt)