Skip to main content
This is not a free tier. The bypass key is provisioned per customer for sandbox testing; abuse → key revoked. Use real X-PAYMENT in production.

​
Why

x402 is great for production AI-agent flows, but during integration:
  • You don’t have a wallet yet
  • You’re validating response shape against your client code
  • You want to hit each tier 50× to load-test parsing logic
Test-bypass routes mirror the paid tiers 1:1. Same handler, same response, no wallet involved.

​
Endpoints

​
Auth

Get the key from your onboarding rep. When the env value isn’t provisioned on the host (default), every /test/* request returns HTTP 503 — fail-closed by design.

​
Example

Response shape is identical to the paid endpoint — see the per-tier pages:

​
What test-bypass DOES NOT do

  • ❌ Does NOT charge USDC
  • ❌ Does NOT write a row in x402_payments
  • ❌ Does NOT trigger the facilitator settle hook
  • ❌ Does NOT consume any quota — there is no quota in x402
What it DOES log: the call ip + path are logged on our side for audit ([test-bypass] /check-address called from <ip>). Treat this as observability, not anonymity — paid x402 mode is more private.

​
Rate limit

/test/* shares the same per-IP rate limiter as paid endpoints.

​
Rotation

Your bypass key can be rotated by your onboarding rep at any time. Old key stops working immediately on the next x402-api restart.