Practical overview
When it fits
Use AgentSafe when consequential HTTP actions need an execution boundary between an agent or API and the target service, with policy decisions delegated to Decionis.
Who it is for
- Teams routing consequential HTTP actions from AI agents or APIs through an authorization checkpoint.
- Operators who want to review requests in shadow mode before enforcing holds or blocks.
- Teams deploying an execution gateway on premises or connecting to the Decionis-managed shadow gateway.
Documented uses
- Intercept an agent or API request before it reaches its target.
- Forward an authorized request once using a single-use grant.
- Hold an action for human review or refuse it according to the authority’s decision.
- Keep chained evidence of authorization decisions and resulting actions.
Requirements & limits
The repository documents a local demo authority that runs on loopback with a synthetic policy without a Decionis key. Connecting to the Decionis control plane uses a Decionis key. The project is licensed under Apache-2.0.
- AgentSafe does not decide whether an action is authorized; it asks the Decionis control plane.
- Human escalation uses Presence in the documented design; the repository’s local Presence double simulates the ceremony and does not prove a real one.
- The documented shadow mode is a review stage before enforcement.
- Supported installation routes include Homebrew, Linux packages, Docker and Helm.
Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.
Run AgentSafe’s local demo gateway
Start the gateway against a local upstream using its loopback demo authority.
Before you start
- AgentSafe is installed.
- A local upstream is available at http://localhost:3000.
Steps
Start the gateway with
agentsafe proxy --upstream http://localhost:3000 --port 8080.Send a request to the gateway, such as the documented POST to
http://127.0.0.1:8080/paymentswith a JSON body containing{"amount": 500}.Review the gateway decision and the response received by the caller.
Expected outcome
The demo authority applies a synthetic policy: the documented $50 payment is allowed and forwarded once; the $500 payment is held for human approval; and the $5000 payment is blocked. A GET passes through untouched.
Guide limitations
- Without a Decionis key, this uses a local demo authority with synthetic policy on loopback, not Decionis.
- The documented example says the held request does not reach the upstream.
- The README indicates evidence is not written by default; use
--verboseorevidence.journalDirfor evidence output.
Sources & review
Source record details
- Source availability
- Active
- Sources checked
- 13 October 2026
- Original website title
- decionis/agent-safe-pipeline · Official homepage title · retained in its source language

