Denial reasons
Why are transactions being denied?
94
Expired
298
Destination
41
Scope
- Revoked26
- Remaining limit22
- Time window19
- Transaction cap15
Certificate-gated security and
insurance for AI agents
- Independent gates
- 2
- Checks per decision
- 15
- Issuer
- Signature
- Active status
- Scope
- Coverage limit
- Claim triggers
- Exclusions
- Revocation
- Settlement path
- Spending limits
- Allowlists
- Asset rules
- Time windows
- Session keys
- Simulation
How it works
One decision before
every transaction
An agent proposes a transaction. CoverGate checks its cover, then its mandate, then simulates the effects. It runs only when both gates approve.
- Expiry alerts
- Time windows
- API and MCP
- Mandate templates
- Decision receipts
- Coverage badge
- Dry-run mode
Covered and allowed
Active cover and a passing mandate. This is the only path that executes.
Allowed
Agent
Transfer 500 USDC to an approved vendor.
CoverGate
- Resolving the AIPS-1 Policy Certificate
- Checking the mandate firewall
- Simulating the transaction
Both gates approved. The transaction executes.
Cover: Certificate active, action in scope, amount within the remaining limit.
Mandate: Under the cap, destination approved, inside the time window.
Decision receipt written · Example decision
Two gates. Neither overrides the other.
Cover answers whether this action is insured right now. The mandate answers whether it is allowed at all. Valid cover never makes an unsafe transaction acceptable.
SimulatedExecute
AssetCapUsedLeft
Spend
Limit
Result
Simulated before it reaches the chain
Transaction Simulation evaluates the effects first. Dry-Run Mode returns the full decision without executing, so teams can test an agent safely.
Cover gate
checked on every spend
Issuer, signature, status, scope, limit, exclusions, and revocation are read from the AIPS-1 certificate.
Verifying certificate
Mandate gate
with limited session keys
An agent gets a key that only works inside its mandate: caps, allowlists, assets, and time windows.
******
Human approval
above your threshold
Transactions above a set size go to a person before execution.
Treasury Agent
Can you approve 8,000 USDC?
Decision receipts
for every outcome
Policy and mandate hashes, the outcome, any denial reason, and execution evidence. Anyone can check one.
Recording…
- Receipt written 0:04
- Simulation passed 0:03
- Mandate passed 0:02
- Cover verified 0:01
# agent-alerts
MessagesFiles
A
Ari 3:12 PM
@CoverGate Why was the payroll agent denied last night?
3 repliesjust now
C
Citra 4:42 PM
@CoverGate Which agents have cover expiring this week?
3 repliesjust now
B
Bima 8:50 PM
@CoverGate Freeze the swap agent until we check it
3 repliesjust now
agent-alerts
A
Ari 3:12 PM
@CoverGate Why was the payroll agent denied last night?
3 repliesjust now
C
Citra 4:42 PM
@CoverGate Which agents have cover expiring this week?
3 repliesjust now
B
Bima 8:50 PM
@CoverGate Freeze the swap agent until we check it
3 repliesjust now
Type a message
Search mail
Cover expires in 7 days
DewiWhich agents depend on this certificate?2:34 PM
AlertsTwo agents. Both will be denied once it lapses.2:35 PM
DewiSend me the certificate and its renewal path.2:37 PM
Alerts <alerts@example.com>
Done. The certificate and both agents are listed in your inbox.
Reply Forward
Today 9:41 AM
Why is the 8,000 USDC transfer waiting?
It is above your approval threshold. Cover and mandate both passed.
Approved.
Executed. The decision receipt is in your log.
Message
Alerts · In-app today, chat and email planned
Know before
an agent stops
Payments Mandate
Rules
Ari is editing mandate v3.
Mandate Templates. Start from ready-made mandates for common agent types, then tune the rules.
Active cover
Certificate verified for this agent.
- Issuer recognized
- Scope stated
- Not revoked
Limits
Exclusions
Claim path
Coverage Badge. Show cover status, scope, protection limits, and claim paths in the open.
ProposeRecordDecide
Mandate Versioning. Every mandate change is kept, so any past decision can be traced to the rules in force at that moment.
Repeated denials · Swap Agent
Agent Monitoring
Flagged the agent for review:
- Agent spending frozen by the operator
- Session key access revoked
- Receipts kept for the audit export
Example alert · Frozen by Ari
Emergency Freeze. Stop an agent's spending at once from one control, the moment something looks wrong.
Exclusion Check. Each action is tested against the certificate's exclusions before it runs, not after a loss.
Claim Evidence Pack. The certificate, mandate, receipts, and transaction data, bundled together for a claim.
Monitoring
Your agents. Your spend. One view.
See approved and denied spend per agent, why transactions are denied, and which cover needs attention.
Controls
Controls for agent operators
- Approved
- 48.6k
- Denied
- 2.1k
- Cover used
- 86%
JanFebMarAprMay
Spend Dashboard
See approved and denied spend per agent in one view, next to the cover still available.
Audit Export
Export decisions and receipts for an agent over any period.
- Capturing…
- Ari froze the swap agent
- Citra renewed a certificate
- Bima updated a mandate
- Dewi exported receipts
Webhooks (planned)
Push decisions and certificate changes into your own systems.
Issuer Registry. A certificate from an unknown issuer is denied.
Asset Restrictions. Limit which tokens an agent can touch.
Plain Denial Reasons. Machine-readable, so an agent can correct its action or stop.
Not audited yet. Any audit will be announced with the report.
Time Windows. Block spending outside the hours you allow.
Allowlists. Restrict an agent to approved contracts and recipients.
Revocation Watcher. A revoked certificate denies the next transaction that depends on it.
Operator Bond. An optional first-loss deductible or performance security.
Counterparty Check. Merchants and protocols verify cover before accepting a transaction.
Remaining Limit Tracker. Spend above the cover still available is denied.
Execution Gateway
Every action faces every check
The gateway executes only when valid cover and mandate approval are both present. Otherwise it denies the transaction and returns a machine-readable reason, so an agent can correct its action or stop.
“Approve contract…”
“Refund the buyer…”
“Bridge funds…”
“Buy API credits…”
“Rebalance vault…”
“Pay this invoice…”
“Swap to USDC…”
“Run payroll…”
“Approve contract…”
“Refund the buyer…”
“Bridge funds…”
Gateway
Within limit
No exclusions
Mandate passed
Simulation passed
Receipt written
Issuer verified
Signature valid
Scope matched
Within limit
No exclusions
Mandate passed
Proof for everyone around the agent
Know an agent is protected before funds move, and see exactly what the cover includes and excludes.
Set the limits once. Agents that step outside the mandate are denied with a reason they can act on.
Verify an agent's cover before accepting a transaction, without relying on the project's word.
Judge a claim on receipts and hashes. Coverage, exclusions, and limits are explicit and machine-readable.
Sandbox
Try it in the sandbox
No cover.
No spend.
Prevent first. Insure the rest. Test an agent against both gates with no real funds.
Try the sandbox