Skip to main content
Proofable plugs into the sign-in, policy engine, agent runtime, and payment processor you already run. It checks each action at the boundary and turns the result into a portable proof every one of those systems can verify. Wallet-signed checks and Proofable-signed outcome statements use CAIP-380, the open Portable Proof standard Proofable’s founder wrote. The Technical Whitepaper covers the architecture.
A signed CAIP-380 envelope proves who signed and that the statement is unchanged, and anyone can check that offline. Proofable adds the check result and whether it is still current.

How Proofable uses these standards

Each layer answers a different question: who the agent is, what it may do, what was decided, what happened, and how strongly another party can rely on the record. Portable Proof keeps those answers as separate, linked records.

Where we contribute

To check a CAIP-380 envelope on your own machine, see Offline verification.

Next

First guarded action

Check permission before a tool runs.

Discover agents

Public agent pages and discovery cards.
Last modified on October 27, 2026