Skip to main content
BotShield Gate checks for a real human at the moment it matters: a sign-up, a checkout, a post, an age-restricted page. The user confirms with a passkey in the BotShield app, and you receive a result. BotShield tells you that the user is human, never who they are. You receive no personal data.

Two gate types

Human Gate

“Is a real human here?” The result is Verified or Unavailable.

Age Gate (Beta)

“Is this human over 13, 18 or 21?” The result is Over N Verified or Unavailable. It never returns a date of birth, an age, or an “underage” answer. See Age Gate.
Both types use the same integration. There are only two result states, and your code should branch on exactly those two. See Result states.
See it before you build it. The BotShield Demos run both gate types on production keys: Ticketz puts a Human Gate on a checkout (with the inline passkey beta), and Vapez puts an Age Gate on a storefront door. Open one on your laptop and confirm on your phone.
Unavailable is not an accusation. It means BotShield could not confirm a human this time: the request expired, the user declined, the check could not run, or the gate’s Who may pass levers refused this person. A lever refusal carries its reason by name.

What a gate is

A gate is one placement of BotShield Gate in your product. You place gates in the BotShield Console (Verified Accounts › BotShield Gates) or from your server with the Gates API, and each gate has:

A gate always asks

Every pass is a new passkey confirmation on the person’s phone. That holds for a Human Gate and an Age Gate, for a person you have seen before and for one you have not. There is no instant pass for a returning person and no window in which an earlier confirmation still counts.

Who may pass

You decide who a gate lets through. The two count levers are off by default on a Custom gate: Passes are counted per person, not per account. A gate can also be for signed-up people only, and can link each pass to the person’s account with you. See Who may pass.

A gate or an action

A gate is a door with a clock: it opens, closes and counts passes. To key one act on your platform to a passkey tap, such as accepting a trade, with no schedule and no counting, use a BotShield Action instead.

Where to use a gate

Use a gate anywhere you would put a CAPTCHA, and anywhere a CAPTCHA has stopped being enough:
  • Sign-up and sign-in, to stop scripted account creation.
  • Checkout, for limited drops, tickets and high-demand inventory.
  • Posting, voting and reviews, to keep automated content out.
  • Age-restricted access, with an Age Gate.
  • Sensitive account changes, such as payout details or recovery.
A gate covers one action. Place separate gates for separate actions so you can set who may pass, read the logs and close each one independently.

Two ways to integrate

Web component

Add a script tag and a <botshield-verify> element to your page. The widget draws the Verify Human button, shows the QR code or opens the app, and hands your page the result. Then you verify it on your server.

Server-to-server

Your server creates the verification request with your API key, you show the link in your own UI, and you learn the result by webhook or by polling. Use this for native apps, custom UI and back-office flows.

How the widget flow works

The event on your page is a convenience for your UI. The decision belongs on your server: always check the result server-side before you let the action through.

Next steps

Place a gate

Create a site key, place a gate and activate it in the Console.

Web component

The full <botshield-verify> reference.

Verify on your server

Check tokens, or run the whole flow server-to-server.

Who may pass

Limit passes per person, and require a BotShield ID that has been real for N days.

Testing

Development keys, the Console Sandbox and a launch checklist.

Go to production

Verified domain, business verification, Developer passkey and a plan.

Live demos

Ticketz (Human Gate at checkout) and Vapez (Age Gate at the door), running on production.