# x402 vs L402

Both belong to the HTTP 402 family group on this map. The map lists them as complementary: sites and agents commonly implement both.

[7 Pay](/category/pay/) [x402](/protocols/x402/) · [7 Pay](/category/pay/) [L402](/protocols/l402/)

|  | [x402](/protocols/x402/) | [L402](/protocols/l402/) L402 |
| --- | --- | --- |
| Lifecycle step | 7 Pay: Settle the bill | 7 Pay: Settle the bill |
| Answers | How can an HTTP client pay per-request or per-resource, in stablecoins, without accounts, API keys, or signup? | How can a client pay for, and then authenticate to, a metered API resource over the Lightning Network with no accounts or database-backed sessions? |
| Governed by | x402 Foundation, a Series of LF Projects, LLC (Linux Foundation); operational launch announced 2026-07-14; Executive Director Michael Hursta from 2026-10-01; 50+ members | Lightning Labs |
| Status (issuer's words) | Open, neutral standard for internet-native payments | Active, registered as an HTTP Authentication scheme (RFC 7235-style) |
| Phase | living | living |
| Version | x402 protocol specification v2, transports-v2/http.md | current protocol-specification.md on the master branch |
| Form / transport | HTTP header | HTTP header |
| Found at | none — signalled per-request via the 402 status code, not a fixed well-known path | none — signalled per-request, no well-known file |
| Adoption | claimed — x402 Foundation (x402.org live dashboard) | unmeasured |
| Evidence | 5 verified | 2 verified |
| Primary use case | Accept payments from agents | Accept payments from agents |
| Last verified | 2026-10-19 (current) | 2026-10-19 (current) |
| Specification | [https://github.com/x402-foundation/x402/blob/main/specs/transports-v2/http.md](https://github.com/x402-foundation/x402/blob/main/specs/transports-v2/http.md) | [https://raw.githubusercontent.com/lightninglabs/L402/master/protocol-specification.md](https://raw.githubusercontent.com/lightninglabs/L402/master/protocol-specification.md) |

## When to use which

- Choose x402 when your question is “How can an HTTP client pay per-request or per-resource, in stablecoins, without accounts, API keys, or signup?” and you accept its maturity: phase living, adoption claimed (x402 Foundation (x402.org live dashboard)).
- Choose L402 when your question is “How can a client pay for, and then authenticate to, a metered API resource over the Lightning Network with no accounts or database-backed sessions?” and you accept its maturity: phase living, adoption unmeasured.

Guidance is derived from the two records (question, phase, adoption, prerequisites, pairings), not from opinion. Each record's page carries its numbered references.

## Read the full articles

- [x402](/protocols/x402/): How can an HTTP client pay per-request or per-resource, in stablecoins, without accounts, API keys, or signup?
- [L402](/protocols/l402/): How can a client pay for, and then authenticate to, a metered API resource over the Lightning Network with no accounts or database-backed sessions?

Ask the MCP server to compare any two: the compare-protocols prompt, or get on both ids. [Connect](/connect/).

[x402.json](/data/protocols/x402.json) · [l402.json](/data/protocols/l402.json) · [Markdown](/compare/x402-vs-l402/index.md)