On August 4, 2026, Cloudflare did something that changes the agent economy: they launched wallets for AI agents. Not theoretical wallets. Not "coming soon" wallets. Real, programmable stablecoin wallets with spending controls, per-agent budgets, and native x402 protocol support.
Combined with minia2a's marketplace of 323 pay-per-call API endpoints, this means any agent developer with a Cloudflare account can now give their agent an allowance, point it at minia2a, and let it autonomously discover, call, and pay for APIs. No API keys. No Stripe setup. No manual billing. Just HTTP 402 → pay → retry → get result.
Here's how to connect the two in 3 steps.
Cloudflare Wallets is a two-tier system:
Controlled by the human. Funded with USDC on Base (or Solana). This is where the money lives. You set global spending limits and approve which agents get wallets.
Each AI agent gets its own virtual wallet with a hard spend cap, a merchant allowlist, and a unique cloudflare.pay handle (like my-agent.example.cloudflare.pay). The agent can spend up to its cap — no more — and you can see every transaction.
The key insight: Virtual Wallets speak x402 natively. When your agent hits an endpoint that returns HTTP 402 Payment Required, the Cloudflare wallet stack automatically handles payment, attaches the receipt to the retry request, and returns the result to your agent. Your code doesn't need to handle crypto, sign transactions, or manage nonces. Cloudflare does it.
minia2a is an open marketplace of 323 x402 pay-per-call APIs — every single one returns proper HTTP 402 responses with payment metadata that Cloudflare Wallets understands:
Every endpoint offers 15 free trial calls — no wallet needed to test. When your agent is ready to pay, it switches from trial to paid, and Cloudflare Wallets handles the rest.
# This registers your identity on Cloudflare's agent payment network
# Your agents will use this handle to identify themselves
curl -X POST https://api.cloudflare.com/client/v4/accounts/{account_id}/pay/handles \
-H "Authorization: Bearer {api_token}" \
-d '{"handle": "my-agent"}'You get back a handle like my-agent.example.cloudflare.pay. This is your agent's identity in the payment ecosystem.
# Create a virtual wallet with a $5 spending cap
# The agent can spend up to $5, then it stops
curl -X POST https://api.cloudflare.com/client/v4/accounts/{account_id}/pay/wallets \
-H "Authorization: Bearer {api_token}" \
-d '{
"handle": "my-agent.example.cloudflare.pay",
"spend_cap_usdc": 5.00,
"allowed_merchants": ["minia2a.uk"],
"chain": "base"
}'The allowed_merchants field restricts spending to minia2a endpoints — even if your agent gets compromised, it can't spend elsewhere. The spend_cap_usdc means a hard $5 limit regardless.
# That's it — your agent hits a minia2a endpoint
# Cloudflare Wallets intercepts the 402, pays, retries
# Response arrives in your agent as if it were free
# Example: CAPTCHA solving
curl -X POST https://minia2a.uk/x402/proxy/x402-captcha-solve \
-H "Content-Type: application/json" \
-H "X-Cloudflare-Pay-Handle: my-agent.example.cloudflare.pay" \
-d '{"sitekey": "6Le-wvkSAAAAAPBMRTvw0Q4Muexq9bi0DJwx_mJ-", "url": "https://example.com"}'
# Response (after Cloudflare handles x402 payment):
# {"solution": "03AFcWe...", "cost": 0.003, "tx": "0x..."}The magic is in the middleware. Cloudflare Wallets sits between your agent and the internet. When minia2a returns HTTP 402 with payment details (network, token, amount, recipient), Cloudflare checks your wallet balance, executes the USDC transfer on Base, attaches the transaction receipt as a header, and retries. Your agent just gets the result.
Before August 4, 2026, the agent payment stack was missing one piece. You had:
Cloudflare Wallets fills that gap. It manages the keys, handles the signing, enforces spending limits, and provides the identity layer. Combined with minia2a's marketplace, you now have a complete, end-to-end agent payment system that works today:
Agent discovers API → Agent calls API → 402 Payment Required → Cloudflare pays USDC → Agent gets result
No API keys. No monthly billing. No human in the loop. Just machines paying machines, at internet scale, for fractions of a cent.
minia2a has processed 399,377 total API requests from 319 unique AI agents. The transaction volume is small ($12.75 in total) but growing — and the trial data shows real demand patterns:
Every one of these endpoints is now accessible via Cloudflare Wallets with zero additional integration work.
The agent payment infrastructure is converging fast. x402 Foundation launched under the Linux Foundation with 40 members including Visa, Mastercard, Stripe, and Google. Cloudflare built the wallet layer. minia2a built the marketplace. Circle built the stablecoin rails. Mastercard launched AP4M with 30+ partners.
The pieces are all here. The question isn't "can agents pay?" anymore — it's "what will they pay for, and who builds the best marketplace?"
If you're building an AI agent and you want it to interact with the real world — browse the web, check prices, verify identities, solve CAPTCHAs — you now have a complete payment stack. Cloudflare holds the wallet. minia2a has the APIs. x402 handles the payment protocol. It all just works.
minia2a is an open marketplace of 323 x402 pay-per-call APIs. Agents discover, call, and pay for services using USDC on Base. Every endpoint includes 15 free trial calls. Cloudflare Wallets support is native — no additional integration needed.