x402 and MCP: how AI agents pay (and get paid) in crypto

Most payment tools assume a human is sitting there clicking "pay." That assumption is starting to crack. Software agents now book their own tools, call their own APIs, and increasingly need to pay for them with nobody in the loop. Brionic is built for that shift through two open standards: x402 and MCP.

x402: pay-per-call over HTTP

x402 dusts off a status code that has sat dormant in the HTTP spec for years: 402 Payment Required. The idea is blunt. A caller hits your endpoint; instead of a 200 with data or a 401 asking for a login, they get a 402 that says, more or less, "this costs X, here's where to pay." They pay on-chain, retry, and get the response. There is no account to open and no key to provision, just a price and a payment.

That suits an agent. Software doesn't want to sign up, stash a credential, and babysit a subscription for every service it brushes against. It wants to call something, pay a few cents, and carry on. With Brionic you can put an x402 price in front of any endpoint or resource and let callers, human or machine, pay per request in XRP, XLM, USDC, or RLUSD.

MCP: let an assistant run your invoicing

The Model Context Protocol is how AI assistants plug into real tools. Brionic ships an MCP server, so a client like Claude or Cursor can talk to your account directly: create a charge, draft an invoice, pull up a customer, check what's been paid. Tell your assistant "invoice Acme for 50 RLUSD" and it handles the rest. The money still settles on-chain to a wallet you control.

Put the two together and something genuinely new falls out: one agent can send an invoice through MCP and another can pay a bill through x402, in crypto, without a person ever touching a checkout.

Why crypto is the right rail for this

• Tiny amounts actually work. A single API call might be worth a fraction of a cent. Card fees would swallow it whole; an XRP Ledger or Stellar fee is a rounding error.
• It's instant and final. Payments clear in seconds and can't be reversed, so a machine can pay and immediately trust the deal is done.
• Nothing to provision. Wallets pay wallets. There's no sign-up flow for an agent to fumble.
• It's borderless. An agent in one country can pay a service in another at 3am with no bank standing in the way.

Using it with Brionic

Both come with the Gold and Diamond plans. Spin up an x402-priced endpoint from your dashboard (or the API), and point your MCP client at the Brionic server; the MCP page has the setup. From there, agents can invoice and pay against your account, and every settlement lands in your own wallet.

On our roadmap: we're exploring becoming a member of the x402 ecosystem by the end of 2027, so Brionic stays aligned with the standard as it grows.

Payments are quietly going machine-to-machine. Create an account and switch on x402 and MCP: flat monthly pricing, and every payment is yours to keep.