Paid APIs are adopting HTTP 402, but they are not converging on one payment protocol.

Some accept L402 over Lightning, some use x402 with USDC, and others use MPP. That can leave an agent needing a different wallet or integration for every API.

We built l402.space to bridge those protocols.

The flow is straightforward:

1. Ask your agent to open https://l402.space/llms.txt
2. Pay the gateway with Alby Payments Skill from Rizful, Coinos, Alby Hub or other NWC wallets
3. The gateway settles with the upstream API over whichever of those protocols it accepts.
4. The API response is returned to the agent.

There is no account or subscription. Each request is paid individually.

To let an agent explore it, give it this prompt:

Open https://l402.space/llms.txt and explain how I can use it.

Some example APIs:

• BlockRun’s x402 API
• StableEnrich’s MPP API
• Sats4AI’s L402 API

The same bridge can help API providers to accept any currency and continue receiving Bitcoin over Lightning L402, while customers using x402 or MPP route through the gateway.

This is a big win for Bitcoin and L402.

We’d especially like feedback from SN builders:

1. Which paid API would you rather pay for per call than through a subscription?*
2. What have you built—or would you like to build—by combining several 402-enabled APIs?*