Skip to main content
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. Agent rules enforced on AgentGovBench, scenarios handled of 48: Proofable 48, ACP gateway 46, Anthropic Agent SDK with ACP 46, OpenAI Agents SDK with ACP 45, Claude Code or Codex with ACP 43, CrewAI or LangGraph with ACP 40, Cursor with ACP 37, coding agents alone 13, no rules at all 5.

What each one answers

Where they fit together

The check is one call before the tool runs.
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.
Last modified on November 17, 2026