composewith.eth
Protocol record · production

x402

HTTP-native payment protocol for programmatic stablecoin payments, API monetization, paid content, and agent-to-service commerce.

89readiness / 100
integration: mediumbasepolygonarbitrum-one

Also available as JSON · Markdown

Resources

docsdocs.cdp.coinbase.comsdkgithub.comtemplatedocs.cdp.coinbase.comsupportdiscord.gg

Good for

Avoid for

Readiness score

89/100

Readiness measures how much verified integration surface exists for builders and agents. It does not mean the protocol is easy to use — integration difficulty is tracked separately.

Docs10/10

Docs URL present

SDK8/8

SDK URL present

Template6/6

Template/quickstart present

Support6/6

Support channel present

Capability depth13/20

HTTP 402 payment flow: integration_workflow; Facilitator verification and settlement: production_surface

Production-ready15/15

Has a production-ready capability

Confidence5/5

Protocol provenance confidence is high

Chain coverage6/10

3 chain(s) (capped at 5)

Freshness10/10

Last verified 7 day(s) ago

No critical issues10/10

No open critical issues

No hard caps applied.

Capabilities

HTTP 402 payment flow production-ready

Best for: servers that return payment instructions with HTTP 402, clients and agents that retry with payment headers, paid APIs and digital goods

  • x402 covers payment authorization and settlement, not marketplace fulfillment, escrow, returns, or dispute handling.

Facilitator verification and settlement production-ready

Best for: sellers that do not want to run blockchain verification infrastructure, ERC-20 stablecoin settlement, multi-network payment acceptance

  • Network, token, facilitator, and transaction-pricing assumptions must be verified before production.

Composes with

erc-8004 agent_identity_and_trust supports

ERC-8004 can provide agent identity, discovery, reputation, and validation around paid x402 service endpoints.

  • agent marketplaces and paid API access

lighthouse-storage storage supports

Lighthouse can store agent-readable manifests, paid-content artifacts, receipts, or service metadata referenced by paid endpoints.

goldsky indexing_and_data supports

Goldsky can index payment, fulfillment, refund, and feedback events for paid service dashboards.

Known issues

x402 does not provide marketplace fulfillment, escrow, returns, or dispute resolution by itself medium confirmed Workaround: Treat x402 as the payment layer. Pair it with marketplace application logic, indexed listing/payment state, admin controls, and explicit fulfillment/refund policies.

Provenance

Last verified 2026-06-03 by composewith.eth research (x402.org, CDP docs, and x402 Foundation GitHub live-verified via WebFetch 2026-06-03) (confidence: high). Score computed by score.v2.