Generic HTTP proxy to your Alby Hub admin API. Use this when no typed convenience tool exists for the endpoint you need. Returns the response status, headers, and (JSON-parsed when possible) body. Non-GET methods are gated by ALBYHUB_READ_ONLY and ALBYHUB_REQUIRE_CONFIRM. Pair with the Hub's own docs to discover endpoints; the typed wrappers (get_node_info, list_apps, get_balances) are layered on top of this and good defaults to start with.

Execute a previously-prepared non-GET request, identified by its one-time token. Only meaningful when ALBYHUB_REQUIRE_CONFIRM=true. The token is consumed (single use) and the safety pipeline (read-only, rate limit) re-runs before the HTTP call.

Fetch Alby Hub node info (identity, network, version) from GET /api/info. Convenience wrapper. If your Hub returns 404 here, the endpoint path differs in your version — use albyhub_proxy_request to probe alternatives like /api/node or /info.

Fetch hub balances (on-chain + lightning) from GET /api/balances. Distinct from nwc_get_balance — that one is a single sub-wallet's view via NWC; this one is the hub-wide aggregate including on-chain. If your Hub returns 404, probe with albyhub_proxy_request.

List NWC connections / sub-wallets ('apps') currently provisioned on the Hub. Each entry typically includes name, pubkey, scope, daily budget, and creation timestamp. Hits GET /api/apps. Use this to inventory what's connected to your Hub and what each connection's budget cap is.

List Lightning channels — typically peer pubkey, capacity, local/remote balance, public/private flag, online status. Hits GET /api/channels. The hub-wide view (vs. nwc-mcp which has no channel concept). Useful for spotting offline channels, low inbound, etc.