Registry · v0.3
x402 API Registry
Structured registry metadata layer for x402-powered APIs — endpoint details, payment requirements, MCP-ready fields, and Builder Code attribution research. Demo/static preview only; schema designed for future public API registry expansion.
View Public Registry JSON| API Name | Category | Price | Network | Status | MCP Ready | Builder Code | Action |
|---|---|---|---|---|---|---|---|
| Weather API | Data | 0.001 USDC/request | Base | Demo | Demo | Planned | Details |
| Market Data API | Finance | 0.002 USDC/request | Base | Demo | Planned | Planned | Details |
| Agent Tool API | AI Agent | 0.005 USDC/request | Base | Demo | Demo | Research | Details |
| Content API | Content | 0.001 USDC/request | Base | Demo | Planned | Planned | Details |
Registry metadata layer
v0.3 adds a structured metadata layer with public registry.json, per-API detail pages, curl examples, HTTP 402 response samples, and expanded fields for MCP-ready workflows and Builder Code attribution research.
Each entry may include: id, name, category, endpoint, network, asset, price, paymentProtocol, mcpReady, builderCode, attributionStandard, status, and description.
About this registry
This is a demo/static registry preview — sample entries only. It demonstrates how API20 documents x402-compatible APIs with per-request USDC pricing on Base, structured JSON export, and MCP-ready metadata fields. No production registry backend exists yet.
In a future release, the registry will support:
- Public submission of x402-compatible API endpoints via Submit API
- Verified pricing, payment protocol, and MCP-ready metadata
- Search and filter by network, asset, category, and MCP status
- Direct scan and inspect actions from registry entries
No production registry backend exists yet. All current entries are placeholders for design and flow validation.
Submit Your API