Proofable Docs | Portable Trust Infrastructure

Proofable is portable trust infrastructure. Keep your sign-in, policy, agent tools, and payments. Proofable adds reusable proofs that those systems can require before access, payment, or action. Wallet-signed checks use the CAIP-380 format. The Technical Whitepaper covers the architecture.

A signed CAIP-380 request proves who signed and that the request was not changed. A Proofable proof records the check result and whether it is still current. Those are related, not the same.

How Proofable uses these standards

Standard	What it provides	How Proofable uses it	Status	See
CAIP-2 / CAIP-10	Network and account identifiers	Accounts, agents, and profiles use the same chain and account IDs	Available	Portable proofs, Discover agents
CAIP-380 Portable Proof	A wallet-signed request format with a stable proof ID	Wallet-signed Proofable checks use this format. Other signed-in checks still create Proofable proofs	Draft	CAIP-380 spec, Portable proofs, Examples
MCP	Tools and context for any MCP client	Hosted MCP carries profile, proofs, listings, permissions, and checks before sensitive tools run	Available	MCP setup
OAuth / OIDC	Sign-in for people and MCP clients	Hosted MCP and app Connect	Available	MCP setup
ACP	Client to a coding harness	Optional self-hosted job pin (OpenCode, Hermes, Claude ACP). Hosted jobs use the Operator engine. Proofable does not spawn ACP on Azure	Works with	Private Cloud Trust Harness
Enterprise Agent SSO	App access for agents with an active user	Keep Okta or your IdP. Proofable records agent limits and runs background jobs those systems do not cover	Works with	Agents
A2A	Agent discovery cards	Public cards show who the agent is and who approved it	Available	Platform A2A card, Discover agents
AuthZEN	A standard way to ask whether an action is allowed	A Proofable proof can be the evidence that decision uses	Works with	First guarded action, Whitepaper
AARM	Runtime checks before an agent acts	Proofable checks identity, limits, and current permission before an action, then records the result	Works with	Agent setup
ATF	Identity, behavior, access limits, and how to stop or revoke	Proofable covers those with identity, permission checks, deny, and revoke	Works with	Agent setup, Proof lifecycle
ERC-8004	Public agent discovery	Proofable publishes compatible discovery cards and keeps its own proof and permission model	Available	Platform agent card, Discover agents
x402	Pay for a single HTTP call	Payment settles the call. Proofable can still require a current proof before the call proceeds	Available	Pay per call
Phala	Confidential compute	Hosted AI can run in a Phala-backed confidential environment. The same proofs work on a private deploy	Available	Private Cloud Trust Harness

Proofable uses these standards. It does not replace them. CAIP-380 remains the open specification for the signed request format.

Check an example

Use a signed request from a check, or the published example:

import { verifyPortableProofEnvelope } from '@proofable/sdk';
import envelope from '../../../examples/caip-380/minimal-evm.json' with { type: 'json' };

const result = await verifyPortableProofEnvelope(envelope);
if (!result.valid) throw new Error(result.errors.join('; '));

This checks the proof ID, account binding, and signature on your machine. Current status still comes from Proofable or another service that stores the result. See Portable proofs.

Portable proofs

How the signed request format works.

Whitepaper

Architecture and trust model.

First guarded action

Check permission before a tool runs.

Discover agents

Public agent pages and discovery cards.

Trust

Standards & interoperability

How Proofable uses these standards

Check an example

Next

Portable proofs

Whitepaper

First guarded action

Discover agents

​How Proofable uses these standards

​Check an example

​Next

Portable proofs

Whitepaper

First guarded action

Discover agents

How Proofable uses these standards

Check an example

Next