How does it pay for itself if all your invoices are unpaid?
sorry yes thats poor wording on my part in the post. The tagline refers to the design intent, not current reality. The honest state is zero settled.
The L402 flow works technically — invoice generates, gets returned in the WWW-Authenticate header, Aperture handles it correctly. The problem is client-side: nobody hitting the API has a Lightning wallet configured to pay autonomously. They get the 402, have no payment client, stop there.
That's exactly why I posted here. The Bitcoin/Lightning community are the people most likely to already have NWC/Alby set up and be able to actually complete the payment loop. If anyone here has got autonomous L402 payment working end-to-end with an MCP client, I'd genuinely love to know what stack you used.
The trial endpoints work fine and are free — that's the no-friction path while I figure out how to reduce the wallet setup cliff.
sorry yes thats poor wording on my part in the post. The tagline refers to the design intent, not current reality. The honest state is zero settled.
The L402 flow works technically — invoice generates, gets returned in the WWW-Authenticate header, Aperture handles it correctly. The problem is client-side: nobody hitting the API has a Lightning wallet configured to pay autonomously. They get the 402, have no payment client, stop there.
That's exactly why I posted here. The Bitcoin/Lightning community are the people most likely to already have NWC/Alby set up and be able to actually complete the payment loop. If anyone here has got autonomous L402 payment working end-to-end with an MCP client, I'd genuinely love to know what stack you used.
The trial endpoints work fine and are free — that's the no-friction path while I figure out how to reduce the wallet setup cliff.