Proofable or a policy engine for agent authorization
A policy engine applies your rules. Proofable adds delegation, spend caps, expiry and instant revoke, plus a receipt any system verifies offline.
Keep your rules in your policy engine. Add Proofable when an agent runs somewhere you don’t own, when more than one party relies on the outcome, or when someone outside your system has to trust the decision. A policy engine with a log is enough only when one team owns the rules, every caller, and everyone who reads the log.
What each one answers
Question
Policy engine or API gateway
Proofable
Is this action allowed by our rules?
Yes, static role and tool rules
Yes, plus owner-to-agent delegation, spend cap, expiry and instant revoke
Who is the agent and who owns it?
Only if you modelled it there; a gateway sees an API key in flight
Signed owner-to-agent identity and scoped permission
Does the decision survive leaving your system?
Server log row inside your infrastructure
A signed receipt (qHash) another agent or auditor verifies offline
Can a downstream agent trust a handed-off result?
No receipt layer; agents trust forwarded text or redo the work
It checks the signed receipt instead of redoing the work
Does a refused action stop the call?
Depends on your integration
The caller stops before the tool runs
Where they fit together
The check is one call before the tool runs.
import { evaluateRuntimeAction } from '@proofable/sdk/runtime-mount';const decision = evaluateRuntimeAction(mount, 'publish_report', { irreversible: true });if (!decision.allowed) throw new Error(`${decision.code}: ${decision.message}`);
Your engine can still run before or after this check. Standards and interoperability lists the authorization and attestation layers Proofable works beside, including AuthZEN and AARM.
Next
Control agent actions
Every limit an agent can carry.
Reuse verification
Check once and reuse the result.
Prove what happened
Keep a record of each decision.
Benchmark
Every benchmark, with its scope and how to rerun it.