Verify once. Reuse the proof.

A proof is a verifiable record of what was checked, who it belongs to, and whether it still holds. The next app checks the proof instead of repeating the check.

Start a check Read the docs

Definition

Portable proof means a verification result another system can check without repeating the original check.

How a proof gets reused

1
A check runs once
Hosted Verify or the API confirms the identity, ownership, access, or claim.
2
The result becomes a proof
The proof records what was verified, who it belongs to, its status, and its expiry.
3
The next system checks the proof
gateCheck reads the current proof on your server and allows or refuses the action.

Check a proof on your server

gate.ts
import { ProofableClient, defineGate } from '@proofable/sdk';

const proofable = new ProofableClient();

const gate = defineGate([{ verifierId: 'proof-of-human' }]);

const result = await proofable.gateCheck({
  gate,
  subject: { accountId: user.accountAddress },
});

if (result.satisfied) {
  // The proof already exists. The action runs.
}

When to use it

Use it when

You repeat the same identity, ownership, or access check across more than one surface.
Checkout, signup, or payout flows each verify the same buyer.
A partner needs to confirm a check you already ran.

Not when

One-off checks that nothing downstream depends on.
Secrets or raw documents you must never share.

Privacy and status

A proof records the result. The documents behind it stay private.
Anyone can recheck a proof later and see if it still holds.
A revoked proof fails the check. Revocation is immediate.
Proofs expire. A gate never trusts a stale result.

Check once. Reuse everywhere.

Run the check, keep the proof, and let the next system verify it instead of asking again.

Start a check

Verify once. Reuse the proof.

A proof is a verifiable record of what was checked, who it belongs to, and whether it still holds. The next app checks the proof instead of repeating the check.

Start a check Read the docs

Definition

Portable proof means a verification result another system can check without repeating the original check.

How a proof gets reused

1
A check runs once
Hosted Verify or the API confirms the identity, ownership, access, or claim.
2
The result becomes a proof
The proof records what was verified, who it belongs to, its status, and its expiry.
3
The next system checks the proof
gateCheck reads the current proof on your server and allows or refuses the action.

Check a proof on your server

gate.ts
import { ProofableClient, defineGate } from '@proofable/sdk';

const proofable = new ProofableClient();

const gate = defineGate([{ verifierId: 'proof-of-human' }]);

const result = await proofable.gateCheck({
  gate,
  subject: { accountId: user.accountAddress },
});

if (result.satisfied) {
  // The proof already exists. The action runs.
}

When to use it

Use it when

You repeat the same identity, ownership, or access check across more than one surface.
Checkout, signup, or payout flows each verify the same buyer.
A partner needs to confirm a check you already ran.

Not when

One-off checks that nothing downstream depends on.
Secrets or raw documents you must never share.

Privacy and status

A proof records the result. The documents behind it stay private.
Anyone can recheck a proof later and see if it still holds.
A revoked proof fails the check. Revocation is immediate.
Proofs expire. A gate never trusts a stale result.

Check once. Reuse everywhere.

Run the check, keep the proof, and let the next system verify it instead of asking again.

Start a check

Verify once. Reuse the proof.

How a proof gets reused

A check runs once

The result becomes a proof

The next system checks the proof

Check a proof on your server

When to use it

Use it when

Not when

Privacy and status

Check once. Reuse everywhere.

Verify once. Reuse the proof.

How a proof gets reused

A check runs once

The result becomes a proof

The next system checks the proof

Check a proof on your server

When to use it

Use it when

Not when

Privacy and status

Check once. Reuse everywhere.