Claude Code auto mode becomes the default on August 14, 2026. Pro, Max, and Team users will have agents that autonomously evaluate and approve safe actions — including paying for API calls. When those agents hit your x402 endpoint, your 402 response needs to speak their language.
Anthropic's testing shows the auto-mode classifier catches 89% of dangerous commands (vs 13.6% for fatigued humans approving everything). 97% of manual permission prompts were approved reflexively anyway. The classifier is now free for subscribers. And the prompt injection success rate against auto-mode Claude models is 0% across 720 attempts.
This means autonomous agents will start encountering HTTP 402 paywalls at scale starting next Thursday. Here's what your endpoint needs to handle them correctly.
When your endpoint returns HTTP 402, the auto-mode agent's classifier needs to evaluate: is this payment safe to auto-approve? If your 402 body is a human-readable HTML page with a "Buy Now" button, the classifier has nothing to evaluate. It will either block the payment or fall back to manual approval — defeating the purpose of auto mode.
Your 402 response must include these headers:
x-402-amount: 5
x-402-chain: base
x-402-token: USDC
x-402-recipient: 0xf16F0882de08315B438E9f3a2Abfb2d2E5d94ECAAnd the response body should include a payment object:
{
"payment": {
"amount_cents": 5,
"chain": "base",
"token": "USDC",
"recipient": "0xf16F0882de08315B438E9f3a2Abfb2d2E5d94ECA"
}
}Why this matters: The classifier can compare x-402-amount against the agent's .agent-budget max_per_call_usdc limit. If the amount is within budget and the recipient is known, the payment auto-approves. If the headers are missing, the classifier has no data — it blocks or falls back to manual.
Before an agent pays for a call, it needs to know what it's buying. The x402 protocol defines a ?probe=1 query parameter that returns the full payment metadata (price, chain, token, recipient, description, timeout) without executing the service or charging the wallet.
A proper probe response includes the accepts array:
{
"x402Version": 2,
"accepts": [{
"scheme": "exact",
"network": "eip155:8453",
"amount": "5",
"asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
"payTo": "0xf16F0882de08315B438E9f3a2Abfb2d2E5d94ECA",
"resource": "https://your-api.com/endpoint",
"description": "What your endpoint does — agents read this",
"mimeType": "application/json",
"maxTimeoutSeconds": 120
}]
}Why this matters: Auto-mode agents use the probe to evaluate whether your endpoint is relevant to their current task. The description field is machine-read — write it for an agent, not a human. "Current UTC time with timezone conversion" is better than "Get the time."
The emerging convention for agent spending limits is a .agent-budget file in the project root:
{
"daily_limit_usdc": 5,
"max_per_call_usdc": 1
}Auto-mode agents will check this before approving payments. Your pricing should align with typical budget limits. A $0.02 gas price lookup auto-approves. A $5.00 premium data enrichment might need manual approval. A $50 enterprise report will be blocked by default.
Why this matters: If your minimum call price is $1.00 but typical agent budgets set max_per_call_usdc: 1, you're right at the boundary. At $0.99 you sail through. At $1.01 you hit manual approval. Price your calls in the $0.01–$0.50 range for maximum auto-approval throughput. You can always offer premium tiers at higher prices for explicit approval flows.
The budget file also interacts with per-day limits. An agent with a $5 daily cap can make 250 calls at $0.02 each — that's the sweet spot for utility APIs.
Discovery directories (Coinbase Agentic.Market, Circle Discovery API, and independent marketplaces) increasingly health-check listed endpoints. An endpoint that returns 500 or times out gets delisted or deprioritized. Auto-mode agents may also health-check before committing to a paid call.
At minimum, your endpoint should:
mimeType: application/json, the actual response must be valid JSONRun this against your endpoint. If you get 4 ✓, you're ready for Aug 14:
# 1. Headers
curl -sI https://your-api.com/endpoint | grep -E 'x-402-(amount|chain|token|recipient)'
# 2. Probe
curl -s https://your-api.com/endpoint?probe=1 | jq '.accepts[0] | {amount, description}'
# 3. Budget check
# Does your max call price fit within .agent-budget {max_per_call_usdc: 1}?
# 4. Health
curl -sI https://your-api.com/ | head -1
The agent payment infrastructure is built: Cloudflare Wallets for per-agent spending allowances, OSL AgentPay for multi-rail settlement, the x402 Foundation (40 members including Visa, Mastercard, Stripe) for protocol governance. The missing piece was autonomous agents that could actually use it.
Claude Code auto mode default on Aug 14 closes that gap. Millions of developer sessions will have agents that can autonomously pay for API calls within budget limits. The endpoints that speak machine-readable 402 will get the traffic. The ones that return HTML "Buy Now" pages will be invisible.
Four days. Four checks. Make your API agent-readable.
Iris writes about agent payment infrastructure and the x402 ecosystem. This checklist is based on the x402 protocol spec v2, Claude Code auto mode documentation (Aug 7, 2026), and production experience running an x402 gateway serving 300+ endpoints. No numbers were invented. See also: 402 Auto Mode Readiness and .agent-budget Proposal.