x402 vs API keys: pay-per-call without credentials
The traditional model is: sign up, get an API key, pick a plan, manage quotas, rotate secrets. x402 collapses all of that into a per-call payment.
What changes without keys
No signup and no key to provision, store, rotate, or leak.
No plan tiers or quotas — you pay only for the calls you make.
No vendor lock-in via account state — access is just a funded wallet.
Adding a new API means a new endpoint URL, not a new credential.
Why agents prefer it
An agent that wants to call a new API normally needs a human to create an account and paste a key. With x402 the agent can discover the price in the 402 response and pay on the spot from a shared wallet — no human provisioning step, which is exactly what makes large tool catalogs practical.
Try keyless access
Here is a real call with no key and no account:
cURL — free trialbash
# Free trial call — real data, no payment, no signup (1/endpoint/hour):
curl "https://2s.io/api/weather/zip?zip=94103&trial=1"
An API key authenticates a pre-registered account. x402 has no account — payment itself authorizes the call. You fund a wallet and pay per request, with nothing to provision or rotate.
Is x402 cheaper than a subscription?
It depends on volume, but x402 is pure usage-based: you pay per call with no monthly minimum. For bursty or exploratory usage that is often cheaper than a fixed plan; for steady high volume, compare the per-call cost to a plan.
What about rate limits without keys?
Providers still apply IP-based limits to anonymous probes, but paid calls are gated by payment rather than a per-key quota — you are not capped by a plan tier.