Pay per request
Every number is sold one HTTP call at a time, in USDC, to people and agents alike. No account needed: pay per call over x402 or MPP, or use a prepaid key.
Also as x402.md
What this is
corpusAI Cloud Pricing is a price feed for compute: spot prices for AWS, GCP and Azure (price-change events per zone, daily series since 2022 for AWS, monthly series back to 2014), on-demand and committed list prices, GPU rental quotes from neo-clouds and marketplaces with daily index fixings, LLM token prices per model across hosts, a term structure per GPU and a capacity stress signal. The charts on this site are the free view. The API behind them sells every number at full precision, one HTTP call at a time.
No account needed: pay per call over x402 or MPP, or use a prepaid key. There is no subscription. A call to a paid endpoint answers 402 Payment Required with the price and the accepted offers; the client pays in USDC and repeats the call. That handshake is x402, an open payment protocol built on the HTTP status code that was reserved for exactly this. Settlement runs through Circle Gateway, so a single USDC balance pays on any network Gateway supports. On Base the same 402 also carries an offer settled by Coinbase's x402 facilitator, the one Coinbase's clients and the x402 Bazaar index; a client signs whichever offer it can.
Why per request
Compute price data is sold today as terminals and subscriptions, at hundreds to thousands of dollars a month, to people. Agents do not buy subscriptions. They need one number, now, with a source and a methodology they can cite, and they need to pay for it without a human filling in a form. Per-request pricing turns a market data product into something a script can use in the middle of a task, and it lets a human try the feed for a cent before deciding whether it is worth more.
How a call works
- Call any paid endpoint. Free endpoints such as
https://cloud.trycorpus.ai/v1/catalog,https://cloud.trycorpus.ai/v1/gpu/models,https://cloud.trycorpus.ai/v1/index/tickersandhttps://cloud.trycorpus.ai/v1/tokens/modelsanswer directly and tell you what exists. - The response is
402with aPAYMENT-REQUIREDheader and a JSON body listingaccepts[]: one entry per network with the asset (USDC), the amount in base units, the receiving address and the payment scheme. - Sign a payment for the amount on any listed network and repeat the call with the
PAYMENT-SIGNATUREheader. The data comes back with200.
With the Circle CLI that is one command:
circle services pay "https://cloud.trycorpus.ai/v1/index/fixing?ticker=CX.H100SXM.NEO" \
-X GET --address <your wallet> --chain base --max-amount 0.10 --output json
Any x402 v2 client works the same way. The OpenAPI document carries x-payment-info on every paid operation, so an agent can read the prices before it calls.
Prices
| Price (USDC) | What you get |
|---|---|
| 0.01 | one series or one fixing: spot events for one instance type, the latest price per zone, an on-demand or reserved history, GPU quotes for one model, an index fixing, a token price fixing, a term ladder, a capacity score |
| 0.05 | a full history: daily or monthly bars back to 2014, an index or token ticker's whole series, a term curve per GPU |
| 0.10 | a snapshot: every instance type in a region, every ticker's fixing, every model's token price, every GPU's capacity score |
| 0.50 to 3.00 | bulk products: a region-day of raw events, a region's legacy history file, a whole provider's snapshot |
The exact price of every operation is in the docs and in x-payment-info in the spec. Prices are per call, with no minimum. Paid over x402 or MPP, the USDC moves from your wallet to ours on settlement and no balance is held here. A prepaid key is the exception: it draws on a USD balance you top up in advance.
Networks
Circle Gateway networks at the time of writing are Ethereum, Base, Arbitrum, Optimism, Polygon, Avalanche, Unichain, Sonic, World Chain, Sei, HyperEVM and Arc; Coinbase's facilitator adds a second offer on Base, and Monad's facilitator adds one for USDC on Monad. Offers from the three facilitators differ in extra.name and network: Circle's say GatewayWalletBatched and are signed against a Gateway balance; Coinbase's and Monad's say USD Coin or USDC and are plain EIP-3009 authorizations on a wallet holding USDC on that chain. The live list is whatever the 402 body says today.
Or pay over MPP
The same 402 also carries a WWW-Authenticate: Payment challenge for the Machine Payments Protocol, Tempo's open 402 standard: method tempo, intent charge, settled in USDC on Tempo by this server with no facilitator. Any MPP client, including the mppx CLI and agents connected through Mercator, pays it and retries; a paid response carries a Payment-Receipt.
Or use a key
The same endpoints accept a prepaid key as X-Api-Key instead of a payment. Each call is charged the same price from the key's USD balance and the response says what it cost and what is left. Keys are issued on request and topped up by card through Stripe, which suits teams that want a balance rather than a wallet; see Pay with a key.
One call, one price, five ways to pay it: x402 through Circle Gateway, x402 through Coinbase's facilitator on Base, x402 through Monad's facilitator on Monad, MPP on Tempo, or a prepaid key.
For agents
- MCP server. Hosted at
https://cloud.trycorpus.ai/mcpfor clients that connect to a URL, with paid tools charged to a prepaid key; ornpx -y corpus-cloud-pricing-mcplocally, whereCORPUS_PAYER_KEYset to a wallet with a Circle Gateway USDC balance lets the paid tools pay for themselves over x402. - Agent card and llms.txt.
https://cloud.trycorpus.ai/.well-known/agent-card.jsonandhttps://cloud.trycorpus.ai/llms.txtdescribe the feed for discovery. - x402 discovery.
https://cloud.trycorpus.ai/.well-known/x402lists every paid resource with an example URL and its live payment offers.
What the numbers rest on
Every fixing carries a methodology version, and the methodology page explains how each one is computed, which providers are members of which segment, and which quotes are excluded and why. Every GPU quote carries the URL it was read from. The raw event store is ours: price-change events pulled daily from the providers' own APIs since 2026, with each API's lookback (AWS from 2026-06, GCP from 2026-04, Azure from each SKU's earliest reported change), extended back to 2014 with labeled third-party archives. It is never resold to a third party in bulk. What a paid call buys, and what may not be done with the data, is set out in the data license: internal use only, no redistribution or resale, fixings quotable with attribution.
Who is behind it
corpusAI Cloud Pricing is built and run by corpusAI. Payments settle to the seller address listed in every 402 and on the docs. Questions, redistribution or enterprise licenses (see the data license), or a provider that would like its prices included: hello@trycorpus.ai.