## What this is corpusAI Cloud Pricing is a price feed for compute: spot price events for AWS, GCP and Azure back to 2014, on-demand and committed list prices, GPU rental quotes from sixteen providers 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. There is no sign-up and no subscription, and a key is optional. A call to a paid endpoint answers `402 Payment Required` with the price and the accepted networks; the client pays in USDC and repeats the call. That handshake is [x402](https://www.x402.org/), an open payment protocol built on the HTTP status code that was reserved for exactly this. Settlement runs through [Circle Gateway](https://www.circle.com/gateway), so a single USDC balance pays on any of the eleven supported networks. ## 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 1. 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/tickers` and `https://cloud.trycorpus.ai/v1/tokens/models` answer directly and tell you what exists. 2. The response is `402` with a `PAYMENT-REQUIRED` header and a JSON body listing `accepts[]`: one entry per network with the asset (USDC), the amount in base units, the receiving address and the payment scheme. 3. Sign a payment for the amount on any listed network and repeat the call with the `PAYMENT-SIGNATURE` header. The data comes back with `200`. 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 --chain base --max-amount 0.10 --output json ``` Any x402 v2 client works the same way. The [OpenAPI document](https://cloud.trycorpus.ai/openapi.json) 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 files: a region's full event history, a day's raw events, a whole provider's snapshot | The exact price of every operation is in the [docs](https://cloud.trycorpus.ai/docs) and in `x-payment-info` in the spec. Prices are per call, with no minimum and no account balance held here; the USDC moves from your wallet to ours on settlement. ## Networks Payments are accepted on Ethereum, Base, Arbitrum, Optimism, Polygon, Avalanche, Unichain, Sonic, World Chain, Sei and HyperEVM through Circle Gateway. The live list is whatever the `402` body says today. ## 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. That is the rail for teams that want an invoice and a balance rather than a wallet; see [Pay with a key](https://cloud.trycorpus.ai/docs#pay-with-a-key). ## For agents - **MCP server.** `npx -y corpus-cloud-pricing-mcp` gives any MCP client twenty-eight tools over this API. Set `CORPUS_PAYER_KEY` to a wallet with a Circle Gateway USDC balance and the paid tools pay for themselves. - **Agent card and llms.txt.** `https://cloud.trycorpus.ai/.well-known/agent-card.json` and `https://cloud.trycorpus.ai/llms.txt` describe the feed for discovery. - **Circle Agent Marketplace.** The API is listed on [agents.circle.com](https://agents.circle.com) with a verified live `402` on every paid operation. ## What the numbers rest on Every fixing carries a methodology version, and the [methodology page](https://cloud.trycorpus.ai/methodology) 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, collected by our own jobs since 2024 and extended back to 2014 from labelled archives, and it is never resold to a third party in bulk. ## Who is behind it corpusAI is a small infrastructure company. The feed is built and run by Julian Traversa; the receiving address is `traversa.eth`. Questions, licensing for redistribution, or a provider that would like its prices included: [julian@traversa.dev](mailto:julian@traversa.dev).