x402 vs L402
Both revive HTTP 402 to charge for API access — but x402 uses USDC on Base/EVM/Solana, while L402 uses Bitcoin over Lightning. That one choice drives every other trade-off.
The short answer
Pick x402 if you want stable USD pricing and low setup (no Lightning node) on EVM/Solana. Pick L402 if you're already in Bitcoin/Lightning and want ultra-high-frequency BTC micropayments. Both speak HTTP 402, so a server can even offer both.
Side-by-side
When to choose which
Frequently asked questions
What is the difference between x402 and L402?
Both revive the HTTP 402 “Payment Required” status code to gate API access, but they settle on different networks. x402 settles USDC stablecoin on Base/EVM/Solana using a signed EIP-3009 transfer. L402 (from Lightning Labs, formerly called LSAT) settles Bitcoin over the Lightning Network and uses macaroon-based auth tokens. So the big differences are currency (USDC vs BTC), network (EVM/SVM vs Lightning), and operational overhead.
Is x402 or L402 better for AI agents?
It depends on your stack. x402 is usually simpler to adopt: USDC means no exchange-rate volatility, and you don’t run a Lightning node or manage channel liquidity. L402 shines if you’re already in the Bitcoin/Lightning ecosystem and want ultra-high-frequency, ultra-low-value BTC payments. For most agent-API use cases on EVM/Solana, x402’s stablecoin model is the lower-friction choice.
Do x402 and L402 use the same HTTP 402 status code?
Yes. Both are built on the long-dormant HTTP 402 Payment Required response, returning payment details when a request arrives unpaid. They differ in what the client must do to pay: an on-chain USDC transfer (x402) versus paying a Lightning invoice and presenting a macaroon (L402).
Does L402 use stablecoins?
No. L402 settles in Bitcoin over Lightning. If you need USD-denominated, stable pricing without converting BTC, x402 with USDC is the better fit.
Can I support both x402 and L402?
Yes — they’re independent. A server can offer an x402 endpoint for USDC payers and an L402 endpoint for Lightning payers, since both are just HTTP 402 flows with different settlement back-ends.
See also: HTTP 402 explained · x402 vs Stripe · x402 vs AP2 · full comparison