The x402 approach skips both. There is no API key to manage and no account to create.
The flow works like a vending machine that quotes its price before taking your coins. A client requests data, the server replies with an HTTP 402 “Payment Required” response, and the client signs a payment payload and resends the request.
That signature travels in a PAYMENT-SIGNATURE header. CoinGecko’s documentation notes that the x402 client builds this header on its own, so developers do not have to assemble it by hand.
The endpoints on offer cover a useful slice of what CoinGecko tracks. Supported queries include crypto price lookups, on-chain token data, pool searches and trending pool information.
The math on the cut is straightforward. A dollar of $USDC now buys twice as many requests as it did under the old $0.01 rate.
Why x402 exists in the first place
The x402 protocol was first developed by Coinbase. It revives the HTTP 402 status code, a part of the web’s plumbing that sat largely unused for years while the internet settled on ads and subscriptions instead.
The idea is to let machines pay machines directly. Instead of a company signing up for a plan and handing a key to its software, the software itself carries a wallet and pays per request.
That design is aimed squarely at automated systems, especially AI agents that need blockchain data on demand. An agent researching a token, rebalancing a portfolio or monitoring liquidity pools does not fit neatly into a human-shaped subscription tier.
Subscriptions assume predictable usage. Agents tend to be bursty, quiet for hours and then suddenly hungry for hundreds of data points at once.
Per-call micropayments match that pattern better. You pay for what you use and nothing for the hours when your agent is idle.
The Polygon addition matters more than it looks
Adding Polygon gives CoinGecko three $USDC settlement networks: Base, Solana and Polygon. Each brings its own developer community and its own set of wallets already holding stablecoins.
That matters because friction kills micropayments. If an agent’s wallet holds $USDC on Polygon but the data provider only accepts payment on Base, someone has to bridge funds first, which defeats the point of an instant, accountless purchase.
Meeting developers on the chains where their funds already sit removes that step. Builders on Polygon can now plug into CoinGecko’s x402 endpoints without moving money elsewhere.
It also signals that CoinGecko views x402 as a multichain standard rather than a single-network experiment. Coinbase incubated the protocol, but the payment rails are spreading beyond its own Base network.
What this means for developers and the data market
The most immediate winners are small teams and independent developers. Usage-based pricing lowers the bar for anyone who found a full subscription hard to justify for a side project or a prototype agent.
A developer testing an idea can now spend pocket change to see whether it works. If it flops, there is no plan to cancel.
For CoinGecko, the move represents a shift in how it sells its core product. Subscription models reward heavy, predictable users, while per-call pricing opens the door to a long tail of customers who would never have signed a contract.
The endpoints remain experimental, which means pricing, coverage and behavior could keep evolving, and developers building production systems on top of them should plan accordingly.