Developers Are Asking Hard Questions About Agent Payments. Here Are the Answers.

Yes, tooling exists. Here are three paths, from easiest to most flexible:

Path 1 — Drop-in MCP with built-in payments (5 minutes):

# Your agent gets 306 pay-per-call APIs, payments handled transparently
claude mcp add minia2a -- npx -y minia2a-mcp

Path 2 — paidFetch() for custom agents (10 lines):

// Drop-in replacement for fetch() that auto-pays 402 responses
import { paidFetch } from 'minia2a-mcp';
const res = await paidFetch('https://your-api.com/endpoint', {
  method: 'POST',
  body: JSON.stringify({ query: '...' })
});
// If the API returns 402, paidFetch handles payment automatically

Path 3 — Raw x402 handshake (full control):

# Step 1: Call endpoint normally
curl -s https://minia2a.uk/x402/gas

# If 402, read machine-readable headers:
# x-402-amount: 5 (cents)
# x-402-chain: base
# x-402-token: USDC
# x-402-recipient: 0xf16F...

# Step 2: Your wallet signs and sends 5¢ USDC on Base
# Step 3: Retry request with X-Payment header containing tx hash

The ecosystem has evolved fast. You don't need to implement the handshake from scratch anymore — use paidFetch or an MCP wrapper and focus on your API logic.

This is the #1 friction point reported by developers. The root cause: Claude Code's default permission model requires human approval for spending. Even with auto mode, the agent needs three things before it will pay:

1. A .agent-budget file — without it, the agent doesn't know its spending limits and won't proceed.
2. Machine-readable 402 headers — if the API doesn't return x-402-amount, x-402-chain, x-402-token, and x-402-recipient, the agent can't construct a payment.
3. A working payment path — the agent needs a wallet with USDC on the right chain.

The fix (30 seconds):

# Create .agent-budget in your project root
echo '{"daily_limit_usdc": 5, "max_per_call_usdc": 1}' > .agent-budget

# Verify your API returns proper 402 headers:
curl -sI https://your-api.com/endpoint | grep x-402-

# If you see x-402-amount, x-402-chain, x-402-token, x-402-recipient → ready
# If not → your API needs 402 header support before Aug 14

Check if any API is auto-mode ready in one command:

curl -s https://minia2a.uk/auto-mode-check | bash -s -- https://your-api.com/endpoint

This concern was valid in early 2026, but the landscape has changed dramatically in the last 30 days:

• Cloudflare Wallets (Aug 4) — agents can hold and spend USDC directly through Cloudflare, no Coinbase account needed. Every site behind Cloudflare can now accept agent payments.
• OSL AgentPay (Aug 7) — multi-stablecoin (USDT, USDC, USDGO), multi-protocol (x402, AP2, MPP) settlement. A Hong Kong public company with full compliance.
• PayAI — third-party facilitator, no Coinbase dependency.
• The x402 Foundation — under the Linux Foundation with ~40 members (Visa, Mastercard, Stripe, AWS, Google, Solana Foundation). Protocol governance is multi-stakeholder, not single-vendor.

The protocol specifies what an HTTP 402 response looks like — not who processes the payment. Any facilitator can settle. The headers are chain-agnostic: x-402-chain: base today, x-402-chain: solana or x-402-chain: arbitrum tomorrow.

minia2a itself is facilitator-agnostic: we support Cloudflare Wallets, PayAI, and direct x402. The protocol is the interface; the settlement rail is a choice.

This is the right question to ask. Here are services that are only available via x402 — no API key, no subscription, no human account:

• Glassnode on-chain data (since Aug 6) — pay-per-call blockchain intelligence. No API key. No account. $0.05/metric.
• Arkham blockchain intelligence (since Aug 6) — same model. Pay-per-call entity attribution, portfolio tracking.
• Apify's 20,000 Actors (since Aug 2026) — Instagram scrapers, Google Maps extractors, Amazon crawlers. All x402-payable.
• On-chain transaction decoding — decode any EVM transaction, event log, or calldata. 1¢ per decode.
• Multi-chain gas prices — real-time gas across 15+ chains. No API key needed.
• Polymarket data — live odds, order book depth, market resolution. Pay-per-call.

The pattern: services that are utility-grade — an agent needs them for 30 seconds, not 30 days. A monthly subscription to Glassnode makes no sense for an agent that needs one data point. Pay-per-call does.

Three things change for Claude Code users on Pro, Max, and Team plans:

1. Auto mode becomes the default. Instead of prompting for approval on every tool call, Claude evaluates safety automatically. Safe actions proceed. Risky ones are blocked.
2. Classifier tokens become free. The safety classifier that evaluates each action no longer counts toward token usage.
3. Agents can spend autonomously. Combined with a .agent-budget file, agents can pay for API calls without human approval — as long as the amount is within budget limits.

Enterprise, API, and platform users (AWS Bedrock, Google Cloud, Microsoft Foundry) get auto mode next month.

What to do now:

# 1. Create your budget
echo '{"daily_limit_usdc": 5, "max_per_call_usdc": 1}' > .agent-budget

# 2. Verify your agent can discover and pay for APIs
claude mcp add minia2a -- npx -y minia2a-mcp

# 3. Test with a free trial call (no wallet, no payment)
curl https://minia2a.uk/x402/gas
# → {"gas_prices": {...}, "_trial": true, "trials_remaining": 14}