SatGate is the economic control plane for AI agents. Observe, budget, and charge for every request — before it touches your API.
Drop-in gateway. Sub-ms overhead. Start in Observe mode — enforce when ready.
Agents badge in once. Every request — verified, metered, budget-enforced.
See how it worksAgents spend without limits. SatGate stops that. 30 seconds.
First, govern your own house. Then open the gates — on your terms.
Always-on for non-PUBLIC routes
Every protected route requires valid credentials (Macaroons). Capabilities, caveats, delegation, and revocation—built into the protocol, not bolted on.
Your Agents
verify → allow → meter/log
Start here. No workflow changes. No budget enforcement yet. Just visibility.
verify → enforce budget → allow
Now enforce it. Hard budget caps — when it hits zero, agents stop.
Their Agents — when you're ready
verify → payment proof → allow
Open your API to the autonomous agent swarm — on your terms.
API keys are all-or-nothing. Delegated capability tokens let you set any budget, scope, and expiry per agent — and agents can't escalate beyond what they're given. Trust flows down, never up.
PUBLIC is the explicit opt-out for probes (/healthz), docs, and webhooks. Everything else is protected by default.
Agents get a credential at startup — like mounting an EZ Pass. Every request after that flows through the gateway: verified, metered, no slowdowns.
No identity lookups on the hot path. No per-request auth round-trips. Just cryptographic verification at wire speed.
Google DeepMind's recent research on intelligent AI delegation concludes that agents need attenuated capability tokens — specifically macaroons — to safely delegate tasks across trust boundaries. They propose Delegation Capability Tokens with cryptographic caveats that restrict what each sub-agent can access.
SatGate already does this.
Agents only get the permissions they need, attenuated at each delegation layer.
Per-agent and per-route economic policy, enforced before upstream execution.
When limits hit, requests stop. Not after billing. Now.
We didn't build this because of a paper. We built it because it's how machine-to-machine authorization has to work. The research just confirms the architecture.— Tomasev et al., 2026
Three deployment modes. Drop-in. No rip-and-replace.
REST, GraphQL, any HTTP endpoint
Route only agent traffic through SatGate
Per-tool budgets, delegation trees
Four steps to protect your API. No code changes required.
Define routes with economic policies. PUBLIC for probes/docs, protected for everything else.
routes:
- path: /healthz
policy: public
- path: /v1/*
policy: observe
- path: /premium/*
policy: chargeApply when ready. Version history + audit log. Rollback if needed.
v3 (applied) ← current v2 (available) v1 (available) Audit: who, when, diff
Use *.satgate.cloud or your custom domain. Traffic flows through SatGate.
# Your domain api.yoursite.com CNAME → satgate.cloud # Or use ours yourapp.satgate.cloud
Real-time: verified vs challenged. Enable Charge policy when ready for revenue.
Verified: 1,203 requests Challenged: 12,847 (402s) Metered: $847 usage → Enable Charge policy?