Gates

Require proof before it happens. You decide what must already be proven. The person verifies. You keep the result. One check is not a gate. A single proof-of-human requirement is Verify with a saved proof: send the person to Hosted Verify, read the returned proof ID, done. No gate to define. Reach for a gate when the decision needs a policy of several checks, a price, or a schedule. Publishing a listing is optional: use it only when you want a persisted gateId, price, schedule, or marketplace offer.

What a gate holds

Part	What it sets
Checks	What must already be proven, with optional match rows such as a provider or minimum age
Price	Optional. Free unless you publish a charge
Schedule	Optional start and end times, enforced on the server when published
Reward	Optional. What people receive after they pass a published listing

Enforce it

Where	How
Your server	`defineGate` + `gateCheck`. `satisfied === true` means ready
A React page	`VerifyGate` with the `gate` policy
A published listing	`VerifyGate` with a `gateId`, or a hosted checkout link
An API	Pay per call with a proof check
An agent action	The agent’s permission check before the tool runs. Control agent actions

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

const proofable = new ProofableClient();
const gate = defineGate([
  { verifierId: 'proof-of-human' },
  { verifierId: 'ownership-dns-txt', match: { domain: 'acme.com' } },
]);
const result = await proofable.gateCheck({ gate, subject });
if (result.satisfied) {
  // grant access
}

import { defineGate } from '@proofable/sdk';
import { VerifyGate } from '@proofable/sdk/widgets';

const gate = defineGate([
  { verifierId: 'proof-of-human' },
  { verifierId: 'ownership-dns-txt', match: { domain: 'acme.com' } },
]);

<VerifyGate gate={gate} onVerified={grantAccess} />;

How a check runs

Define the policy. Verifier IDs plus optional match, freshness, and count rows.
Check existing proofs. gateCheck evaluates the subject’s current proofs against that policy.
Verify what’s missing. Hosted Verify or your own verify call covers only the gaps.
Decide. satisfied is the decision. Proofable does not grant access for you.

Who pays

Checks on a published listing use your credits by default. Turn on visitor checkout to charge a price instead. Inline defineGate checks and other API calls can be sponsored by your app or paid per call with x402. Pricing

Guides

Sell access with one gate

Publish, embed, and confirm in three steps.

Gate checkout

Drive the full checkout from your own backend.

NFT and token gating

Require a holder or a minimum balance.

Pay per call

Charge per API request with x402.

Overview

Use cases

Reference

Legal

Guides

What a gate holds

Enforce it

How a check runs

Who pays

Guides

Sell access with one gate

Gate checkout

NFT and token gating

Pay per call

​What a gate holds

​Enforce it

​How a check runs

​Who pays

​Guides

Sell access with one gate

Gate checkout

NFT and token gating

Pay per call

What a gate holds

Enforce it

How a check runs

Who pays

Guides