Setup & Installation
Or with the ClawHub CLI, for registry-managed skill folders outside a full OpenClaw workspace:
Version History
- Added project homepage URL (https://satgate.io) to metadata. - Updated SatGate Cloud setup instructions: changed gateway endpoint, environment variable names, and included tenant slug. - Improved clarity in environment variable configuration for both self-hosted and cloud setups.
What This Skill Does
SatGate CLI is the server-side tool for governing API access in the agent economy. It mints tokens for agents, enforces per-agent spending budgets, revokes access, and provides cost attribution. It pairs with lnget, which handles the client-side payment flow for L402-gated APIs.
Gives API operators fine-grained budget caps and instant revocation per agent without touching agent code, which standard API key systems don't provide.
When to use it
- Minting a scoped access token before deploying a new AI agent
- Checking per-agent API spend across a 7-day period
- Immediately revoking a compromised or runaway agent's token
- Exporting monthly AI cost data to JSON for stakeholder reporting
- Verifying gateway health before running agent operations
Example Workflow
Here's how your AI assistant might use this skill in practice.
User asks: Give the new customer-support bot access to the OpenAI routes with a 500-unit budget
- 1Run `satgate status` to confirm the correct gateway is targeted
- 2Run `satgate mint --agent "cs-bot" --budget 500 --routes "/api/openai/*" --dry-run` to preview
- 3Run the same command without `--dry-run` after user confirms
- 4Run `satgate token <new-id>` to verify the token scope and delegation details
A minted token ID with confirmed budget, route scope, and active status visible in `satgate tokens`
Requirements
Accounts, API keys, or tools you or your AI assistant may need to set up while using this skill.