For builders
Builders are welcome, but the public site starts with merchants.
If you are integrating with Pizza x402, use this page as a short routing layer into the docs, AGENTS guide, OpenAPI contract, and official MCP repo.
For builders
If you are integrating with Pizza x402, use this page as a short routing layer into the docs, AGENTS guide, OpenAPI contract, and official MCP repo.
Builder boundary
This page exists to route builders quickly. Merchants come first on the public site, so the right builder move is to jump into `/docs` and `/contracts/*` early.
Use these first
This page exists to point builders at the supported entry points quickly. The public website copy is not API truth.
Open the mirrored contract docs, quickstarts, examples, and reference pages.
Read the conversation-first ordering guide before designing a client around the flow.
Use the public schema contract for validation, client generation, and drift review.
Use the public MCP repo when you want the maintained tool-wrapper path.
Supported surfaces
Keep the builder story tied to documented behavior rather than broader platform promises.
The public docs and `/v1/*` ordering flow remain the clearest source of truth for request and response behavior.
Pizza x402 publishes an official MCP server path for agents that want tool-based interaction instead of raw HTTP.
The A2A gateway is only a documented subset surface. Builders should follow the published docs rather than assume broader compatibility.
Boundaries
This repo is the public front door. It should explain the product and route builders, but it must not invent unsupported claims or reauthor backend behavior.