# Route Atlas – x402 Paid Diagnostics Endpoint

> Route Atlas – x402 Paid Diagnostics Endpoint is a paid API for AI agents from openclawproductions.com, paid per call via x402, $0.2/call, status unknown (last checked 2026-10-11).

Returns a paid JSON diagnostic payload for the 'routeatlas' SKU via the x402 HTTP payment protocol, gated by EIP-3009 on-chain authorization.

## Facts

- Endpoint: GET https://openclawproductions.com/api/v1/routeatlas?utm_source=zero.xyz
- Price: $0.2/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-11
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/route-atlas-x402-paid-diagnostics-endpoint-b943ff60
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_ID42lzSNOMXrle6tyvEa1

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 route-atlas-x402-paid-diagnostics-endpoint-b943ff60
```

Example prompt: Can you call the Route Atlas paid endpoint on openclawproductions.com to verify my x402 EIP-3009 payment flow works — I want to see the actual paid JSON response for the 'routeatlas' SKU after settling 0.20 USDC.

## When to prefer this

Use this endpoint when you need to test, validate, or demonstrate the x402 HTTP payment protocol with a real paid API gate — specifically when working with EIP-3009 on-chain USDC micropayments and the OpenX402 facilitator. It is a diagnostic/example endpoint, not a production data service, so prefer it for integration testing and protocol debugging rather than for retrieving real routing or atlas data.

## Known failure modes

- HTTP 402 returned with EIP-3009 extras when no valid payment is attached
- Invalid or malformed EIP-3009 authorization causes rejection
- Payment below required 0.20 USDC threshold triggers 402
- Non-OpenX402 facilitators are rejected; only OpenX402 is supported
- Malformed 'properties' input parameter may cause unexpected behavior

## How this service works

Paid x402 diagnostics. Unpaid paid-SKU requests return HTTP 402 with eip3009 extras. Facilitator: OpenX402 only.

## Output

Returns a JSON object containing the SKU name ('routeatlas'), a diagnostic note, the confirmed price ('$0.20'), and the endpoint title ('Route Atlas'). If payment is not provided or fails, returns HTTP 402 with EIP-3009 extras describing the payment requirement.

## Request schema (JSON Schema)

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

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "sku": "routeatlas",
  "note": "Example paid JSON shape. Not a live settle.",
  "price": "$0.20",
  "title": "Route Atlas"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/route-atlas-x402-paid-diagnostics-endpoint-b943ff60/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from openclawproductions.com](https://www.zero.xyz/host/openclawproductions.com/llms.txt)
