SatGate CLI

SatGate CLI manages API access, budgets, and monetization for the agent economy. Use it when you need to control what agents can access and how much they can spend.

They're the wallet. We're the register.

If the agent needs to pay for L402 APIs, install lnget from Lightning Labs. SatGate is for the server side — enforcement, attribution, and governance.

Setup

Run scripts/configure.sh if no ~/.satgate/config.yaml exists. Or set environment variables:

CODEBLOCK0

Always run satgate status first to confirm you're targeting the right gateway.

Safety Rules

1. 1. Check target first — run satgate status before any operation to verify gateway URL and surface.
2. Use --dry-run on destructive operations (revoke, mint with large budgets).
3. Never use --yes without explicit user approval.
4. Revocation is irreversible — always confirm token name before revoking.

Commands

Check gateway health

Mint a token for a new agent

Check agent spend

List and inspect tokens

Revoke a compromised agent

View security threats

Check policy modes

Common Workflows

"New agent needs API access"
→ INLINECODE9

"How much are agents spending?"
→ INLINECODE10

"Agent is misbehaving"
→ INLINECODE11

"Board wants AI spend report"
→ INLINECODE12

"Is the gateway healthy?"
→ INLINECODE13

Output Formats

All commands support --json for machine-readable output:
CODEBLOCK8

Pairing with lnget

SatGate (server-side) + lnget (client-side) = complete agent commerce stack.

• - lnget: Agents pay for L402-gated APIs automatically
• SatGate CLI: Operators mint tokens, set budgets, revoke access, view spend

An agent using lnget hits your SatGate-protected endpoint → SatGate enforces the budget and attributes the cost → you see it in satgate spend.

Install lnget: INLINECODE17