Cowrie Research

x402-primary-sources-2026-04-27

4 min read

x402 primary-source snapshot

Last reviewed: 2026-04-27 UTC

Project status snapshot

What the official materials say

1) Official site

  • URL: https://www.x402.org/
  • Key takeaways:
    • x402 presents itself as an internet-native payments standard, not as a single app or hosted wallet product
    • The site’s core story is that HTTP 402 was always the natural primitive for machine-readable payments and is now practical because stablecoin rails and modern developer tooling exist
    • The homepage explicitly emphasizes agentic payments, open-standard framing, and the existence of a technical whitepaper plus open-source implementation

2) Welcome / overview docs

  • URL: https://docs.cdp.coinbase.com/x402/welcome
  • Key takeaways:
    • The official docs define x402 as a protocol that lets services monetize APIs or content directly over HTTP without accounts, sessions, or conventional auth/payment setup
    • The docs explicitly target both human developers and AI agents as buyers
    • The protocol flow is straightforward: request resource, receive 402 Payment Required, send signed payment payload, then receive the paid resource after verification/settlement

3) Foundation repo

  • URL: https://github.com/x402-foundation/x402
  • Key takeaways:
    • The foundation repo is a major signal that x402 is being framed as a community/open-standard effort rather than a Coinbase-only product surface
    • The repo exposes the multi-language SDK inventory, open-standard principles, flow definitions, extensibility model, and roadmap references
    • The README is also useful because it clarifies the separation of roles among client, resource server, and facilitator

4) Coinbase repo transition note

  • URL: https://github.com/coinbase/x402
  • Key takeaways:
    • The old Coinbase repo now points to the foundation repo, which is useful lineage evidence
    • This transition matters for categorization because it shows the project trying to move from vendor-led launch toward foundation/open-standard stewardship

5) Network support

  • URL: https://docs.cdp.coinbase.com/x402/network-support
  • Key takeaways:
    • x402 v2 uses CAIP-2 identifiers, which is a strong clue that the protocol wants to be chain-agnostic and composable beyond a single network family
    • The reference SDKs support any configured EVM chain and Solana-family environments, while CDP’s hosted facilitator currently focuses on a narrower set of production-supported networks
    • The docs also make it clear that the live protocol supports multiple schemes and multiple token transfer styles, especially EIP-3009 and Permit2 on EVM

6) Facilitator docs

  • URL: https://docs.cdp.coinbase.com/x402/core-concepts/facilitator
  • Key takeaways:
    • The facilitator is positioned as optional but highly practical middleware for verification, settlement, gas sponsorship, and operational simplification
    • The docs explicitly say the facilitator is not meant to be a custodian that holds user funds
    • CDP’s facilitator adds concrete operational features such as KYT screening, hosted infrastructure, and usage-based pricing, which shows how the open protocol is currently packaged for production

7) Bazaar discovery layer

  • URL: https://docs.cdp.coinbase.com/x402/bazaar
  • Key takeaways:
    • x402 is expanding from pure payment transport into discovery and agent-friendly service indexing
    • The Bazaar adds searchable catalogs, semantic search, MCP interfaces, and metadata-rich route declarations for payable APIs
    • This is especially important for research categorization because it means x402 is becoming part payment protocol, part discovery layer for machine-payable services

Whitepaper / technical-doc status

  • Yes: x402 publishes an official technical whitepaper, saved locally as x402-whitepaper.pdf.
  • The whitepaper appears to sit alongside a broader living-docs surface rather than replacing it.
  • In practice, the clearest current operational picture comes from reading the whitepaper, the CDP docs, and the foundation repo together.

Research notes

  • Best current category for the library: HTTP-native payments protocol / agentic payments standard / API monetization infrastructure.
  • The key insight is that x402 should not be cataloged as just another crypto payments API; it is trying to standardize how internet resources become machine-payable over ordinary HTTP.
  • The split between protocol and provider is important: x402 is the standard, while CDP currently operates the most developed hosted facilitator/discovery implementation.

Graph View