x402 roadmap

AllowKit is leaning fully into agentic payment safety: Cloudflare makes resources payable, x402 makes payments internet-native, and AllowKit makes agent spending safe. This is the sequence, not a committed timeline — private-beta escrow and policy ship first, x402-native middleware and MCP support build on top of it.

Phase	Status	Description
00 · Narrative alignment	In progress	Positioning, docs, and demo name Cloudflare Monetization Gateway and x402 explicitly.
01 · x402 buyer SDK	Planned	@allowkit/x402 — automatic 402 detection, payment-requirement parsing, policy check, payment signing, retry with proof, and receipts.
02 · MCP paid tool support	Planned	@allowkit/mcp — a tool-call payment wrapper with per-tool policy.
03 · Cloudflare Gateway compatibility	Planned	A guide and sample app showing an agent paying a Cloudflare-gated resource end to end, with receipts carrying gateway metadata.
04 · Team and enterprise controls	Planned	Teams, roles, per-agent and per-team budgets, approval workflows, webhooks, and exportable audit logs.
05 · Ecosystem partnerships	Planned	Presence across x402 facilitators, MCP directories, agent frameworks, and stablecoin/wallet infrastructure.

Where we are today

Phase 00 is in progress: positioning, docs, and the demo dashboard now name Cloudflare Monetization Gateway and x402 explicitly. Phases 01+ are engineering work not yet started — the SDK snippets referenced throughout these docs are illustrative, not installable.