Switchfrog
Turns a website's existing user workflows into WebMCP actions that agents can call directly, and shows site owners which agents are using the product and what they do there.
Documentation
Detect AI agents using your product, so you can see which accounts they use, where they go, and what they do.
Backed bySessionsIllustrative example
| Identity | Type |
|---|---|
| bruce@waynetech.com | Agent |
| clark@dailyplanet.com | Human |
| tony@starkindustries.com | Agent |
| diana@themyscira.org | Human |
| reed@baxterbuilding.com | Unknown |
| lois@dailyplanet.com | Human |
Sees Claude in Chrome Instinct Muse OpenAI Codex Cursor Grok Gemini Perplexity Copilot OpenClawand every other browser-driving agent
Your customers are bringing agents.
Millions of people are using AI browser agents like Claude Cowork, Codex, and OpenClaw. Since they use your customers’ real browsers and accounts, they bypass traditional bot detection and look like ordinary product usage.
Switchfrog detects when an AI agent takes over, shows you what it does, and lets you respond in real-time.
Session
Session events
- Started
- Human
- AgentClaude in Chrome took over
Activity
- /dashboard 7m agoHuman4 updates
- /settings/team 6m agoHuman3 updates
- /reports 5m ago · Claude in ChromeAgent5 updates
Understand how AI agents are using your product.
View session activity by human or agent, across all pages on your website. See which users are bringing agents, what they're doing, and at what time of day.
Sessions · last 24 hours
Sessions
1,470
last 24 hours
Human
1,120
76%
Agent
279
19%
Unknown
71
5%
Human
1,12076%
Agent
27919%
Unknown
715%
Choose how to react to agent usage.
Switchfrog reads the session itself, not just the traffic, so it can tell a person from an agent on the same account.
Install
Installation is easy - just one line of code.
Your page
The tag loads with the page and watches how the session is driven.
<script async src="https://api.switchfrog.com/sdk/v1.js"
data-publishable-key="sf_pk_your_publishable_key"></script>
Detect
We can detect whether a session is AI or human, usually in milliseconds.
Switchfrog
The verdict for this session.
Identity
Type
Agent
Driver
Claude in Chrome
Confidence
0.97
Respond
Choose whether to allow the agent, block them, or bill them for an agent seat.
Your systems
POST /webhooks/switchfrog
{ "session": "s_9f2a71", "identity": "bruce@waynetech.com",
"type": "agent", "driver": "claude-in-chrome", "confidence": 0.97 }
AI agents are bypassing API pricing.
seat: bruce@waynetech.com · starter
Person
39 / 39 h this week
MonTueWedThuFriSatSun
Agent, same login
140 / 140 h this week
MonTueWedThuFriSatSun
00:0012:0024:00
You priced seats assuming a person was using it a few hours a day. An agent on that login runs all night and is getting 10x more value out of it. If you want to bill an agent like an API, Switchfrog shows you which seats are agents, how much usage they are running, and allows you to bill it appropriately.
Frequently asked questions
Software driving the browser on a person’s behalf: Claude in Chrome, Claude Cowork, OpenClaw, Codex and the like. Switchfrog reads how the session is being driven rather than who is logged in, so it catches the handover even when the agent is using a real customer’s account.
A session where the signal isn’t strong enough to call it either way. Those are kept apart from the Human and Agent counts rather than guessed, so you can decide how to treat them.
Yes. It’s one tag on the pages your customers already use. Nothing changes about your login, your SSO or your identity provider, and there’s no proxy to run.
How the session is driven: input timing, pointer movement and navigation. It is there to tell a person from an agent, and it doesn’t need the contents of what people type or see to do that.
While the session is still open. Each session is classified within milliseconds and the verdict is available by webhook or API straight away, so you can act on it before the session ends.
No. It tells you what’s driving the session and leaves the decision to you: allow the agent, flag the account, or move the seat onto agent pricing.
That’s the point. The verdict reaches your billing system by webhook, so a seat that turns out to be an agent can be metered like the API it has become. We’re pricing agent-seat billing with the beta customers who use it first.
See how agents use your app.
Backed by