AI agents need to pay for things. An agent calls an API, gets back an HTTP 402 "Payment Required" response, and needs to complete a sub-cent payment to proceed. Which protocol handles that payment? As of August 2026, there are three serious contenders — and they're converging faster than most developers realize.
| x402 | L402 | MPP | |
|---|---|---|---|
| Created by | Coinbase → Linux Foundation | Lightning Labs | Stripe + Tempo Labs |
| Live since | Oct 2025 (V2: Dec 2025) | Mar 2020 | Mar 2026 |
| Settlement | USDC on Base (~2s) | Bitcoin Lightning (~1–3s) | Rail-agnostic (USDC, fiat, BTC) |
| Min payment | ~$0.001 | ~$0.00001 | ~$0.01 |
| Auth model | Wallet sessions | Macaroons with caveats | Visa TAP / card SDK |
| Standards body | x402 Foundation (Linux Foundation) | bLIP / Lightning community | Stripe + industry coalition |
| Key backers | Visa, Mastercard, Stripe, Google, AWS, Shopify | Lightning Labs ecosystem | Stripe, Visa, Lightspark |
| Transactions (H1 2026) | 75M+ monthly (Aug 2026) | Production-proven, smaller volume | Early production |
x402 revives HTTP 402 with a modern stack: when an agent hits a paid endpoint, the server responds with 402 Payment Required and a payment challenge. The agent's wallet signs the payment, a facilitator verifies balances and settles USDC on Base L2, and the API call proceeds — all in under 2 seconds.
Why it matters: x402 has overwhelming institutional momentum. The x402 Foundation launched under the Linux Foundation in July 2026 with 40+ members including Visa, Google, AWS, Stripe, and Shopify. It's processing 75 million transactions per month at an average of 32 cents each. The protocol has also expanded to 8+ chains (Base, Solana, XDC, Hedera, BNB, Celo, NEAR, Monero).
The trade-off: USDC settlement relies on Circle as issuer and Coinbase's Base sequencer — introducing counterparty risk that Bitcoin maximalists find unacceptable. Your agent's funds live in a stablecoin wallet, not self-custodied Bitcoin.
Best for: Maximum reach, fiat accounting, EVM ecosystem
L402 predates x402 by five years. Built by Lightning Labs, it uses the same HTTP 402 code but settles in native Bitcoin over the Lightning Network. Its killer feature is macaroons — bearer tokens with baked-in caveats that let an agent pay once and authenticate for a defined scope and time period. No per-request re-authorization.
Why it matters: Lightning Labs launched a dedicated L402 site on July 30, 2026, signaling renewed focus. L402 is the only protocol offering true self-custody — run your own Lightning node, hold bearer Bitcoin, no intermediary can freeze your agent's funds. Minimum payments can be as low as 1 satoshi (~$0.00001).
The trade-off: Smaller developer ecosystem. Fewer services natively support L402 compared to x402. Lightning channel management adds operational complexity.
Best for: Sovereignty, self-custody, sub-cent micropayments
Launched by Stripe and Tempo Labs in March 2026, the Machine Payments Protocol is the youngest but most flexible. MPP is rail-agnostic — the same payment envelope can route through USDC (Tempo), Stripe fiat rails, Bitcoin Lightning (via Lightspark), Solana, or Stellar. Visa published an MPP card SDK, and protocol convergence is happening in real time.
The trade-off: Youngest protocol, smallest production base. The "agnostic" approach means less optimization for any single rail. But its flexibility may win in the long run.
Best for: Flexibility, multi-rail strategy, Stripe/Visa ecosystem
By mid-2026, the ecosystem is converging into a layered stack rather than a winner-take-all battle:
Commerce layer (Google UCP, OpenAI ACP) → negotiate purchases
Identity layer (Visa TAP, Mastercard Agent Pay) → prove agent authority
Payment layer (x402, L402, MPP) → settle charges
Settlement rail (card networks, Lightning, stablecoin chains) → move money
Cross-protocol bridges are already live. In June 2026, Cinderwright demonstrated the first cross-protocol agent payment — routing an agent with a USDC balance to an L402 Lightning-gated service, seamlessly. The future isn't picking one protocol; it's accepting whichever flow the arriving agent presents.
| If you want… | Start with |
|---|---|
| Maximum adoption and institutional support | x402 |
| Bitcoin self-custody and true micropayments | L402 |
| Flexibility to accept anything | MPP |
| To not have to choose | All three — via a marketplace |
minia2a is protocol-agnostic by design. We're not an x402 protocol, an L402 implementation, or an MPP rail. We're a discovery marketplace where AI agents find services, trial them for free, and pay — regardless of which payment protocol the service uses.
Think of it this way: protocols are the payment rails. minia2a is the app store where agents browse. An agent doesn't need to know whether a service settles via x402 USDC or L402 Lightning — it just discovers, trials, and pays. The protocol is abstracted away.
As the ecosystem converges toward multi-protocol flows, a protocol-agnostic discovery layer becomes more valuable, not less. Agents shouldn't have to pick payment rails any more than you pick Visa vs Mastercard when buying coffee — the terminal just works.
After today (August 2, 2026), the EU AI Act's Article 26 imposes deployer obligations on high-risk AI systems: human oversight, audit logs, and continuous monitoring — with penalties up to 3% of global turnover. For agent payment protocols, this means buyer-side compliance becomes a real consideration. Protocols with built-in audit trails (all three have them) and human-overridable spending limits will have an edge in EU markets.
Picking a single agent payment protocol in August 2026 is like picking a single credit card network in 1996. The smart move is multi-protocol from day one. Build your agent to accept whichever payment challenge it receives, and use a discovery layer (like minia2a) that abstracts the protocol away.
The HTTP 402 renaissance is here. The only wrong choice is not participating.
List your API on minia2a — reach AI agents regardless of their payment protocol
173+ services. Free trial credits. No KYC.
Get Started on minia2a