- CollectionCommerce & Payments
- Classificationagent-native
- MCPUnknown
- Agent SkillUnavailable
- InterfacesREST · SDK · http
What it does
x402 revives HTTP 402 Payment Required for machine-to-machine payments: a client requests a resource, the server responds with payment terms, the client pays (typically stablecoin on EVM or Solana via facilitator), and retries with proof. Coinbase Developer Platform provides a facilitator (verify/settle), SDKs, and Bazaar as a discovery layer for x402-enabled endpoints — aimed at AI agents and autonomous API consumers paying per call without human checkout.
Agent-facing interfaces
- Catalog protocols: REST, SDK, http
- MCP: ⚠️ Not a standalone MCP product — any MCP agent that performs HTTP can participate in x402 payment flows.
- Agent Skill: ⚠️ No official AgentSkills bundle located; integration is SDK + HTTP middleware.
- Onboarding type:
sdk
How agents onboard
# Example: Python SDK per coinbase/x402 README
pip install x402
See the full onboarding section in the dossier.
Protocol surface
| Interface | Detail |
|---|---|
| HTTP | x402 challenge/response on any compliant host |
| SDKs | https://github.com/coinbase/x402 |
| CDP REST | Facilitator endpoints per docs |