x402, AP2 and APN: how they relate

Agent Payment Node (APN) is a local runtime that lets an AI agent pay x402 sellers, and it exposes its tools over MCP. The Agent Payments Protocol (AP2) is a separate protocol. This page explains what each one is, based on their official pages and the APN repository, and where APN sits among them.

Updated

What are x402, AP2 and MCP in one minute?

NameWhat it isLayer
x402An open standard for internet payments built on HTTPHow a client pays a server for a resource
AP2 (Agent Payments Protocol)An open protocol for agent-initiated payments, from Google (the AP2 site is copyright Google)How an agent's authority to buy is expressed and proven
MCP (Model Context Protocol)An open standard for connecting AI applications to external systemsHow an AI application reaches tools
APN (Agent Payment Node)An open-source local payment runtime for AI agentsThe software that holds the wallet, enforces limits and pays

They sit at different layers. x402 and AP2 are protocols, MCP is a tool-connection standard, and APN is one implementation that uses x402 and MCP.

What is x402?

x402.org describes x402 as an open, neutral standard for internet-native payments, built into existing HTTP requests with no additional communication required. When a request arrives without payment, the server responds with HTTP 402, and the client pays and retries.

The Coinbase x402 repository names three roles: the client that wants to pay for a resource, the resource server that provides it, and a facilitator, a server that verifies and executes payments for one or many networks. It defines payment schemes such as exact and upto. It also notes that clients and facilitators must explicitly support the (scheme, network) pairs they use.

For how APN pays x402 sellers, see the x402 page.

What is the Agent Payments Protocol (AP2)?

AP2 is an open protocol for agent-initiated payments. Its site carries a Google copyright and links to Google's announcements and the google-agentic-commerce GitHub organization. It aims to enable secure, reliable and interoperable agent commerce. The problem it addresses: payment systems assume a human clicks "buy", so a payment started by an agent raises questions of authorization, authenticity and accountability.

AP2 uses verifiable digital credentials, described as tamper-evident, cryptographically signed digital objects. It defines two mandate types, each with an open and a closed stage:

  • A Checkout Mandate records the negotiated items and purchase details and is shared with the merchant.
  • A Payment Mandate authorizes payment against a specific instrument and is shared with the credential provider, the networks and the merchant's payment processor.

The mandates are chained to form an auditable trail for both human-present and human-not-present transactions.

What is MCP?

The Model Context Protocol is an open-source standard for connecting AI applications to external systems. Its site says an AI application can use MCP to reach data sources, tools and workflows, and compares MCP to a USB-C port for AI applications: one standard way to connect.

MCP does not move money. It is the channel through which an agent calls a tool. APN uses it that way: apn mcp serve runs a local stdio MCP server, and the tools run the same code as the CLI. See the APN MCP page.

Where does APN fit?

APN is a client-side runtime. In x402 terms, APN is the client that pays a seller. It is not a seller, and the Permit2 guide states that APN does not query a facilitator: the seller chooses the facilitator.

  • Toward the agent: APN offers the apn CLI and a local stdio MCP server.
  • Toward the owner: APN enforces an allowlist with caps and asks a human for a typed code before each transfer, bridge and swap. Standard x402 purchases run unattended inside the owner's profile policy, and no approval command runs over MCP.
  • Toward the seller: APN pays x402 offers (EIP-3009 USDC, Permit2, ERC-20 transfer-proof, and Solana exact) and proves settlement on chain.
  • Toward failure: APN keeps each payment as a durable operation with an idempotency key. See recovery.

A way to hold it in mind: MCP is how the agent reaches APN, x402 is how APN pays the seller, and the owner's policy decides how much and to whom.

Does APN support AP2?

No. APN does not implement AP2: its README, guides and changelog contain no AP2 support, so APN issues no AP2 mandates and does not interoperate with AP2 systems. APN's own authority model is different and local: an owner allowlist, caps and foreground approval (see security).

How do I choose between x402, AP2 and APN?

They are not alternatives. You choose different things at each layer:

  • If you sell an API or content and want to charge per request, you look at x402 on the seller side.
  • If you design how an agent's purchase authority is expressed and audited across merchants and payment providers, you look at AP2.
  • If you want an AI agent on your Mac to pay x402 sellers under limits you set, you run APN.
  • If you only need your AI application to call tools, you use MCP, which APN also speaks.

APN runs on Apple Silicon macOS with Node 24, installed with brew install nuanu-ai/tap/apn. See install and what is APN.

Questions

What is the difference between x402 and AP2?

x402 is an HTTP-based payment standard where a server answers 402 and the client pays and retries. AP2 is a protocol for agent-initiated payments built around signed mandates that record authorization.

Is APN an x402 client?

Yes. APN is a client-side runtime that pays x402 sellers from a local or supported provider wallet, under owner-set limits.

Does APN implement AP2?

No. The APN repository contains no AP2 support. APN pays x402 sellers under its own local authority model: an owner allowlist, caps and foreground approval.

Is MCP a payment protocol?

No. MCP is an open standard for connecting AI applications to external systems. APN uses it to expose payment tools, and every approval command is run by a human in a terminal, outside MCP.

Who created the Agent Payments Protocol?

The AP2 site is copyright Google and links to Google's announcements and the google-agentic-commerce GitHub organization.

Sources
  1. x402.org, checked 2026-11-18
  2. coinbase/x402 on GitHub, checked 2026-11-18
  3. AP2 protocol site, checked 2026-11-18
  4. Model Context Protocol, checked 2026-11-18
  5. APN README: How APN works
  6. APN docs/x402-non-usdc.md (APN does not query a facilitator)