# StatePulse API - Coordination Bounty Release

> StatePulse API - Coordination Bounty Release 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-15).

Releases a completed bounty payout to a worker wallet on-chain, recording a COMPLETED status and transaction hash.

## Facts

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

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-bounty-release-85010076 -d '<json body>'
```

Example prompt: Release the bounty with ID 0x000000000000000000000000000000000000000000000000000000000000000a and pay out the completed reward to worker wallet 0x976EA74026E726554dB657fa54763abd0C3a0aa9.

## When to prefer this

Use this endpoint when you need to finalize and disburse a coordination bounty payout to a specific worker wallet on-chain via Base/USDC, particularly in agentic or automated workflows where no API key is available and micropayments via x402 are acceptable. Prefer this over manual on-chain transactions when you need a structured JSON confirmation with tx_hash and status.

## Known failure modes

- Bounty ID not found or already released — may return error or unexpected status
- Worker wallet address invalid or malformed — request rejected
- Insufficient authorization to release bounty — access denied
- On-chain transaction failure — tx_hash may be absent or status non-COMPLETED
- x402 payment failure — call not executed if USDC payment is rejected

## How this service works

Triggers the EscrowRegistry contract to release a locked USDC bounty to a worker wallet. Releasing can only be authorized by the StatePulse hot wallet (owner). Matches: release onchain bounty, payout escrow bounty, resolve locked bounty.

## Output

Returns a JSON object confirming the bounty release with a 'COMPLETED' status, the on-chain transaction hash (tx_hash), the bounty ID, the recipient worker wallet address, a 'supported' flag, and a confidence level ('high').

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "result": {
   "status": "COMPLETED",
   "tx_hash": "0x...",
   "bounty_id": "0x000000000000000000000000000000000000000000000000000000000000000a",
   "worker_wallet": "0x976EA74026E726554dB657fa54763abd0C3a0aa9"
  },
  "supported": true,
  "confidence": "high"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/statepulse-api-coordination-bounty-release-85010076/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)