Skip to main content
When someone already holds a proof that meets your rule, Proofable accepts it and skips the check.

How reuse is decided

1

Find existing proofs

Proofable looks for proofs the person or agent already holds for each required check.
2

Confirm they are current

Expired and revoked proofs never count. Point-in-time checks, such as a token balance or wallet risk, must be recent enough for your rule.
3

Confirm they fit this rule

A stricter rule can need a new check. A basic proof of human does not satisfy a gate that also requires a minimum age.
4

Pass, or verify only what's missing

If every requirement is covered, the person continues. If not, they complete only the missing checks.

Reuse in your product

Reuse costs less

Signed-in owners checking their own proofs through MCP pay nothing.

Private proofs

Gate checks read public and unlisted proofs by default. A private proof counts when its owner is signed in, or when you pass a signed payload from createGatePrivateAuth. Gates in the SDK

Next

Proofs

What a proof records and how to read it.

Proof lifecycle

Freshness, reuse strategies, and revocation.

Gate checkout

How reuse works inside a checkout.

Pricing

What checks and new proofs cost.
Last modified on September 12, 2026