# StatePulse API – Coordination Bounties Lookup

> StatePulse API – Coordination Bounties Lookup is a paid API for AI agents from statepulse-api.hahavoid0.workers.dev, paid per call via x402, $0.01/call, status unknown (last checked 2026-09-14).

Looks up on-chain coordination bounty details by querying deposited USDC bounty records on the blockchain, returning status, reward amount, sender, and transaction hash.

## Facts

- Endpoint: POST https://statepulse-api.hahavoid0.workers.dev/coordination/bounties
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/statepulse-api-coordination-bounties-lookup-7e83e300
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_xXEaFZ5zmrsKzZ0Ji7H__

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 statepulse-api-coordination-bounties-lookup-7e83e300 -d '<json body>'
```

Example prompt: Can you check the on-chain status of coordination bounty ID 0x000000000000000000000000000000000000000000000000000000000000000a and tell me who deposited it, how much USDC is attached, and what the transaction hash is?

## When to prefer this

Use this endpoint when you need a quick, pay-per-call on-chain lookup of a coordination bounty's deposit status, reward, and sender without setting up API keys or managing subscriptions. It is well-suited for agents that need to verify bounty conditions before executing work or releasing funds, especially in Base/USDC ecosystems.

## Known failure modes

- Unknown or invalid bounty ID returns empty or unsupported result
- Network latency from Cloudflare Workers or Base RPC may cause timeouts
- Malformed bounty ID format (non-hex or wrong length) may cause parsing errors
- Bounty not yet mined or pending confirmation may return stale status
- Payment failure via x402 (insufficient USDC balance) blocks the call entirely

## How this service works

Deposits a real USDC bounty on Base using EIP-3009 receiveWithAuthorization, locking it in the non-custodial EscrowRegistry contract. Matches: deposit onchain bounty, non-custodial escrow bounty, lock usdc bounty.

## Output

Returns a JSON object containing the bounty's on-chain details: sender wallet address, current status (e.g. DEPOSITED), transaction hash, bounty ID, and reward amount in USDC, along with a supported flag and confidence level (e.g. 'high').

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "result": {
   "sender": "0x742d35Cc6634C0532925a3b844Bc454e4438f44e",
   "status": "DEPOSITED",
   "tx_hash": "0x...",
   "bounty_id": "0x000000000000000000000000000000000000000000000000000000000000000a",
   "reward_usdc": "10.00"
  },
  "supported": true,
  "confidence": "high"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/statepulse-api-coordination-bounties-lookup-7e83e300/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from statepulse-api.hahavoid0.workers.dev](https://www.zero.xyz/host/statepulse-api.hahavoid0.workers.dev/llms.txt)