# Bounty Engineer x402 Payment Preflight

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

Checks and prepares x402 payment metadata for a given URL before an autonomous agent commits a micropayment

## Facts

- Endpoint: POST https://bounty-engineer-x402-prod.onrender.com/v1/x402-payment-preflight?utm_source=zero.xyz
- Price: $0.05/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-x402-payment-preflight-4beb37cd
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_9IjQ4s3ZhUIAuzRkJDfI4

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-x402-payment-preflight-4beb37cd -d '<json body>'
```

Example prompt: Before you spend any USDC on that API, run a preflight check on https://api.example.com/data to see if it's x402-ready and what the payment decision comes back as.

## When to prefer this

Use this endpoint when an autonomous agent needs to confirm that a target URL supports x402 payment semantics before committing USDC — especially useful for cost routing, agent fleet deployment validation, or any workflow where payment failures are expensive. Prefer this over blindly calling a paid endpoint and handling 402 errors reactively.

## Known failure modes

- Invalid or malformed URL returns validation error
- URL not reachable or returns non-x402 response leads to low score or failed decision
- Missing URL field in request body causes 400-level error
- Endpoint may return ok:false with a decision indicating metadata is not ready

## 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, a 'mode' string (e.g. 'x402_payment_preflight'), a numeric 'score' (0–100) indicating payment readiness, and a 'decision' string (e.g. 'metadata_ready') indicating whether the endpoint is prepared for x402 payment processing.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "url": {
   "type": "string",
   "format": "uri"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "ok": true,
  "mode": "x402_payment_preflight",
  "score": 100,
  "decision": "metadata_ready"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/bounty-engineer-x402-payment-preflight-4beb37cd/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)