# Bounty Engineer Action Idempotency API

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

Manages idempotency for autonomous agent actions by reserving, checking status, committing, or releasing action slots to prevent duplicate execution

## Facts

- Endpoint: POST https://bounty-engineer-x402-prod.onrender.com/v1/action-idempotency?utm_source=zero.xyz
- Price: $0.002/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-11
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/bounty-engineer-action-idempotency-api-41e6b732
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_5iBL56iwKvOF6lTR2JjAy

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-action-idempotency-api-41e6b732 -d '<json body>'
```

Example prompt: Before I run this payment action again, reserve an idempotency slot for action_id 'pay-invoice-8821' with fingerprint 'sha256-abc123' in namespace 'payments', set to expire in 120 seconds — I need to make sure it hasn't already been committed.

## When to prefer this

Choose this endpoint when an autonomous agent needs exactly-once execution guarantees for critical or paid actions — especially when retries, network failures, or multi-agent coordination could cause duplicate side effects. It is specifically designed for agent commerce pipelines where double-execution means wasted spend or duplicate transactions. Prefer it over application-level deduplication when you need a shared, cross-process idempotency store with TTL-based expiry and commit/release lifecycle management.

## Known failure modes

- Conflict detected if action_id is already reserved by another process (conflict: true)
- Duplicate detected if action was already committed (duplicate: true, decision may block re-execution)
- Invalid op enum value returns validation error
- TTL below 30 seconds rejected by schema minimum
- Missing action_id or namespace_key may cause server error or undefined behavior
- Payment failure (x402) if USDC balance insufficient for $0.002 call fee

## 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

A JSON object confirming the operation outcome, including 'ok' boolean, the operation type performed, whether a conflict was detected, the decision made (e.g. 'reserved'), and a duplicate flag indicating whether this action was already seen.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "op": {
   "enum": [
    "reserve",
    "status",
    "commit",
    "release"
   ],
   "type": "string"
  },
  "payload": {},
  "action_id": {
   "type": "string"
  },
  "fingerprint": {
   "type": "string"
  },
  "result_hash": {
   "type": "string"
  },
  "ttl_seconds": {
   "type": "integer",
   "minimum": 30
  },
  "namespace_key": {
   "type": "string"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "ok": true,
  "op": "reserve",
  "mode": "agent_action_idempotency",
  "conflict": false,
  "decision": "reserved",
  "duplicate": false
 }
}
```

## More

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