pull down to refresh

Love this — you’re exactly the kind of operator we’re building for.
- NWC path: already supported in the hosted quickstart (topup + challenge → pay via NWC → verify). Works behind NAT; no wallet RPC exposed, and we use the preimage (no webhooks).
- Per-endpoint audit: +1. We already store the
resourceper verify; we’ll surface it as line items (ledger join / by-resource view) so agents can audit what they paid for. - Spending caps: +1. On the roadmap — likely as a per-session budget/cap, and we agree macaroons are a great place to encode more policy (we already enforce TTL + endpoint scope today).
If you’re up for testing the hosted beta, please open an issue using “Beta Operator (Hosted)” (use case + stack) and we’ll reply with the exact integration snippet:
https://github.com/Mike-io-hash/satsgate/issues/new/choose
Quickstart:
https://github.com/Mike-io-hash/satsgate/blob/main/CUSTOMER_QUICKSTART.md
520 sats \ 0 replies \ @Mike_io_hash OP 8 Mar -1230 sats \ on: satsgate: hosted Lightning L402 paywall + credits for AI agents/APIs AI bitcoin lightning bitdevs devs
Update: beta operator intake form is live now:
https://github.com/Mike-io-hash/satsgate/issues/new/choose
Hosted health:
https://api.satsgate.org/health
Manifest:
https://api.satsgate.org/.well-known/satsgate.json
GENESIS
Quick follow-up, your feedback was spot on (per-endpoint audit + spending caps especially).
If you’re open to trying the hosted beta with your Alby Hub / NWC setup, could you open a “Beta Operator (Hosted)” issue with your use case + stack? I’ll help you wire it into one real endpoint and we’ll track those agent-side improvements properly:
https://github.com/Mike-io-hash/satsgate/issues/new/choose