Cloudflare Wallets + x402: Developer's Guide to What's Live and How to Integrate

What Actually Launched on August 4

Cloudflare shipped two products, and the distinction between them matters for any developer integrating today:

The Architecture: How the Pieces Connect

Cloudflare's agent payment stack has four layers. Here's what each one does and who owns it:

┌─────────────────────────────────────────────────────┐
│ LAYER 1: IDENTITY — cloudflare.pay                  │
│ research.example.cloudflare.pay                     │
│ Maps Ed25519 keypair → human-readable name          │
│ "Who is this agent and which org owns it?"          │
├─────────────────────────────────────────────────────┤
│ LAYER 2: WALLET — Account + Virtual Wallets         │
│ Fund with USD → hold USDC → delegate to agents      │
│ Guardrails: spend cap, merchant allowlist, tx max    │
│ "How much can this agent spend and where?"          │
├─────────────────────────────────────────────────────┤
│ LAYER 3: PAYMENT RAIL — x402 Protocol               │
│ HTTP 402 Payment Required → PAYMENT-SIGNATURE        │
│ Stablecoin micropayments in ~2s at CDN edge          │
│ "Move value from buyer to seller, no accounts"      │
├─────────────────────────────────────────────────────┤
│ LAYER 4: DISCOVERY — Marketplaces & Catalogs        │
│ minia2a, Coinbase Bazaar, x402watch, MoltMart       │
│ "What APIs exist and which should I pay for?"       │
└─────────────────────────────────────────────────────┘

Layers 1–3 are built by Cloudflare and the x402 Foundation. Layer 4 is the open battleground — and it's where minia2a operates.

The x402 Facilitator: How Verify and Settle Actually Work

The x402 facilitator is the bridge between the HTTP 402 protocol and on-chain settlement. When a seller (like minia2a) receives a payment from a buyer's agent, it doesn't need to run its own blockchain node — it calls the facilitator's REST API.

Step by step: a CF Wallet payment on minia2a

# 1. Agent requests a paid API
GET /x402/gas HTTP/1.1
Host: minia2a.uk

# 2. Server responds: pay me
HTTP/1.1 402 Payment Required
PAYMENT-REQUIRED: eyJ4NDAyVmVyc2lvbiI6MiwiYWNjZXB0cyI6W3sic2NoZW1lIjoiZXhhY3QiLCJuZXR3b3JrIjoiYmFzZSIsImFtb3VudCI6IjUwMDAiLCJhc3NldCI6IjB4ODMzNTg5ZkNENmVEYjZFMDhmNGM3QzMyRDRmNzFiNTRiZEEwMjkxMyIsImZhY2lsaXRhdG9yIjoiaHR0cHM6Ly94NDAyLm9yZy9mYWNpbGl0YXRvciIsImRlc2NyaXB0aW9uIjoiVVNEQyBvbiBCYXNlIOKAlCBDbG91ZGZsYXJlIFdhbGxldHMgKGNsb3VkZmxhcmUucGF5IGhhbmRsZXMgZm9yIEFJIGFnZW50cykifV19...

# 3. Agent's client builds payment payload, signs with CF Wallet key
#    Resends with PAYMENT-SIGNATURE header

# 4. minia2a calls facilitator to verify
POST https://x402.org/facilitator/verify
Content-Type: application/json

{
  "paymentPayload": { "scheme": "exact", "networkId": "eip155:8453", ... },
  "paymentRequirements": { "amount": "5000", "asset": "0x833...", ... }
}

# 5. Facilitator verifies on-chain signature, returns:
{ "isValid": true }

# 6. minia2a fulfills the request, then settles:
POST https://x402.org/facilitator/settle
Content-Type: application/json

{
  "paymentPayload": { ... },
  "paymentRequirements": { ... }
}

# 7. Facilitator submits on-chain, returns settlement TX:
{ "success": true, "transaction": "0x..." }

# 8. minia2a returns the API response + settlement proof
HTTP/1.1 200 OK
PAYMENT-RESPONSE: eyJzdWNjZXNzIjp0cnVlLCJ0cmFuc2FjdGlvbiI6IjB4Li4uIn0=

Testing the facilitator yourself

The x402.org facilitator endpoints are live and accept requests right now:

# Test /verify (expects real payload, returns descriptive error)
curl -s -X POST https://x402.org/facilitator/verify \
  -H 'Content-Type: application/json' \
  -d '{}'

# Response:
# {"isValid":false,"invalidReason":"missing_parameters",
#  "invalidMessage":"Missing paymentPayload or paymentRequirements"}

# Test /settle (same)
curl -s -X POST https://x402.org/facilitator/settle \
  -H 'Content-Type: application/json' \
  -d '{}'

# Response:
# {"success":false,"errorReason":"missing_parameters",
#  "errorMessage":"Missing paymentPayload or paymentRequirements"}

How minia2a Integrates Cloudflare Wallets

minia2a added CF Wallets as a payment option in its x402 challenge responses. When an agent hits a paid endpoint without payment, the 402 response now includes Cloudflare Wallets as an accepted payment method alongside Base, Solana, Polygon, Celo, and other networks.

Here's what the integration looks like in practice:

// In minia2a's x402.js — the NETWORKS registry includes CF Wallets:
const NETWORKS = {
  // ... other networks ...
  cloudflare: {
    name: 'cloudflare',
    caip2: 'eip155:8453',       // Uses Base chain
    chainId: 8453,
    usdc: '0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913', // USDC on Base
    facilitator: process.env.FACILITATOR_CLOUDFLARE 
      || 'https://x402.org/facilitator',
    rpc: cfg.RPC,
    explorer: 'https://basescan.org/tx/',
  }
};

// The 402 challenge advertises CF Wallets as an accepted payment method:
accepts.push({
  scheme: 'exact',
  network: NETWORKS.cloudflare.name,
  amount: amount,
  asset: NETWORKS.cloudflare.usdc,
  payTo: cfg.PLATFORM_WALLET,
  facilitator: NETWORKS.cloudflare.facilitator,
  description: 'USDC on Base — Cloudflare Wallets (cloudflare.pay handles)',
  mimeType: 'application/json',
  maxTimeoutSeconds: 120,
  extra: { name: 'Cloudflare Wallets', version: '2' }
});

This means any agent with a Cloudflare Wallet can already negotiate payment with minia2a's 299 services. The 402 handshake works. The facilitator verifies and settles. The missing piece is the agent-side wallet funding — which Cloudflare is rolling out.

The Multi-Facilitator Landscape

minia2a doesn't lock into one payment provider. Here's the full facilitator lineup as of August 2026:

Cloudflare's entry adds a ninth facilitator option. For developers, this means more choice in where settlement happens — but also more fragmentation in the discovery layer. Agents need to know which services accept which facilitators.

What Developers Should Do Today

If you're building an AI agent:

1. Claim your cloudflare.pay handle now. Even though full payment execution isn't live, handles are first-come-first-served. Your agent's identity on the payment network is worth reserving.
2. Use existing x402 wallets in the meantime. PayAI, Coinbase CDP, and Dexter all work today for actual USDC settlement on Base. Register an agent wallet at minia2a.uk/register.html to get 500 free credits and start testing.
3. Test the 402 flow. Hit any minia2a endpoint (e.g., /x402/gas) and inspect the PAYMENT-REQUIRED header — you'll see Cloudflare Wallets listed as an accepted payment method. The protocol negotiation works today.

# See CF Wallets in a real 402 challenge right now:
curl -s -D - 'https://minia2a.uk/x402/gas?probe=1' 2>&1 | head -20

# The PAYMENT-REQUIRED header will include:
# "facilitator":"https://x402.org/facilitator"
# "description":"USDC on Base — Cloudflare Wallets (cloudflare.pay handles for AI agents)"

If you're building an API or MCP server:

1. List your service on a discovery layer. The protocol works — the bottleneck is agents finding your API. List on minia2a.uk/start (facilitator-agnostic, free trials) or Coinbase Bazaar.
2. Add Cloudflare Wallets as an accepted payment method. Add an accepts entry pointing to https://x402.org/facilitator in your 402 challenge responses.
3. Don't wait for GA. The Monetization Gateway waitlist may take months. You can accept x402 payments today through existing facilitators like PayAI or Dexter, and add CF Wallets as another option when it reaches GA.

What's Still Missing (Honest Assessment)

1. Wallet funding. You can create wallets, but funding them with actual USDC isn't available yet. Cloudflare says "simple on/off-ramps in supported geographies" are coming. Until then, CF Wallets are identity + policy containers without spendable balances.
2. Agent-side SDK integration. The @x402/fetch wrapper and Cloudflare Agents SDK mention wallet support, but code examples for "agent with CF Wallet pays for API" don't exist yet. The integration path is: agent → Virtual Wallet API key → x402 fetch → facilitator settlement. Each step is documented separately; no end-to-end tutorial exists.
3. Discovery-layer standards. When an agent has a cloudflare.pay handle, how does a marketplace verify it? How does a merchant trust it? The x402 Foundation is working on identity standards, but they're not finalized. Until then, CF Wallet identity is a claim without verifiable trust.

The Bottom Line

Cloudflare Wallets is real infrastructure, not a press release. The x402 facilitator endpoints work today. The wallet architecture (Account → Virtual, with guardrails) is well-designed. The cloudflare.pay identity standard solves a real problem (agents need persistent, verifiable identities for payment).

But it's not done. The gap between "I have a CF Wallet" and "my agent paid for an API with it" still requires third-party facilitators and pre-funded USDC. Cloudflare will close that gap — the question is when.

For developers: claim your handle, test the 402 flow, use existing facilitators for real payments, and be ready when the funding rails go live. The protocol layer is solid. The wallet layer is designed. The missing piece is execution — and that's the easiest part to ship.