# x402 Radar Conformance Probe

> x402 Radar Conformance Probe is a paid API for AI agents from remind-host-lots-rouge.trycloudflare.com, paid per call via x402, $0.002/call, status unknown (last checked 2026-09-14).

Checks whether a given URL serves a valid x402 payment handshake and returns its price, asset, network, payTo address, and latency.

## Facts

- Endpoint: POST https://remind-host-lots-rouge.trycloudflare.com/api/check
- Price: $0.002/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/x402-radar-conformance-probe-e87bc97c
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_b0Ex4cWG-708fOGinP9QF

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-radar-conformance-probe-e87bc97c -d '<json body>'
```

Example prompt: Before I pay, can you probe https://api.exa.ai/search and tell me if it's a valid x402 endpoint — what's the price, which network and asset it uses, the payTo address, and how fast it responds?

## When to prefer this

Use this endpoint when an AI agent needs to verify that a third-party x402-enabled API is live and correctly configured before committing a payment. It is the right choice when you want to inspect the price, asset, network, and payTo address of an x402 endpoint without actually paying. Prefer this over manually parsing 402 responses yourself, or when building automated pipelines that must gate payment execution on valid handshake confirmation.

## Known failure modes

- Probed URL is unreachable — alive: false, no payment data returned
- URL does not serve a 402 status — x402: false, valid_handshake: false
- Malformed or non-conformant 402 response — valid_handshake: false with partial fields
- Network timeout leading to high latency_ms or missing response
- Input URL is invalid or missing — request rejected with error
- Transient Cloudflare tunnel instability causing probe failures

## How this service works

Live x402 conformance probe: url=<endpoint>, returns whether it serves a valid 402 handshake, actual price/asset/network/payTo, latency. Verify before you pay. By x402 Radar.

## Output

Returns a JSON object indicating whether the probed URL is alive, x402-compliant, and serving a valid 402 handshake. Includes the detected price in USD (if USDC), atomic price, asset type, blockchain network, payTo wallet address, x402 scheme (e.g. 'exact'), x402 protocol version, HTTP status code returned, and round-trip latency in milliseconds.

## Response schema (JSON Schema)

```json
{
 "type": "object",
 "example": {
  "x402": true,
  "alive": true,
  "scheme": "exact",
  "status": 402,
  "checked": "https://api.exa.ai/search",
  "network": "base",
  "latency_ms": 340,
  "valid_handshake": true,
  "price_usd_if_usdc": 0.007
 },
 "properties": {
  "at": {
   "type": "string"
  },
  "x402": {
   "type": "boolean"
  },
  "alive": {
   "type": "boolean"
  },
  "asset": {
   "type": "string"
  },
  "payTo": {
   "type": "string"
  },
  "scheme": {
   "type": "string"
  },
  "status": {
   "type": "number"
  },
  "checked": {
   "type": "string"
  },
  "network": {
   "type": "string"
  },
  "latency_ms": {
   "type": "number"
  },
  "price_atomic": {
   "type": "string"
  },
  "x402_version": {
   "type": "number"
  },
  "valid_handshake": {
   "type": "boolean"
  },
  "price_usd_if_usdc": {
   "type": "number"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/x402-radar-conformance-probe-e87bc97c/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from remind-host-lots-rouge.trycloudflare.com](https://www.zero.xyz/host/remind-host-lots-rouge.trycloudflare.com/llms.txt)