# Bounty Engineer Agent Continuity API

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

Provides distributed task-state management for autonomous agents: claim, save, restore, heartbeat, and release leased job checkpoints with spend controls.

## Facts

- Endpoint: POST https://bounty-engineer-x402-prod.onrender.com/v1/agent-continuity?utm_source=zero.xyz
- Price: $0.01/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-continuity-api-de39286a
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_xyAdeqiLhLPkLYaGPWIX2

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-continuity-api-de39286a -d '<json body>'
```

Example prompt: Claim task job-abc123 in namespace my-agent-namespace-key-001 with a 60-second lease so I can start processing it exclusively, and give me the lease token so I can save checkpoints as I go.

## When to prefer this

Choose this endpoint when your autonomous agent needs to coordinate exclusive task ownership across distributed instances, persist intermediate state/checkpoints for long-running jobs, or implement heartbeat-based lease renewal to tolerate agent crashes. Prefer it over generic key-value stores when you need built-in lease semantics, TTL management, and per-call micropayment billing via x402 USDC.

## Known failure modes

- Lease already held by another agent — acquired returns false
- Invalid or expired lease_token — operation rejected
- namespace_key too short (min 24 chars) — validation error
- ttl_seconds or lease_seconds out of allowed range — 400 error
- Payment not settled — endpoint returns 402 requiring x402 payment
- Unknown op value not in enum — schema validation failure
- task_id exceeds 96 character limit — rejected

## 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 (boolean), the op performed, mode ('agent_continuity_cloud'), task_id, acquired (boolean indicating whether the lease was successfully claimed), and a lease_token UUID issued after payment settlement.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "op": {
   "enum": [
    "save",
    "restore",
    "claim",
    "heartbeat",
    "complete",
    "release",
    "status"
   ],
   "type": "string"
  },
  "result": {},
  "task_id": {
   "type": "string",
   "maxLength": 96
  },
  "checkpoint": {},
  "lease_token": {
   "type": "string"
  },
  "ttl_seconds": {
   "type": "integer",
   "maximum": 2592000,
   "minimum": 300
  },
  "lease_seconds": {
   "type": "integer",
   "maximum": 900,
   "minimum": 10
  },
  "namespace_key": {
   "type": "string",
   "minLength": 24
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "ok": true,
  "op": "claim",
  "mode": "agent_continuity_cloud",
  "task_id": "job-123",
  "acquired": true,
  "lease_token": "uuid-issued-after-settlement"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/bounty-engineer-agent-continuity-api-de39286a/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)