x402 Agent Micropayment Support So AI Agents Can Pay Per Call Without an Account
Lets autonomous agents pay tiny per-call fees for your API without ever creating a human account first.
What this signal tests
We check whether your metered endpoints support x402, an emerging HTTP-native micropayment standard (x402 means HTTP-native payments, named after the long-dormant 402 Payment Required status code). A compliant endpoint responds with HTTP 402 and either a PAYMENT-REQUIRED header or a JSON body containing an accepts array describing which x402 schemes the caller can use to pay.
Why it matters for your visibility in AI
Most paid APIs today require an account, a credit card, and a key - workflows designed for human developers. AI agents acting on behalf of one-off users cannot realistically navigate that. x402, championed by Coinbase through 2024 and 2025, lets an agent pay a few cents for a single API call, on the spot, with no prior relationship. Sites that support it can be called by zero-account agent buyers; sites that do not are limited to users who have already signed up. This is the leading emerging standard for agent-to-server payments. It is genuinely new and adoption is early, but the strategic logic is strong: when an agent has a small budget to research, compare, or transact on a user's behalf, it will route to providers that accept stateless micropayments. Early adopters are positioning themselves to be the default option once agent commerce scales.
Pass criteria at a glance
| Criterion | Passes when |
|---|---|
| At least one endpoint demonstrates spec-conformant 402 + x402 headers/body. |
How we test it
Our scanner fetches a metered endpoint without authentication and inspects the response. It passes if the server returns HTTP 402 - the long-dormant Payment Required status, now revived by x402 - together with either an x402 PAYMENT-REQUIRED header or a JSON body containing an accepts array that lists at least one x402 scheme and version. The endpoint must be spec-conformant; a generic 402 without x402 metadata does not pass.
Show technical detection method
GET metered endpoint without auth; pass if HTTP 402 with PAYMENT-REQUIRED header OR JSON body with 'accepts' array containing x402-version/scheme.
If your site fails: how to fix it
- Decide which of your endpoints make sense as agent-payable: typically metered data feeds, premium API calls, or one-off services priced under a dollar; the work to do this is best done by a developer who can read the x402 specification.
- Integrate x402 middleware using the Coinbase-maintained SDKs for TypeScript, Go, or Python; the middleware handles the 402 response, the accepts array, and the payment verification handshake.
- Start with a single low-risk endpoint - even an /api/x402/tip endpoint that accepts a voluntary micropayment is useful for proving the integration works and indexing your site as x402-aware.
- Document the supported payment schemes (currently primarily USDC on Base) and the price for each endpoint in your OpenAPI document so agents can plan ahead.
- Keep an eye on the x402 specification at x402.org as it evolves; this is a young standard and adopters benefit from staying current with its versions.
Quick facts
| Maturity | EMERGING |
|---|---|
| Weight | low |
| Category | Agent Actions |
Primary sources
Related signals
Frequently asked questions
Is this only useful when autonomous AI agents become mainstream?
x402 is genuinely forward-looking - most current traffic still comes from human-account workflows. Adopt this signal because you want to be indexed first as agent commerce ramps. Today's benefit is positioning and discovery; the transactional benefit grows over the next 12–24 months.
Do we have to accept cryptocurrency?
Currently x402's reference implementation uses USDC on Base, a regulated stablecoin. Other payment schemes are explicitly part of the spec; the accepts array is extensible. If you have a strong preference against crypto entirely, hold off and watch the spec until non-crypto schemes ship.
Does this cost anything to implement?
The x402 specification and SDKs are open source. Implementation cost is developer time - typically a few days for a first integration. Per-transaction settlement costs depend on the payment scheme; USDC on Base settles for fractions of a cent.
Will this matter in 2026 or is it years away?
x402 is firmly EMERGING - early adopters in 2025–2026, mainstream adoption likely later. Most businesses do not need it urgently. Adopt early if your business model benefits from agent micro-transactions: data APIs, premium content, AI-callable utility services.
Run your own scan
Run a free scan and see how your site grades across all 155 AI-readiness signals.