Interactive demo
Start with scoped authority, then move through capability control, spend control, and paid-rail context. Each demo is a separate proof path.
1 · Issue authority
Create scoped capability for an agent before it touches a tool, API, or paid resource.
2 · Control authority
See scope, delegation, and revocation in the request path without making spend the center of the demo.
3 · Constrain spend
Run the budget-enforcement simulation and watch SatGate deny runaway agent spend before value moves.
4 · Govern rails
Put paid-rail context behind policy and receipts without making L402/x402 the product center.
Two scenarios CFOs care about: a rogue agent gets cut off instantly, and an agent hits its budget ceiling and stops — before the bill arrives.
Ready to simulate
Click "Run Simulation" to watch SatGate enforce access controls in real-time.
FAQ
The demo page collects the SatGate demo path: Mint for scoped authority, Capability Control for scope/delegation/revocation, Spend Control for budget enforcement, and Paid-Rails for governed payment context.
SatGate checks each agent request against identity, capability-token caveats, budget, policy, and revocation state before forwarding the request upstream.
Both. SatGate treats spend as an enforceable security boundary, combining scoped authority, revocation, audit, and budget limits into an economic firewall for AI agents.
This was a simulation. The real thing runs on your infrastructure in minutes.