GPU markets / inference pricing / agent compute
The compute market is becoming tradable.
A neutral map of how GPUs are priced, where compute is rented, how inference turns hardware into tokens, and how x402-style payments could let agents buy small units of compute directly.
Market Board
checked 2026-07-06
Key facts
Verdict
Compute is now bought in four overlapping markets.
The buyer can rent raw accelerators, buy a managed model API, accept live marketplace risk, or pay for a narrow compute result. Those markets share hardware, but they optimize for different things. Training clusters optimize for synchronized capacity. Inference APIs optimize for latency, batching, and quality. GPU marketplaces optimize for price discovery. Agent-native services optimize for machine-readable, per-call settlement.
This site does not rank vendors. It explains the units and tradeoffs so a buyer can ask the right question: not "what is the cheapest GPU?" but "what is the cheapest reliable way to finish this workload under these constraints?"
Free calculators
Estimate GPU-hour cost, compare dated GPU prices, and model rough inference cost.
Hyperscalers
Enterprise controls, quota, regions, IAM, data gravity, and calculators.
GPU-first clouds
Clearer accelerator catalogs and cluster products for training and inference teams.
Peer and decentralized
Live supply, host choice, interruptible economics, bids, and benchmark-hour markets.
The map
Use How Compute Is Priced to normalize GPU-hour, token, request, storage, and egress meters. Use The Marketplaces to understand the provider categories without vendor shilling. Use Inference vs Training Markets to separate long-running accelerator demand from low-latency serving economics.
Use the GPU Cost Estimator, GPU Price Compare, and Inference Throughput Cost Calculator when you need a working worksheet rather than another static explainer.
The agent page, Agent-Native Compute, intentionally stays in the compute lane. It links out to x402-specific references for payment details and focuses on what machine payments change for compute procurement.
What to verify before buying
- The exact GPU model, VRAM, interconnect, region, and trust tier.
- The billing unit and whether it changes by batch, priority, cached input, output, or interruption risk.
- Storage, data transfer out, idle workers, cold starts, and support terms.
- The measured cost per useful unit on your workload, not a generic provider benchmark.
Sitemap