x402Coinbase · agent-servicesvsAgent 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.

x402 versus Agent Payments Protocol: shared and category-specific attributes
Attributex402Awaiting documentation reviewAgent 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.PaymentsPayments
Entry typeDirectory classification distinguishing products, frameworks, infrastructure and protocols.protocolprotocol
Directory coverageHow the entry entered this directory; not a quality rating or a claim that every field is verified.CatalogedCataloged
Recorded availabilityAvailability classification in the directory; check the source and review date before relying on current access.activeactive
InterfacesDocumented ways a person or application interacts with the entry.Not documented
Recorded sources

Recorded catalog specification; availability and terms may have changed.

Not documented
Recorded sources

Recorded catalog specification; availability and terms may have changed.

Execution / hostingWhere the documented service or workload runs; this is not a data-residency guarantee.Not documented
Recorded sources

Recorded catalog specification; availability and terms may have changed.

Not documented
Recorded sources

Recorded catalog specification; availability and terms may have changed.

Pricing basisSource-described price and billing basis. Different units and plans are not directly equivalent.Not documented
Recorded sources

Recorded catalog specification; availability and terms may have changed.

Not documented
Recorded sources

Recorded catalog specification; availability and terms may have changed.

LicenseDocumented license for the specified component or offering.Not documentedNot 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 documentedNot documented
Identity and authorizationProvides identities, credentials or authorization for agent activity.Not documentedNot documented
Spending controlsSupports policy or budget limits on payments.Not documentedNot documented
Payment approvalRequires authorization for designated transactions.Not documentedNot documented
Payment railsExplicitly documented payment networks or settlement mechanisms.Not documentedNot documented
CurrenciesDocumented settlement or transaction currencies.Not documentedNot documented
SEC.02

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.

SEC.03

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
FAQ

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.

ALT

More comparisons