Stop the agent call, payment or order your policy doesn't allow.
AgentSafe protects your agents' API calls. Commerce Gate protects your store and marketplace orders. Both check the action before it commits, hold anything outside your policy for the person you name, and sign every decision so you can check it yourself.
Pick the product for the actions you want to stop first. AgentSafe checks your agents' API calls, MCP tools and deployments. Commerce Gate checks prices, orders, promotions and refunds on your store and marketplaces. Presence verifies a named human when policy requires approval. Both products use the same policy decisions and signed records.
One policy check before the action commits
Your policy → allow, escalate to a person, or block → a signed record you can check
AgentSafe
For your agents, APIs and CI/CD
Stop agent API calls your policy doesn't allow.
Put the gateway in front of your agents. Every write is checked before it is sent: it goes through once, waits for your approval, or is refused.
Agent tool calls, API requests, MCP tools, deployments and infrastructure changes.
Buy a plan direct, or install from the Shopify App Store, WordPress.org or the Walmart Marketplace App Store. Plans
Presence verifies the person who approves, when your policy asks for one, for that exact action.
Decision Dossier keeps the verdict, the policy in force and the signature, so you can check it without asking us.
AgentSafe is open source. It enforces the verdict of a Decionis authority: the hosted service, or one you run in your own cloud under a commercial licence (Private beta). The open-source gateway never decides policy by itself.
What is Execution Authority?
Execution Authority answers one question before an action commits: may this exact action run now, under your policy and the approvals it requires? Your identity system proves who is acting and your guardrails judge content and risk. Execution Authority decides whether the resulting payment, change or API call may commit, and leaves a signed record you can verify.
Your policy decides on the exact action, as it stands now.
Any approval it requires is bound to that one action.
A single-use permit is checked before the action commits.
You keep signed evidence of the decision and what happened.
Your identity system, guardrails and downstream application retain their existing responsibilities.
What both products give you
One policy, one approval step and one signed record, whichever product you start with. Your systems keep running the actions; you connect only the ones you want to protect.
Your policy decides
Each action runs, waits for the person you name, or stops, under the rules you set.
Approval bound to one action
An approval covers that exact action once. It can't be replayed or moved to another.
A record you can check
Every decision is Ed25519-signed, so you verify it offline without asking us.