# BotShield > BotShield makes human in the loop products for humans that wish to maintain their autonomy online. For a company it is one mechanism, placed where it matters: verify your customers once, then gate the moment (BotShield Gates) or key the act (BotShield Actions). The person holds one credential, a BotShield ID, and the passkey comes with it. BotShield systems never learn who anyone is. BotShield, Inc. is based in Denver, Colorado and is a member of the FIDO Alliance. Every check is a passkey ceremony on the person's own phone, answered in the BotShield app; the check that unlocks the phone never leaves it. What reaches a company is a signed verdict scoped to that company alone — never a name, an email, a document or a face. ## Products - [Verified Accounts](https://botshield.ai/verified-accounts): A real person behind every account. One passkey binds an account to a real person; the company gets a yes or a no scoped to it alone, keyed by an opaque ID. The link is the proof, and it is what a gate counts on — a gate requires a verified account. Offered as one chip behind the company's own sign-in: Verify with BotShield. - [BotShield Gates](https://botshield.ai/gate): The mechanism to arrive able to redeem fairly. A gate is a door in front of a moment — a presale, a drop, a vote, a signup. A real person signs up, passes once on their own phone, and lands where the company runs it holding a single-use token. Placed on a page, an API call, a link or an agent's tool — or sent from the company's server to one named person, recallable (Verify with BotShield), which is where the SMS code used to go. Age is an attribute of the same tap (13 · 18 · 21), set when the gate is placed. Verdicts: pass or Unavailable, with a reason. - [BotShield Actions](https://botshield.ai/actions): A gate lets someone through; an Action is the thing — a cart, a payout, a plan change, executed in place on the company's own page with a passkey. No clock, no queue. A signed record of who approved it comes back to the company's code. - [Trusted Agents](https://botshield.ai/trusted-agents): Every agent a company runs, registered in the Console with its own key and the verbs it may ask for, and linked by each person who lets it in. Revoke the key and every link dies with it; the person can cut any agent from their side. - [Agents Ask](https://botshield.ai/agents-ask): The SMS-code alternative when a company's agent — a support desk, a billing agent, an Agentforce-class agent — has to be sure it is really the person. The ask lands in the BotShield app; the person answers with a passkey; a signed Proof of Resolution comes back. Approved, declined or expired; the default is always no. Five MCP tools, none of which can say yes. - [BotShield ID](https://botshield.ai/id): What the person holds. A passkey on the phone they already own, created in a sheet their OS drew, anchored to an Apple or Google root. One ID, one account per platform, and it never rotates. Free for people, always. - [Couchtour](https://botshield.ai/couchtour): Tenant #1 — presale codes, streams and merch drops for artists and their fans, built on BotShield like any partner: every account a Verified Account, one presale code and one draw entry per account, a stream seat opened with a passkey. Launches soon. - [BotShield Console](https://botshield.ai/console): Sandbox keys the moment you sign in; production once your domain is verified. One script tag and one element to place a gate; Verify with BotShield to send one; the Verified Accounts registry; the five MCP tools. ## Integrating - [Docs](https://docs.botshield.ai): Quick start, the `` element (`site-key`, `scope`), server-side verification, webhooks, the TypeScript SDK, and the hosted MCP server for agents. - [MCP server](https://docs.botshield.ai/agents-ask/mcp-server): `https://mcp.botshield.ai/mcp` — propose_resolution, bind_session, check_binding, check_resolution_status, cancel_resolution. - [API reference](https://docs.botshield.ai/api-reference/overview): Base URL `https://api.botshield.ai/operations`. ## Key facts - What a company receives: a signed verdict (ES256 JWT, verifiable against `https://api.botshield.ai/.well-known/jwks.json`) with a request id, the verdict, the organization id, a timestamp, a nonce and an opaque ID to key by. Never personal data. - What a gate stores: a random ID for the person; a count of passes per person on the platform, for the window the company set; that a human confirmed, and when — never where, never what. No email, name or phone; no browsing, location or activity; no face, no fingerprint. Verdicts are kept 90 days, then deleted. - What BotShield holds, named: the BotShield ID (the person's own root), an opaque ID per link, gate sign-ups as opaque keys against a deal, a count never a roster, and a verified number only where a gate asked for one. The data is with the party that needs it. Data goes to the one party the person chose to do business with; it is never sold. - A gate always asks; BotShield never keeps anyone signed in and never replaces a login. The company sets who may pass; BotShield reports what happened and never decides. - Legal: [Terms](https://botshield.ai/terms) · [Privacy](https://botshield.ai/privacy) · [Age assurance](https://botshield.ai/age-assurance). Contact: hello@botshield.ai · (303) 903-3274.