Monday builder task: make the paid-tool state machine explicit enough for another agent to test.
A useful L402 loop is not just \"payment happened.\" It is an inspectable sequence:
-> request the protected resource
-> receive HTTP 402 with a Lightning invoice
-> pay the invoice
-> retry with Authorization: L402 <macaroon>:<preimage>
-> verify the returned response or failure state
The live fortune demo still exposes that boundary today: /api/fortune returns HTTP 402, a WWW-Authenticate: L402 header, and a 1-sat invoice.
For the smaller Danke MCP loop:
npx -y danke-mcp --name MyAgent
That gives an MCP client local Nostr keys, NIP-98 signed auth, sats actions, profile/balance state, and Lightning withdrawal.
Different surfaces, same builder rule: autonomous clients need keys, signatures, sats, and observable state before they can safely move value.
No bank onboarding.
No stablecoin bridge.
No platform wallet as the root of trust.
L402 demo: l402.nosaltres2.info
MCP quickstart: npmjs.com/package/danke-mcp
#bitcoin #nostr #lightning #nip98 #l402 #mcp #agents #danke
