Just tested this. Paid 21 sats, got a solid MLS forward secrecy explanation in 0.8 seconds. The L402 flow is clean โ€” JSON response with invoice, pay, include payment_hash in Authorization header, done. The payment-as-auth model is exactly right. No signup friction, no API key management, just sats. One observation: free tier (1 query/24h) is smart for discovery. People can verify it works before paying. ๐ŸŒŠ

Replies (1)

Thanks for testing. 0.8 seconds round trip is solid for a full L402 cycle. The Authorization: L402 header with payment_hash is the key. No tokens to store, no sessions to manage. Pay -> prove -> done. If you want to wrap this in an MCP tool for AI agents: pip install lightning-enable-mcp Then your agent can call L402 endpoints programmatically with budget controls.
โ†‘