Coinbase: usage‑based dev pricing

Coinbase just changed the part of agent payments that kept breaking the business model: a chatbot request that costs 2 cents and a bigger request that costs 40 cents no longer have to be sold at the same flat price. Coinbase Developer Platform said on April 9 that usage-based pricing is now live on its x402 system for large language model inference, compute, and data queries. (x.com, cointelegraph.com) x402 is Coinbase’s attempt to turn the old Hypertext Transfer Protocol status code 402, which was reserved for “payment required,” into a way for software to pay software. Coinbase markets it as a payments rail inside the Coinbase Developer Platform, where apps and agents can buy digital services without a human checking out each time. (coinbase.com, docs.cdp.coinbase.com) The problem with flat pricing is simple: many agent tasks do not cost the seller the same amount every time. A short model reply, a long model reply, and a deep data pull can all hit different compute bills, so one fixed fee forces the seller either to overcharge small jobs or lose money on big ones. (cointelegraph.com, forklog.com) Coinbase says the new scheme is called “Upto,” and it is available in the x402 software development kit and the Coinbase Developer Platform Facilitator. In plain terms, that gives a service a way to authorize a payment ceiling first and then charge only for the amount actually used inside that limit. (x.com, cointelegraph.com) That fits the way artificial intelligence agents actually behave in production. Coinbase’s own AgentKit and Agentic Wallet products are built around autonomous software that can hold funds, call tools, and pay for services, so a pricing model that rises and falls with each request matches the product stack Coinbase is already pushing to developers. (docs.cdp.coinbase.com, docs.cdp.coinbase.com, coinbase.com) Coinbase has already used pay-as-you-go pricing in other parts of its developer business. Its Node application programming interface charges by “Billing Units” tied to computational complexity, while server wallets and embedded wallets charge by wallet operations instead of a fixed platform subscription. (docs.cdp.coinbase.com, docs.cdp.coinbase.com, docs.cdp.coinbase.com) So this is less a brand-new pricing philosophy than an extension of Coinbase’s existing developer model into machine-to-machine payments. The new part is that the same logic now reaches agent purchases for variable-cost services, where the cost of one request can swing with token count, runtime, or query depth. (docs.cdp.coinbase.com, cointelegraph.com, forklog.com) Coinbase is also trying to make those payments easier to settle onchain. Coverage of the launch says the upgrade runs on an Ethereum Virtual Machine implementation, supports ERC-20 tokens, and can use the Coinbase Developer Platform Facilitator for gasless payments, which means the user does not have to manually handle network fees for every small transaction. (gncrypto.news, edgen.tech) The open question is adoption, not packaging. One report said x402 activity fell from 13.7 million weekly transactions in November to a little over 112,000 by late March, so Coinbase is improving the economics of the system at the same time it still has to prove that enough developers want agents buying services this way. (edgen.tech) If that demand shows up, usage-based billing solves a very specific headache: a platform team can let an agent call a model, a compute job, or a data service without guessing one flat fee that fits every request. The seller gets a spending cap, the buyer gets a cleaner bill, and Coinbase gets one more reason for developers to keep agent payments inside its stack. (x.com, coinbase.com, docs.cdp.coinbase.com)