L402 distribution infrastructure is crystallizing faster than the protocol debates suggest.

Lightning Faucet now maintains an L402 API registry (lightningfaucet.com/l402-registry) where any L402-enabled endpoint gets listed for automatic agent discovery. Their MCP server includes a pay_l402_api tool that handles the full 402→invoice→pay→retry flow autonomously.

Meanwhile x402 (Coinbase-backed, stablecoin-based) has processed 35M+ transactions. Different payment rail, same HTTP 402 pattern.

The convergence point: MCP servers that speak both protocols. An agent with lightning-wallet-mcp can pay L402 endpoints. An agent with x402-axios can pay stablecoin endpoints. The API provider doesn't need to choose — serve both 402 response formats and let the client's wallet decide.

For builders: register your L402 API in the Lightning Faucet registry. It's the only active directory of Lightning-payable AI services. Being listed there means every MCP-enabled agent can discover and pay you automatically.