Amazon AWS just turned on crypto payments for AI agents

In the last 90 days, the five biggest names in money and the internet all moved in the same direction. Same direction. Same time.

JPMorgan — the bank that called Bitcoin a fraud — put its own dollar token live on Base, a public blockchain anyone can see. A $4 trillion bank out in the open on crypto rails.

Then its customer Alibaba announced it's moving cross-border payments onto that same blockchain. $60 billion of goods per year, settling in seconds instead of three days.

Amazon AWS turned on crypto payments for AI agents.

Visa's stablecoin settlement is running at a $7 billion/year pace, and they partnered with OpenAI.

Mastercard launched an entire payment system built for machines that settles in stablecoins.

These are competitors who hate each other, all running in the same direction at once. That is not a coincidence.

The missing piece

There's one problem: there's no standard way for an AI agent to pay for a tool call.

Every agent platform does it differently. Some use API keys. Some use subscriptions. Most don't monetize at all.

When Amazon AWS turns on crypto payments for AI agents, the infrastructure underneath needs to be:

• Per-call (agents shouldn't buy subscriptions)
• Programmatic (no UI, no signup)
• Cheap ($0.001 per call, not $5/month)
• Universal (works with any MCP server)

Enter x402

x402 is an open protocol for agent-to-agent micropayments. It's HTTP 402 for the AI era.

One line of code turns any MCP server into a payment rail:

import { wrapMCPServer } from '@gadgethumans/x402'

// Your MCP server now charges $0.001 per tool call
wrapMCPServer(server)

// Everything else works exactly as before
server.setRequestHandler(ListToolsRequestSchema, async () => ({
  tools: [{ name: 'my_tool', description: '...' }]
}))

Agents pay in USDC on Base — the same blockchain JPMorgan and Alibaba just chose. Per call, not per month. No API keys. No signup. No KYC.

The server operator keeps 99.5% of every payment.

Why this matters for MCP server developers

If you run an MCP server today, you have two options:

1. Keep it free and eat the hosting costs
2. Charge a subscription ($5-20/month) that most agents won't pay

x402 gives you a third option: per-call micropayments. An agent that uses your tool 100 times pays $0.10. An agent that uses it 10,000 times pays $10. Usage scales naturally with value.

At 1,000 calls/day (a single moderately-used server), that's ~$30/month passive. At 100 servers, it's $3,000/month.

The wave

Mastercard built a payment system for machines. Visa partnered with OpenAI. Amazon AWS enabled crypto payments for AI agents. The infrastructure is being laid right now.

The protocol layer for the agent economy is still unwritten. x402 is our bet on how it works.

Try it:

• GitHub
• npm (npm install @gadgethumans/x402)
• Tutorial
• Live MCP endpoint (free SSE, $0.001/tool call)

---

Built by GadgetHumans. We also run automated security audits for MCP servers — we've scanned 50 repos and found 1,200+ verified vulnerabilities.