Agent Readiness Check

Does your x402 endpoint return a challenge buyers can read?

If an unpaid request to your paid API does not come back as HTTP 402 with a parseable x402 challenge, agents cannot pay you and directories cannot list you. This test makes that unpaid request from outside your network and tells you what a buyer sees.

Run it

GET https://trademypage.com/check.php?domain=your-api.com&probe=/your/paid/path

Price: 0.01 USDC on Solana mainnet, paid with x402. The first, unpaid call returns our own 402 challenge; any x402 client that pays Solana USDC retries it with payment and receives the JSON report. Retrying the same paid request returns the same report with no second charge. If your domain cannot be reached at all, no report is produced and the payment is not settled.

What you get back

The x402_probe part of the report, for one unpaid GET to your path:

"x402_probe": {
  "status": 402, "error": null, "is_402": true,
  "payment_required_header": true, "parsed": true,
  "x402_version": 2, "accepts_count": 1,
  "offers": [{"scheme": "exact", "network": "solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp"}]
}

The same report also covers HTTPS and redirects, /llms.txt, /.well-known/agent-card.json and robots.txt rules for 11 AI crawlers, which is how many agents find a service before they ever call it. Field meanings are in the report guide.

Common failures it shows

Limits

The probe sends one unpaid GET to a path on the same domain you name. It does not pay your endpoint, so it cannot show that settlement or delivery works. It reports observations, not a certification. Private and internal addresses are refused.

OpenAPI · llms.txt · Terms of Service