Developers

Sandbox keys the moment you sign in.

Sign in, take a key, place a gate on a page. The sandbox asks for nothing. Production opens once we have verified your business.

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

Check the answer on your server. A gate that only the browser enforces can be skipped.

Three ways in

On a page, from an agent, or sent to one customer.

On a page

Place a gate.

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

For agents

Five MCP tools.

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.

Sent to one person · coming soon

Send a request.

Your staff or your server send a request to verify to one person, by their phone number. They answer on their own phone with their passkey.

The MCP tools

Five tools. Your agent calls them; none of them can say yes.

propose_resolution

Puts the act in front of the person and waits.

bind_session

Ties this agent’s session to the person who linked it.

check_binding

Asks whether that link still stands before it tries.

check_resolution_status

Reads the answer — waiting, confirmed, denied, expired.

cancel_resolution

Withdraws the ask. Nothing happened.

What is not here

A tool that approves. The yes only comes from the person’s phone.

The Console itself

Every request, and what each one answered.

The Console places a gate, registers your agents and keeps every answer. Sending a request by phone number, shown here, is coming soon.

console.botshield.ai
The BotShield Console — Verify with BotShield: a request sent to one customer by phone number, answered Verified, with the day’s other sends beside it

Illustrative data.

Where to go

Where to go from here.

The Console

Keys, what you placed, and every answer that came back.

Open the Console  →

A person

The docs are on their way. Until then, tell us what you are building and we will walk you through it.

Talk to us  →

Status

Whether everything is up, right now.

status.botshield.ai  ↗

Console FAQ

How do I place a 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 button; 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 gates and sends requests to verify from your server; 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 single-use value. No identity fields in any of it.
What do I need before going to production?
A verified domain and a verified business. Sandbox keys work the moment you sign in; production opens once both are done.
Can our own agents call it?
Yes. Register the agent in the Console, give it its key and the acts 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. Add one element, and you are testing.

Start now

Sign in and take a sandbox key. The sandbox asks for nothing.

Get sandbox keys  →
Or have us reach out

Leave your work email and a person replies.