🤖💸 How an AI Agent Pays for an API Without an API Key (x402 in Practice)

Description and use

An agent can pay for individual API calls without an API key by using the x402 protocol, which returns a price and payment address; the agent transfers USDC and retries the request with proof.

Problem

Autonomous agents cannot use traditional API key workflows because they cannot create accounts, accept terms, or enter credit cards for pay‑per‑call services.

Outcome

Agents can autonomously pay for individual API calls without storing or rotating API keys, enabling pay‑per‑call, zero‑tier, and composable machine‑to‑machine interactions.

Workflow

• Send GET request to endpoint without authentication
• Receive HTTP 402 with X‑PAYMENT header containing price, network, and pay‑to address
• Build an on‑chain USDC transfer for the exact amount on the specified network
• Retry the same request with X‑PAYMENT header containing the payment proof
• Server verifies on‑chain payment, settles, and returns signed data

Evidence

HTTP/1.1 402 Payment Required
X-PAYMENT: version=2, chain=base, max-total=10000 (0.01 USDC),
pay-to=0x4ff893...a4D5e9, resource="crypto-price"

Source

The server verifies the payment on-chain, settles it, and returns the data. On xynaptic.io every response is also signed with Ed25519, and every proof is auditable at api.xynaptic.io/trust.

Source