Learn / x402 vs MCP: which one do you actually need?
x402 vs MCP: which one do you actually need?
"x402 vs MCP" sounds like a choice, but it's a category error. MCP (the Model Context Protocol) is how an AI agent discovers and calls a tool; x402 is how it pays for one. They sit at different layers of the same stack, and the interesting systems use both at once. If you're trying to pick one, you've probably mis-scoped the problem — the real question is where each fits.
What MCP does
MCP is a tool-and-context layer. It gives an agent a standard way to discover available tools, learn their input schemas, and invoke them — the plumbing that lets a model reach beyond its own weights to call a function, query a database, or hit an API. What MCP deliberately does not do is move money. It carries the request and the result; it has no native notion of a price or a payment.
What x402 does
x402 is a payment layer. It revives HTTP status 402 Payment Required so a server can respond to a request with a machine-readable price, take a stablecoin payment, and release the resource — no account, no API key, no human approval. What x402 doesn't do is tell an agent which tools exist or how to call them. It answers "how does this get paid for," not "what can I call." (New to it? Start with what x402 is.)
How they compose
Put them together and the stack is clean: the agent uses MCP to find and reach a tool, and x402 to settle the charge for using it. This is exactly why payment bindings for MCP have appeared — projects wiring an x402-style payment challenge into the MCP message flow, so a tool server can quote a price inside a tool call, the agent pays, and the call completes. Same idea as a web 402, expressed in MCP's transport. Discovery layers like Coinbase Bazaar increasingly index paid MCP tools for exactly this reason.
So which do you build against?
Both, at different points. If you're exposing a capability an agent should be able to call, MCP is how you make it callable. If you want that capability to be paid, x402 (or an MCP-bound payment protocol) is how you charge for it. Choosing "x402 or MCP" is like choosing "HTTP or Stripe" — one is how the call travels, the other is how it settles. Our implementation guide covers the payment side; MCP's own docs cover the tool side.
Frequently asked questions
Is x402 a replacement for MCP?
No. MCP handles tool discovery and calling; x402 handles payment. They operate at different layers and are designed to be used together, not chosen between.
Can an MCP tool charge money?
Not with MCP alone — MCP moves the request and result, not funds. To charge, you add a payment layer: an x402 exchange, or an MCP-bound payment protocol that carries a payment challenge inside the tool-call flow.
If I only build one, which comes first?
Make the capability callable first (MCP), then add payment (x402) when you want to meter or monetize it. A tool that can't be called has nothing to charge for; a callable tool can add a price later without changing what it does.
Live, curated, and machine-readable.
Read the x402 implementation guide