# Bounty Engineer Agent Execution Gate

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

Acts as a gating layer for autonomous agent tool calls, enforcing spend controls, idempotency, retry planning, and decision routing before an agent action executes.

## Facts

- Endpoint: POST https://bounty-engineer-x402-prod.onrender.com/v1/agent-execution-gate?utm_source=zero.xyz
- Price: $0.02/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-execution-gate-4a7d63ea
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_ScRa7KTaD6Ok2rkNlLxwV

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-execution-gate-4a7d63ea -d '<json body>'
```

Example prompt: Before running the next tool call in my agent pipeline, check through the execution gate — action ID 'scrape-job-42', namespace 'prod-bounty', fingerprint 'abc123', TTL 60 seconds — and tell me if it's allowed to proceed.

## When to prefer this

Choose this endpoint when an autonomous agent needs a centralized gate to authorize, deduplicate, and spend-control individual tool calls before execution — especially in multi-step pipelines where idempotency, retry safety, and budget enforcement are critical. Prefer this over ad-hoc agent logic when you need a single decision point that combines fingerprinting, TTL-based reservation, and namespace-scoped spend controls in one call.

## Known failure modes

- Action already executed (idempotency conflict) — returns decision 'deny' with idempotency status 'conflict'
- TTL too short (below 30 seconds minimum) — request rejected with validation error
- Missing required fields (tool, action_id, fingerprint) — 400-level error
- Insufficient funds or spend limit exceeded — decision 'deny' with spend control reason
- Service unavailable on Render cold start — timeout or 503 error
- Invalid namespace_key — unauthorized or unrecognized namespace response

## 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, the execution mode ('agent_execution_gate'), a tool decision object containing 'allow' or 'deny', a top-level 'decision' field, and an idempotency object indicating whether the action slot was 'reserved' or already consumed.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "tool": {
   "type": "object"
  },
  "payload": {},
  "purchase": {
   "type": "object"
  },
  "action_id": {
   "type": "string"
  },
  "fingerprint": {
   "type": "string"
  },
  "ttl_seconds": {
   "type": "integer",
   "minimum": 30
  },
  "namespace_key": {
   "type": "string"
  },
  "untrusted_context": {}
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "ok": true,
  "mode": "agent_execution_gate",
  "tool": {
   "decision": "allow"
  },
  "decision": "allow",
  "idempotency": {
   "decision": "reserved"
  }
 }
}
```

## More

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