API Keys & Subscriptions vs x402 & MPP (HTTP 402)
Human-provisioned API keys, credit cards & monthly SaaS tiers is the classic web primitive built for human browsers and pre-integrated services (Meter and bill API usage to a human developer account with a stored credit card), whereas x402 and its step 7 (Pay) peers provide the machine-native agentic surface (none — signalled per-request via the 402 status code, not a fixed well-known path) so autonomous agents can answer: "How can an HTTP client pay per-request or per-resource, in stablecoins, without accounts, API keys, or signup?" Across the agenticweb.wiki conformance panel, x402 is multi-implementation (x402 Foundation (x402.org live dashboard)).
How API Keys & Subscriptions compares to x402 & MPP (HTTP 402) at step 7 (Pay): why the classic primitive breaks for software agents, and how sites deploy both together.
| Dimension | Human-provisioned API keys, credit cards & monthly SaaS tiers Classic web | x402 Agentic web |
|---|---|---|
| Primary consumer | Human driving a web browser or pre-integrated developer code | Autonomous software agent, coding harness, or AI search/RAG crawler |
| Lifecycle step | Classic web baseline for step 7 (Pay) | 7 Pay: Settle the bill |
| Core question answered | Meter and bill API usage to a human developer account with a stored credit card. | How can an HTTP client pay per-request or per-resource, in stablecoins, without accounts, API keys, or signup? |
| Wire format & entrypoint | Authorization: Bearer <api_key> after manual dashboard signup | HTTP header at none — signalled per-request via the 402 status code, not a fixed well-known path |
| Failure mode for agents | An agent that needs to make a single $0.002 query against a new data source cannot pause to create an account, pass KYC, verify an email, enter a credit card, and copy an API key into its environment. | Solved natively: x402 is an open, HTTP-native payment protocol that activates the long-reserved (since 1999) HTTP 402 "Payment Required" status code: a server responds 402 with machine-readable payment requirements, the client pays (in practice, stablecoins over an EVM-compatible network) and retries the request with proof of payment attached. |
| Governance & status | Established IETF / W3C / industry baseline | x402 Foundation, a Series of LF Projects, LLC (Linux Foundation); operational launch announced 2026-07-14; Executive Director Michael Hursta from 2026-10-01; 50+ members — Open, neutral standard for internet-native payments |
| Live adoption (/check/ census) | Universal across the classic web | multi-implementation — x402 Foundation (x402.org live dashboard) |
| Primary specification | https://www.rfc-editor.org/rfc/rfc9110#name-402-payment-required | https://github.com/x402-foundation/x402/blob/main/specs/transports-v2/http.md |
Why API Keys & Subscriptions breaks when the caller is an agent
An agent that needs to make a single $0.002 query against a new data source cannot pause to create an account, pass KYC, verify an email, enter a credit card, and copy an API key into its environment.
When to use which (and how they work together)
- Keep Human-provisioned API keys, credit cards & monthly SaaS tiers: You have long-lived enterprise integrations with predictable monthly volume and negotiated contracts.
- Add x402: You want zero-signup, per-request machine micropayments where an unauthenticated HTTP request receives a 402 Payment Required challenge and immediately settles in stablecoins or Lightning via x402, MPP, or L402.
All agentic web standards replacing or extending API Keys & Subscriptions
- x402 — multi-implementation: How can an HTTP client pay per-request or per-resource, in stablecoins, without accounts, API keys, or signup?
- Machine Payments Protocol (MPP) — multi-implementation: How can a machine client (an agent, script, or another server) pay for an HTTP resource using any payment network, not just one?
- L402 — shipping: How can a client pay for, and then authenticate to, a metered API resource over the Lightning Network with no accounts or database-backed sessions?
- s402 — prototype: How can an agent pay a Sui-native resource using six payment schemes (including prepaid batching and escrow), while staying wire-compatible with plain x402 clients?
- Cloudflare Pay per crawl — prototype: How can a site charge an AI crawler per request, and how does the crawler agree to pay?
- x401: HTTP Proof Requirement Protocol — shipping: How can a resource ask an agent to prove something about the person behind it, such as being a verified human, before serving a request?