Is your x402 server
actually ready?

Free compliance audit against every paymentauth.org spec plus cross-registry visibility (Bazaar, x402scan, mppscan). No signup. Results in under a second.

try hirescrape.com · the402.ai · exa.ai
01
Discovery
OpenAPI 3.1, x-payment-info, ownership proofs, /.well-known/x402, llms.txt.
02
Runtime 402
Status, headers, 16KB cap, x402 v2, bazaar.schema, CAIP-2.
03
HTTP Payment auth
draft-httpauth-payment-00 auth-params + draft-payment-intent-charge-00 fields.
04
Per-method charge
evm · tempo · solana · stellar · lightning · stripe · card — auto-detected.
05
JSON-RPC / MCP
draft-payment-transport-mcp-00. Probes /mcp, /rpc, /jsonrpc for error -32042.
06
Registry visibility
Coinbase Bazaar, x402scan, mppscan — live queries.
for agents
/llms.txt
agent-readable site index (markdown)
/openapi.json
OpenAPI 3.1 with x-payment-info
/.well-known/x402
x402 discovery manifest
SKILL.md
install as a Claude Code skill
$ npx agentcash fetch "https://x402audit.dev/api/audit?url=hirescrape.com"
what it catches
  • › Oversized PAYMENT-REQUIRED headers (Node's 16KB cap)
  • › Missing extensions.bazaar.schema.properties.input/output
  • › Malformed Payment auth-params per draft-httpauth-payment-00 §5.1
  • › Wrong CAIP-2 network refs, non-checksummed EVM addresses
  • › Empty ownership proofs, missing /.well-known/x402
  • › Unindexed on Bazaar, x402scan, or mppscan