# Bounty Engineer Agent State Fabric

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

Provides persistent key-value state storage for autonomous agents, supporting get/put/delete, atomic counters, compare-and-set, and distributed locking operations.

## Facts

- Endpoint: POST https://bounty-engineer-x402-prod.onrender.com/v1/agent-state?utm_source=zero.xyz
- Price: $0.003/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-12
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/bounty-engineer-agent-state-fabric-8097a9ca
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_d4hMgMrmQ9AfdwiJC1MFN

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-state-fabric-8097a9ca -d '<json body>'
```

Example prompt: Store the current workflow step as 'step-3' under the key 'workflow-step' in my agent state, with a TTL of 300 seconds, so I can resume from this point if interrupted.

## When to prefer this

Choose this endpoint when an autonomous agent needs lightweight, fast, pay-per-use persistent state without provisioning a full database — especially useful for workflow checkpointing, distributed locking, atomic counters, and inter-agent coordination in x402-native agent pipelines. Prefer over full databases when state is ephemeral, TTL-bounded, and cost-per-call billing via USDC micropayments is acceptable.

## Known failure modes

- Key not found on get/delete returns ok:false or null value
- Compare-and-set fails if expected value does not match current value
- Lock acquisition fails if lock is already held by another agent
- TTL below 30 seconds is rejected with a validation error
- Missing required 'op' or 'key' fields return a 400-level error
- Service unavailability on Render cold start may cause latency spikes

## 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 an 'ok' boolean confirming success, the operation name ('op'), the state key, the current value after the operation, and a 'mode' field confirming 'agent_state_fabric'. For counter operations, returns the new numeric value. For locks, confirms acquisition or release.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "op": {
   "enum": [
    "get",
    "put",
    "delete",
    "counter_add",
    "compare_and_set",
    "lock_acquire",
    "lock_release"
   ],
   "type": "string"
  },
  "key": {
   "type": "string"
  },
  "delta": {
   "type": "number"
  },
  "value": {},
  "expected": {},
  "ttl_seconds": {
   "type": "integer",
   "minimum": 30
  },
  "namespace_key": {
   "type": "string"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "ok": true,
  "op": "counter_add",
  "key": "workflow-step",
  "mode": "agent_state_fabric",
  "value": 1
 }
}
```

## More

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