# x402 Oracle — Diagnose 402

> x402 Oracle — Diagnose 402 is a paid API for AI agents from x402orcle.vercel.app, paid per call via x402, $0.5/call, status unknown (last checked 2026-11-18).

Post-mortems a failed x402 HTTP 402 payment handshake, diagnosing issues with payment shape, bazaar extension, network, asset, or resource URL.

## Facts

- Endpoint: POST https://x402orcle.vercel.app/api/consult/oracle_diagnose_402?utm_source=zero.xyz
- Price: $0.5/call
- Payment: x402
- Status: unknown
- Last checked: 2026-11-18
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/x402-oracle-diagnose-402-81db4e4e
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_lGuSpEzaRYyh8qgFPLSlg

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 x402-oracle-diagnose-402-81db4e4e -d '<json body>'
```

Example prompt: My agent keeps getting a 402 PAYMENT-REQUIRED error even after attempting payment on this resource — can you diagnose the x402 handshake failure and tell me what the verdict and fix is? The resource URL is https://someapi.example.com/endpoint and here is the raw 402 challenge: eyJwYXltZW50IjoiLi4uIn0=

## When to prefer this

Choose this endpoint when an x402-enabled agent or developer has already received a 402 PAYMENT-REQUIRED response and needs to understand exactly why the payment handshake failed — especially for bazaar extension issues, wrong network/asset configuration, or malformed payment headers. It is specifically designed for post-mortem diagnosis of x402 protocol failures rather than general API debugging.

## Known failure modes

- Invalid or unparseable base64 challenge returns error verdict
- Resource URL unreachable or malformed causes incomplete diagnosis
- Unrecognized 402 challenge shape may yield generic verdict
- Missing both resource_url and challenge_b64_or_json may result in empty or error response
- Network or payment asset mismatch may not be fully diagnosable from challenge alone

## How this service works

Post-mortem a 402 handshake: PAYMENT-REQUIRED shape, bazaar extension, network, asset, resource.url.

## Output

Returns a JSON object with a 'verdict' field identifying the specific failure category (e.g. 'missing_bazaar_extension', 'wrong_network', 'malformed_payment_header') and a 'wisdom' field providing human-readable diagnostic explanation and developer remediation guidance.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "resource_url": {
   "type": "string"
  },
  "challenge_b64_or_json": {
   "type": "string"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "wisdom": "…",
  "verdict": "missing_bazaar_extension"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/x402-oracle-diagnose-402-81db4e4e/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from x402orcle.vercel.app](https://www.zero.xyz/host/x402orcle.vercel.app/llms.txt)
