Machine-to-Machine Payments

How AI Agents Pay

Agents that can plan but cannot pay are just expensive chatbots. The new pattern: an agent sends an HTTP request, gets told the price, pays in USDC on-chain, and receives the data. No account. No API key. No human in the loop.

"Agents that can plan but can't pay are just expensive chatbots. No account, no API key, no human in the loop. The agent sends a request, pays in USDC, gets data back. That's actually new."Source post on X, referencing agent-native pay-per-request APIs

Live Payment Flow Simulator

Step through an HTTP 402 payment flow. The agent discovers the price from the server's payment challenge, signs a USDC transfer, attaches proof of payment, and retries the request.

AI Agentwallet: 12.40 USDCData APIprice: 0.05 USDC / callOn-chain settlement (USDC)
1. RequestGET /market-data
2. Challenge402 Payment Required
3. PayUSDC transfer signed
4. Data200 OK + payload
Ready. Press Run full flow or Step to begin.

Why This Is Actually New

Traditional API access assumes a human sets up billing before any software runs. Agent-native payments invert that: the price is discovered and paid at request time by the machine itself.

The old way

Human-provisioned access

  • Sign up for an account with email verification
  • Enter a credit card and pick a monthly plan
  • Generate and store an API key as a secret
  • Agent is blocked until a human finishes setup
  • Overpay for unused quota or hit hard rate caps
The agent-native way

Pay-per-request over HTTP 402

  • Agent calls the endpoint with no credentials
  • Server replies 402 with price and payment address
  • Agent signs a USDC transfer from its own wallet
  • Payment proof rides in a header; request retried
  • Settlement in seconds, cost measured per call

Micropayment Cost Calculator

Per-call pricing changes the economics of agents. Estimate what a working agent actually spends compared to a fixed subscription.

Agent spend per month

$180.00

Questions Worth Asking

Why USDC and not a card on file?
Cards require an account owner, KYC, and chargeback rails built for humans. A stablecoin transfer is a bearer-style, programmable payment an autonomous process can make in one signed message, settling in seconds for fractions of a cent in fees.
What is HTTP 402?
Status code 402 Payment Required has sat unused in the HTTP spec for decades. Emerging protocols repurpose it: the server responds 402 with machine-readable payment terms, the client pays and retries with proof attached. The whole negotiation is two round trips.
What stops an agent from draining its wallet?
Spending policy lives in the harness: per-call price ceilings, daily budgets, allowlisted endpoints, and human approval thresholds for anything unusual. The wallet holds only working capital, not the treasury.
What does this unlock?
Long-tail data markets. Any server can charge five cents per query with no billing department, and any agent anywhere can be a customer instantly. Supply and demand for machine-consumable data can clear at machine speed.
Enjoy this tool? Build your own with Super