Phase 1 · Current
Website, docs, terminal preview
Launch api20.xyz with project overview, developer documentation, interactive terminal preview, registry preview, and public roadmap.
Roadmap
API20 is an early experimental discovery and testing layer. This roadmap outlines planned phases — timelines are indicative and subject to change.
Phase 1 · Current
Launch api20.xyz with project overview, developer documentation, interactive terminal preview, registry preview, and public roadmap.
Phase 2 · Completed
Public registry.json, API detail pages, structured metadata fields, curl and HTTP 402 examples, and GitHub documentation repo.
Phase 3 · Planned
Probe real endpoints and parse x402 payment requirement fields including network, asset, amount, scheme, and resource metadata.
Phase 4 · Planned
Agent tool documentation, payment-aware metadata, and future MCP server compatibility research. No live MCP server today.
Phase 5 · Planned
Enable API builders to submit and list x402-compatible endpoints with verified pricing, network, and MCP-ready status.
Research · Builder Codes
Explore how Builder Codes can be represented in API20 registry metadata to help identify apps, APIs, and agent workflows associated with x402 traffic on Base. Not live settlement integration. See Builder Codes Research.
Phase 6 · Research
Track Machine Payments Protocol and Tempo models as future research — not a live feature. See MPP / Tempo Research.
Phase 7 · Future
Publish an installable CLI tool for scan, inspect, registry, and MCP metadata preview. Not live yet.
Phase 8 · Future
Structured agent mode output for AI tools and automation pipelines — autonomous discovery and payment flow preparation.
API20 is in Phase 2–3. Phase 2 (registry metadata layer) is complete as a demo/static preview. The installable CLI package, real payment execution, official MCP server, Builder Code settlement integration, and MPP/Tempo integration are not live.
Disclaimer: API20 is an independent experimental project. It is not affiliated with Coinbase, Base, Coinbase Developer Platform, Tempo, Stripe, or any official x402, MCP, or MPP organization. References are for ecosystem compatibility, research, and educational purposes only.