Coinbase adds usage billing

Coinbase’s new billing feature fixes a boring but expensive problem: an artificial intelligence agent often doesn’t know the final cost of a job until the job is done, but old payment rails usually want the price up front. On April 10, 2026, Coinbase’s developer arm said x402 now supports a usage model called “Upto,” where a buyer approves a ceiling and pays the actual amount used instead of a flat fee. (cointelegraph.com) x402 is Coinbase’s payment protocol for the web, and it turns the old Hypertext Transfer Protocol status code “402 Payment Required” into a working checkout step for software. In Coinbase’s docs, a server can answer a request with payment instructions, the client can send back a signed payment payload, and the server can return the resource after verification and settlement. (docs.cdp.coinbase.com) That sounds abstract, but the everyday version is simple: software asks for something, gets a bill, pays it, and retries the same request. Coinbase says x402 was built so APIs, apps, and artificial intelligence agents can pay directly over standard web requests without accounts, sessions, or manual checkout screens. (docs.cdp.coinbase.com) Before this change, the cleanest model was a fixed price per call, which works for a weather lookup but breaks for variable jobs. Coinbase’s x402 FAQ now lists “Up-to” as a pricing scheme where the client authorizes a maximum amount and is charged only for actual usage such as tokens, compute time, or bandwidth. (docs.x402.org) The GitHub spec makes the use case even plainer: “exact” is like paying $1 to read an article, while “upto” is for jobs where the final bill depends on what happened during the request. The EVM version of the spec says the client authorizes a maximum amount first, and the facilitator settles the actual amount used at the end of the request. (github.com, github.com) That is a much better fit for large language model inference, where the number of output tokens can change from one answer to the next. It also fits bandwidth metering and time-based access, which the x402 docs name as examples of variable-cost resources. (github.com) Coinbase has been pushing x402 as infrastructure for “agentic commerce,” which is the idea that software agents will buy data, tools, and compute from each other without a human in the loop. In September 2025, Coinbase and Cloudflare said they planned an x402 Foundation to make the standard neutral and open for artificial intelligence-driven payments. (coinbase.com) The protocol is already designed around small, automatic payments, not monthly subscriptions. Coinbase’s docs say x402 supports micropayments, machine-to-machine transactions, and facilitator services that handle verification and settlement so sellers do not need to run their own blockchain payment stack. (docs.cdp.coinbase.com) Coinbase also built x402 to work with gas sponsorship tools, which is blockchain shorthand for letting someone else cover the network fee so the end user does not need native tokens in the wallet. The docs list gasless Permit2 approvals as an extension, and recent coverage of the Upto launch said the feature helps support gasless transaction patterns for artificial intelligence services. (docs.cdp.coinbase.com, coincentral.com) The business angle is less about one new button and more about the plumbing around it. If agents start buying model calls, data queries, and compute in tiny increments, someone has to connect those usage events to budgets, treasury rules, invoicing, and onchain settlement, and Upto gives that middleware a cleaner payment primitive to work with. (docs.x402.org, docs.cdp.coinbase.com) Coinbase is trying to make that plumbing feel as normal as loading a web page. If x402 works the way Coinbase and its partners want, “402 Payment Required” stops being a forgotten line in the web standard and becomes the moment one piece of software pays another for exactly the work it just did. (docs.cdp.coinbase.com, coinbase.com)