x402Coinbase · agent-servicesvs
Agent Payments ProtocolGoogle · agent-services
The two open answers to 'how does an agent pay?' x402 (Coinbase) revives HTTP 402 for instant stablecoin settlement on Base; AP2 (Google) defines signed mandates that prove authorization over existing card and payment rails.
agentlist.io · documented attributes · sources and dates shown per value
Compare the same attributes
Every entry uses the same category fields. Open a source to check the scope and date behind a value. Not documented means we have no supported value, not that a feature is absent.
| Attribute | x402Awaiting documentation review | Agent Payments ProtocolAwaiting documentation review |
|---|---|---|
| Common attributesDirectory metadata and source-documented values. Not documented is an evidence gap, not a negative claim. | ||
| CategoryAgentlist's buyer category; directory classification rather than a product capability. | Payments | Payments |
| Entry typeDirectory classification distinguishing products, frameworks, infrastructure and protocols. | protocol | protocol |
| Directory coverageHow the entry entered this directory; not a quality rating or a claim that every field is verified. | Cataloged | Cataloged |
| Recorded availabilityAvailability classification in the directory; check the source and review date before relying on current access. | active | active |
| InterfacesDocumented ways a person or application interacts with the entry. | Not documentedRecorded sourcesRecorded catalog specification; availability and terms may have changed. | Not documentedRecorded sourcesRecorded catalog specification; availability and terms may have changed. |
| Execution / hostingWhere the documented service or workload runs; this is not a data-residency guarantee. | Not documentedRecorded sourcesRecorded catalog specification; availability and terms may have changed. | Not documentedRecorded sourcesRecorded catalog specification; availability and terms may have changed. |
| Pricing basisSource-described price and billing basis. Different units and plans are not directly equivalent. | Not documentedRecorded sourcesRecorded catalog specification; availability and terms may have changed. | Not documentedRecorded sourcesRecorded catalog specification; availability and terms may have changed. |
| LicenseDocumented license for the specified component or offering. | Not documented | Not documented |
| PaymentsComparable questions for this category. Sources and dates describe the evidence; no performance ranking is implied. | ||
| Agent paymentsProvides payment, wallet or charging capabilities for agents. | Not documented | Not documented |
| Identity and authorizationProvides identities, credentials or authorization for agent activity. | Not documented | Not documented |
| Spending controlsSupports policy or budget limits on payments. | Not documented | Not documented |
| Payment approvalRequires authorization for designated transactions. | Not documented | Not documented |
| Payment railsExplicitly documented payment networks or settlement mechanisms. | Not documented | Not documented |
| CurrenciesDocumented settlement or transaction currencies. | Not documented | Not documented |
Pick which
pick x402 if
You want working machine-payable endpoints today — USDC on Base, no card network in the middle, minimal ceremony.
pick Agent Payments Protocol if
You need card-network compatibility and explicit user authorization — signed mandates that merchants and issuers already understand.
watch out
They're converging rather than competing — x402-style rails and mandate-signed card payments will coexist; don't hard-code one settlement layer.
Feature notes
- x402
- 01HTTP 402 status as payment handshake
- 02USDC settlement on Base
- 03Client and facilitator SDKs
- 04Middleware for paid endpoints
- 05Open spec with Coinbase backing
- Agent Payments Protocol
- 01Signed intent/cart mandates
- 02Card-network and payment-rail compatible
- 03Verifiable credential chain
- 04Crypto extension via x402 ecosystem
- 05Open protocol
Frequently asked
x402 or Agent Payments Protocol — which should I pick?
The two open answers to 'how does an agent pay?' x402 (Coinbase) revives HTTP 402 for instant stablecoin settlement on Base; AP2 (Google) defines signed mandates that prove authorization over existing card and payment rails. Pick x402 if: You want working machine-payable endpoints today — USDC on Base, no card network in the middle, minimal ceremony. Pick Agent Payments Protocol if: You need card-network compatibility and explicit user authorization — signed mandates that merchants and issuers already understand.
Is x402 or Agent Payments Protocol cheaper?
x402: Open protocol (free); settlement on-chain. Agent Payments Protocol: Open protocol (free). These are recorded catalog prices, not a fresh quote. Check vendor pricing for current plans, usage charges and seat terms.
Does x402 or Agent Payments Protocol run locally?
x402 hosting: local, cloud. Agent Payments Protocol hosting: local, cloud. Interfaces differ too: x402 exposes api, Agent Payments Protocol exposes api.
Are x402 and Agent Payments Protocol still maintained?
Recorded catalog status — x402: actively maintained. Agent Payments Protocol: actively maintained. Check the linked sources for current availability; the catalog's creation date is not a product verification date.