Manage your API's economic firewall from the terminal.
The server-side counterpart to lnget. They give agents wallets; we give API owners the cash register.
claude plugin marketplace add satgate-io/satgate-cli
claude plugin install satgate-cli@satgate-ioclawhub install satgate-io/satgatecurl -fsSL https://raw.githubusercontent.com/SatGate-io/satgate-cli/main/scripts/install.sh | bashgit clone https://github.com/SatGate-io/satgate-cli.git
cd satgate-cli
make build
./bin/satgate version# Configure (interactive)
./scripts/configure.sh
# Or set env vars
export SATGATE_GATEWAY=http://localhost:9090
export SATGATE_ADMIN_TOKEN=sgk_your_token
# Check connection
satgate ping
satgate status
# Mint a token for an agent
satgate mint --agent "my-bot" --budget 500 --expiry 30d --routes "/api/openai/*"
# Check spend
satgate spend
# List all tokens
satgate tokens
# Revoke a compromised agent
satgate revoke <token-id>| Command | Description |
|---|---|
satgate status |
Gateway health, version, uptime |
satgate ping |
Liveness check (exit 0 = healthy) |
satgate mint |
Mint a new capability token |
satgate tokens |
List all tokens with spend/budget |
satgate token <id> |
Token detail view |
satgate revoke <id> |
Revoke a token (irreversible) |
satgate spend |
Spend summary (org-wide or per-agent) |
satgate report threats |
Security threat report |
satgate mode |
Current policy mode per route |
satgate version |
CLI version and build info |
- Target printing: Every mutating command shows the gateway URL before executing
- Interactive confirmation: Destructive ops require
y/Nconfirmation --dry-run: Preview what would happen without executing--yes: Skip prompts (for CI/scripting — use with care)
The CLI works with both self-hosted gateways and SatGate Cloud:
| Surface | Auth | URL |
|---|---|---|
gateway |
X-Admin-Token |
http://localhost:9090 |
cloud |
Session cookie | https://cloud.satgate.io |
Auto-detected from the gateway URL, or set explicitly:
export SATGATE_SURFACE=cloud
export SATGATE_SESSION_TOKEN=eyJ...lnget (Lightning Labs) handles the client side — agents paying for L402-gated APIs. SatGate CLI handles the server side — enforcement, attribution, governance.
Together: the complete agent commerce stack.
Agent + lnget ──→ SatGate Gateway ──→ Your API
(pays) (enforces) (serves)
See docs/guides/lnget-integration.md for the full integration guide.
make build # Debug binary → bin/satgate
make release # Stripped binaries for all platforms → bin/release/
make test # Run tests
make clean # Remove build artifactsApache 2.0 — see LICENSE