Public beta · the BotShield app is live on the web.  →
Console
Console
Products
Verified AccountsTrusted AgentsBotShield ActionsBotShield Gates
For your users
BotShield IDAgents Ask™
For developers
Console
Customers
Couchtour
Company
AboutInvestorsContactNewsroom
Console

Sandbox keys the moment you sign in.

Sign in, take a key, place a gate on a page. The sandbox asks for nothing. Production is a conversation: verify your accounts with us, then place the gate.

Explore the consoleTalk to a person  →
The console itself

Every gate you placed, and what each one answered.

One screen for all of it: place a gate, watch it open and close on its own schedule, and read every verdict it returned — pass or Unavailable, with the reason.

console.botshield.ai/couchtour/gates
The BotShield Console — Verified Accounts › Gates: gates placed in production, each with its rule, state and the day it was placed

Illustrative · mock company

Place a gate

One script tag and one element.

It is a custom element, so it works wherever your HTML works — no framework, no rewrite, nothing to migrate onto.

<script src="https://cdn.botshield.ai/sdk.js"></script>
<botshield-verify
  site-key="pk_live_…"
  scope="checkout"
  checkout-label="Complete purchase">
</botshield-verify>
Or send one

Or send one.

Verify with BotShield is set up in three steps — the surface, the tag, turn it on — and your server can put a gate in front of one person from then on.

For agents

Five MCP tools. That is all of it.

Point any MCP client at the server and your agent can ask a person for a yes. Small on purpose — an agent should not be able to do more to your customer than this.

See the five tools, named  →

Console FAQ

How do I place a BotShield Gate on my site?
Sign in to the Console, take a site key, and put one script tag and one custom element where the moment is. The element renders the chip; the person taps; a signed verdict comes back to your code. No framework, no rewrite.
Is there an SDK, an API, or MCP tools?
All three, on one key. The SDK is the element on your page; the API places and reads gates from your server, and sends Verify with BotShield to one person; the five MCP tools are what your own agents call. Every way in writes to the same record.
How do I check a verdict is genuine?
Verify the ES256 token against BotShield’s public JWKS before you let the act through — one call, or locally. It carries a request id, the verdict, your organization id, a timestamp and a nonce, and an opaque ID you can key by. No identity fields in any of it.
What do I need before going to production?
A verified domain — the domain is the claim. Sandbox keys work the moment you sign in; production unlocks once your business is verified and your accounts are, with us.
Can our own agents call it?
Yes. Register the agent in the Console, give it its key and the verbs it may ask for, and point it at the MCP server. It can propose, check and cancel; it cannot say yes — the person does, with a passkey.
Where do I get keys?
In the Console, under Developer Tools: one site key per surface for the element, API keys for your server, and one key per agent for the tools. Revoke any of them there, at once.

Sandbox today. Production after a call.

Keep your stack, your login and your checkout exactly where they are. Verify your accounts with us, then place the gate.

Talk to a person  →Explore the console