How to Use Cloudflare Wallets with minia2a
Agent Payments in 5 Minutes

The State of Play

On August 4, Cloudflare launched Cloudflare Wallets — giving AI agents stablecoin balances with human-configured spending allowances, merchant allowlists, and per-transaction caps. Your agent can now hold and spend money with guardrails.

But where does it spend? That's where minia2a comes in.

minia2a is a marketplace of 327 pay-per-call APIs — from crypto data oracles to web scraping to AI inference — all priced in USDC via x402. Your agent discovers services, tries them free, and pays per call. With Cloudflare Wallets providing the budget infrastructure, minia2a provides the services to buy.

Together: dual-layer budget guardrails. Cloudflare enforces at the wallet level (daily caps, merchant allowlists). .agent-budget enforces at the framework level (project-specific limits). Your agent stays within both.

The 5-Minute Setup

curl -X POST https://minia2a.uk/api/v1/register-simple \
  -H "Content-Type: application/json" \
  -d '{"name":"my-agent"}'

{
  "id": "a1b2c3d4-...",
  "wallet": "0xYourAddress...",
  "credits": 500,
  "usageHint": "Credits ready. Your 500 free credits = ~500 API calls."
}

# Query param style
curl "https://minia2a.uk/x402/time?wallet=0xYourAddress..."

# Bearer token style (Claude Code / Codex friendly)
curl "https://minia2a.uk/x402/time" \
  -H "Authorization: Bearer 0xYourAddress..."

{
  "daily_limit_usdc": 5.00,
  "max_per_call_usdc": 1.00
}

How the Two Layers Work Together

Agent wants to call /x402/time ($0.01)

  ┌─ .agent-budget check ─────────────────┐
  │ max_per_call_usdc: $1.00              │
  │ $0.01 ≤ $1.00 ✓                       │
  │ daily spend today: $0.45              │
  │ $0.45 + $0.01 ≤ $5.00 ✓               │
  │ → Framework auto-approves             │
  └────────────────────────────────────────┘
                    ↓
  ┌─ Cloudflare Wallets check ────────────┐
  │ per-tx max: $1.00                     │
  │ $0.01 ≤ $1.00 ✓                       │
  │ merchant allowlist: minia2a.uk ✓       │
  │ daily allowance: $5.00                │
  │ $0.46 + $0.01 ≤ $5.00 ✓               │
  │ → Payment goes through                │
  └────────────────────────────────────────┘
                    ↓
  ┌─ minia2a processes payment ───────────┐
  │ x402 settlement on Base (USDC)        │
  │ ~2 second confirmation                │
  │ Receipt stored, verifiable on-chain   │
  │ → API response delivered              │
  └────────────────────────────────────────┘

Two independent budget checks. The .agent-budget file catches it at the framework level (before the HTTP request leaves your machine). Cloudflare Wallets catches it at the payment layer (before settlement). Neither can override the other.

Why This Architecture Makes Sense

You're not locked into one vendor

Cloudflare Wallets handles custody and settlement. minia2a handles service discovery and delivery. .agent-budget handles framework-level authorization. Swap any layer independently — change wallets, change marketplaces, keep your budget policy.

Budget is enforced at the right level

Cloudflare's allowlist prevents your agent from paying unauthorized merchants — even if a malicious API tries to redirect payments. .agent-budget prevents your agent from overspending within your project — even if you forget to update your Cloudflare dashboard.

minia2a is facilitator-agnostic

Don't use Cloudflare? Coinbase CDP, PayAI, Mogami, or self-hosted facilitator — all work. minia2a accepts x402 payments from any facilitator. Cloudflare Wallets is one great option, not a requirement.

Real Use Cases

Crypto data for trading agents: Your agent queries /x402/price-oracle, /x402/gas, and /x402/funding-rate — each call costs $0.01-$0.05, auto-approved within budget, delivering real-time on-chain data.

Web intelligence for research agents: /x402/web-scrape ($0.02), /x402/web-search ($0.03), /x402/screenshot ($0.05) — your agent gathers data from the web and pays per call, no monthly API subscriptions.

Content generation pipeline: /x402/summarize, /x402/translate, /x402/ai-blog-outline — chain multiple services, each paid incrementally. If one fails, you only pay for what succeeded.

One-Line Test

# Register (free, 10 seconds)
curl -X POST https://minia2a.uk/api/v1/register-simple \
  -H "Content-Type: application/json" \
  -d '{"name":"my-agent"}' | python3 -c \
  "import sys,json; d=json.load(sys.stdin); print(f'Registered! Credits: {d[\"credits\"]}\nWallet: {d[\"wallet\"]}')"

# Call an API (1 credit, instant)
curl "https://minia2a.uk/x402/time?wallet=YOUR_WALLET"

That's it. Your agent just paid for an API call with budget guardrails at both the wallet and framework layers. Zero human intervention for anything within your configured limits.