Gateway
Discovery document
GET /.well-known/agent-commerce — merchant, adapters, pinned spec versions and the settlement destination.
GET
/.well-known/agent-commercepublicWhat this gateway is and what it can do: merchant, enabled protocols, every adapter's pinned specification and capabilities, and the effective settlement destination. If the documentation and this endpoint ever disagree, the endpoint is the truth.
curl -s http://localhost:8080/.well-known/agent-commerceAdapter descriptor
namestringrequiredkindprotocol | payment | storage | authorizationrequiredimplementationVersionstringrequiredVersion of the adapter, independent of the spec.
supportedSpecstringrequiredThe exact pinned specification revision.
capabilitiesstring[]requiredunsupportedstring[]What is explicitly not implemented — the same list
doctor prints.statusstable | experimental | plannedrequiredpayments.x402.mode is the derived deployment mode: local, testnet or mainnet. The RPC URL is withheld on purpose — providers put API keys in the path.