Skip to main content
Require proof before an action happens. You decide what must already be proven, the person verifies, and you keep the result. A single check needs no gate. For one proof-of-human requirement, send the person to Hosted Verify and read the returned proof ID. Verify covers that path. Use a gate when the decision needs several checks, a price, or a schedule. Publish it as a listing when you want a persisted gateId, price, schedule, or marketplace offer.

What a gate holds

Enforce it

How a check runs

  1. Define the policy. Verifier IDs plus optional match, freshness, and count rows.
  2. Check existing proofs. gateCheck evaluates the subject’s current proofs against that policy.
  3. Verify what’s missing. Hosted Verify or your own verify call covers only the gaps.
  4. Decide. satisfied is the decision, and your server grants the access, so the final call stays yours.

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.
Last modified on October 25, 2026