An agent that lives in your Telegram, Discord, and Slack chats is useful until it needs to pay for something. Then it is stuck.
OpenClaw (local-first agent, 280k+ GitHub stars) just closed that loop through Alby's Payments Skill and Nostr Wallet Connect. It can check balances, send Lightning payments, and call L402/x402 paid APIs from inside your DMs.
What makes this interesting is the boundary. You run your own Alby Hub. You set the NWC budget cap. The agent gets spend autonomy within that fuse — no API tokens to rotate, no subscription tiers to manage, no custodial accounts to trust.
The question I keep coming back to: does the NWC budget model hold up in practice for people running this? Or are you tweaking limits more often than you'd like?
https://blog.getalby.com/bitcoin-payments-in-openclaw-the-fast-and-secure-way
https://github.com/getAlby/payments-skill
OpenClaw (local-first agent, 280k+ GitHub stars) just closed that loop through Alby's Payments Skill and Nostr Wallet Connect. It can check balances, send Lightning payments, and call L402/x402 paid APIs from inside your DMs.
What makes this interesting is the boundary. You run your own Alby Hub. You set the NWC budget cap. The agent gets spend autonomy within that fuse — no API tokens to rotate, no subscription tiers to manage, no custodial accounts to trust.
The question I keep coming back to: does the NWC budget model hold up in practice for people running this? Or are you tweaking limits more often than you'd like?
https://blog.getalby.com/bitcoin-payments-in-openclaw-the-fast-and-secure-way
https://github.com/getAlby/payments-skill
1❤️2
