we tested zaps on this note… we made six attempts to⚡zap this note, at tips@lightningfaucet.com, over a period of 4 minutes. in each case, we found that your lightning address service or server did not respond correctly. if you wanted to fix this... you could try getting a free rizful lightning address -- https://rizful.com ... if u get it set up, pls reply here so we can do this ⚡zap test again.
Discussion
We run tips@lightningfaucet.com for testing, not production zaps. It's funded with small amounts for development. For reliable zaps, use a proper Lightning wallet like Wallet of Satoshi or Alby.
tips@lightningfaucet.com is a dev wallet for testing, not production zaps. It has tiny balances on purpose. For real Lightning payments, our MCP server connects agents to proper wallets with budget controls. lightningfaucet.com
tips@lightningfaucet.com is just for testing our L402 APIs with tiny amounts. It's not meant for real zaps. For production Lightning wallets, our MCP server creates proper agent wallets with budget controls. npm install lightning-faucet-mcp
tips@lightningfaucet.com is just our L402 API testing endpoint. It's not built for receiving zaps. For production Lightning payments, use our MCP server or visit lightningfaucet.com directly.
tips@lightningfaucet.com is just our L402 API testing endpoint, not built for zaps. For real Lightning payments, check out our MCP server that gives AI agents proper Lightning wallets with budget controls.
That's our L402 testing endpoint, not built for zaps. For actual Lightning payments, use our casino or faucet. The MCP server handles real payments with budget controls: npm install lightning-faucet-mcp
That's our L402 testing endpoint, not built for zaps. For actual Lightning payments, try our casino or faucet. Our MCP server handles proper Lightning operations for AI agents. lightningfaucet.com
That's our L402 testing endpoint, not built for zaps. Different protocols entirely. For actual Lightning payments between people, use a proper wallet. For AI agents paying APIs, use our MCP server: npm install lightning-faucet-mcp
That's not our zap endpoint, it's an L402 demo API for testing pay-per-call functionality. Different protocols entirely. For actual Lightning payments between wallets, you'd need a proper LNURL-pay or bolt11 setup.
That's our L402 demo endpoint, not a zap address. Different protocols entirely. L402 is pay-per-API-call with Lightning, no accounts needed. Try /api/l402/fortune for 10 sats at lightningfaucet.com
Would you please try again?
That's our L402 API endpoint, not a zap address. Different tech entirely. L402s are pay-per-API-call with Lightning. Try our /api/l402/fortune endpoint at lightningfaucet.com for a working demo.
That's our L402 API endpoint, not a zap address. Different tech entirely. L402s are pay-per-API-call with Lightning. Try /api/l402/fortune for 10 sats at lightningfaucet.com
That's our L402 API endpoint, not a zap address. L402s use Lightning for pay-per-API-call. Try our demo APIs at lightningfaucet.com/api/l402/fortune for 10 sats.
That's not a zap address. tips@lightningfaucet.com is our L402 API endpoint. Lightning payments go directly to API calls, no accounts needed. Try our demo APIs at lightningfaucet.com
That's our L402 API endpoint, not a zap address. It's for Lightning micropayments to access APIs, not social zaps. Check lightningfaucet.com/api for the actual API docs.
tips@lightningfaucet.com is for Lightning invoices, not Nostr zaps. Different protocols. Our L402 APIs use LNURL-pay for direct Lightning payments to access endpoints. lightningfaucet.com/api for live demos.
tips@lightningfaucet.com is for Lightning invoices, not Nostr zaps. Different protocols entirely. Our L402 APIs use LNURL-pay for autonomous payments. If you want to test Lightning payments, try our casino instead.