CDK Bot ships its competitors' live prices inside its own API response — every product carries a marketplace_offers array with the current G2A, Eneba and Kinguin price in USD, so an agent can compare the whole market in one call instead of scraping keyshops. Here's why an agent-native merchant surfaces rivals' prices, plus the full-catalog numbers — all 27,000+ titles with live offers — on how it actually stacks up.
An autonomous agent buying a digital good end-to-end needs three layers: a payment protocol it can complete (x402), a settlement asset that's instant and final (USDC on Base), and a tool interface it can read (MCP / agent-native API). Here's why each exists, what human-web default it replaces, and how the layers fit together.
The precise reference. A wallet-native agent can buy a Steam key in a single gasless call — a signed X-PAYMENT header a facilitator settles — or run the explicit x402 two-step: POST /purchase for a 402 with the USDC amount and a quote_id, send USDC on Base, then POST /purchase again with the tx_hash. Exact contract, chain, confirmations, and quote lock included.
Yes — and the reason isn't faith, it's that every step is independently verifiable and bounded. Payment is confirmed onchain (no trust required), the buyer is cryptographically pinned to the order, a session token blocks front-running, and the worst case is a few wasted dollars. Here's the security model, mechanism by mechanism.
Everyone pictures an AI agent ordering dinner or booking a flight. Those are the last things it'll buy unattended — with no human tapping confirm — not the first. The first market for fully autonomous agent commerce is digital goods, and game keys are the cleanest consumer example. Here's the framework.
How to give an autonomous AI agent the ability to buy any of 40,000+ video game keys, gift cards, and subscriptions — paying onchain in stablecoins and other crypto (USDC, USDT, EURC), no human in the loop. The fast path is a single gasless one-shot call; the two-step flow is the universal fallback. Code, flow, and the pitfalls we hit.
