Detect Bots

Overview

A bot detection API for crawlers and scrapers. Bot Detector uses a comprehensive database of known bot and crawler user agent patterns to identify automated traffic, categorizing detected bots into types like search engines, social media crawlers, SEO tools, and monitoring services. It also applies list-free heuristics to flag automated clients the database misses — missing user agents and non-browser clients such as curl and scripts — and returns a composite risk score.

Live Test Detect Bots Source →

Formula

One function covers the whole catalog: the first argument names the source, the rest are its inputs, and the "field" pair says which single value lands in the cell. Formulas covers the grammar that applies to all of them.

=VERVE("botdetector", A2, "field", "userAgent")

A2 holds the ua you are looking up. Drag the formula down and each row resolves on its own.

With literal values

Nothing has to come from a cell — typed values work the same way.

=VERVE("botdetector", "Googlebot/2.1 (+http://www.google.com/bot.html)", "field", "userAgent")

Inputs

Required inputs are positional, in the order below. Everything else is passed as a "name", value pair after them — the same shape as SUMIFS. Premium inputs are accepted on every plan but only take effect on plans that include them.

Input	Type	Where it goes	Description
`ua`Required	string	argument 2 (A2)	The user agent string to analyze (URL encoded)
`ip`Optional	string	"ip", value	Optional IP the request came from. When the user agent claims to be a Google, Bing, OpenAI or Apple crawler, it is checked against that operator's published IP ranges ip

Passing an option

=VERVE("botdetector", A2, "ip", "66.249.66.1")

What lands in your sheet

The "field" pair is what makes the formula resolve to one cell. Its value is a dot-path from the table below, so swapping it is how you pull a different value — one formula per column.

Seeing everything at once

Drop the "field" pair and the formula returns the whole response instead: two columns, field name on the left and value on the right, spilling from the cell you typed in.

=VERVE("botdetector", A2)

Good for exploring, not for filling down

The second row's table would land on top of the first's, and every cell after the first reads #REF! (#SPILL! in Excel). Keep one per sheet, or name a field, and leave the cells below and to the right empty.

Response fields

Paths are relative to data. Each one is exactly what the "field" pair accepts, so swapping it is how you pull a different value into a cell. On a plan without a Premium field the cell reads #PREMIUM(field) rather than a value, so a locked field never looks like a real answer.

Use as "field"	Type	Example cell value	Description
`userAgent`	string	`Googlebot/2.1 (+http://www.google.com/bot.html)`	The analyzed user agent string provided in the request
`isBot`	boolean	`true`	Whether the user agent belongs to a known bot or crawler
`bot`Premium	object	`{…}`	Detailed bot information including name, category, and reputation
`bot.name`Premium	string	`Googlebot`	Name of the detected bot or crawler
`bot.category`Premium	string	`search_engine`	Category of bot: search_engine, social_media, monitoring, seo_tool, scraper, other
`bot.url`Premium	string	`http://www.google.com/bot.html`	Official URL or documentation link for the bot
`bot.reputation`Premium	string	`trusted`	Trust level: trusted (search engines, social), neutral (monitoring, SEO), malicious (scrapers, spam), or unknown
`bot.shouldBlock`Premium	boolean	`false`	Recommendation whether to block this bot based on category and reputation
`isAutomated`Premium	boolean	`true`	Heuristic signal that the traffic is automated — true for known bots, missing user agents, and clients that do not present as a standard browser (e.g. curl, scripts, headless tooling). Catches automated clients not in the bot database
`verified`Premium	boolean	`true`	Whether a claimed Google, Bing, OpenAI or Apple crawler really comes from that operator's published IP ranges (false = spoofed). Null when no ip is given or the user agent claims no verifiable crawler
`riskScore`Premium	number	`0`	Composite 0-100 risk score combining bot reputation, block recommendation and automation heuristics (higher is riskier)
`riskLevel`Premium	string	`low`	Risk band derived from the score: low, medium or high

Filling a whole column

Both platforms make one batched call for a column rather than one request per cell, and both cost the same — 10 credits per row looked up. How you write it differs, because the two runtimes batch at different points.

Rows 2–100 in one call

=VERVE("botdetector", A2:A100, "field", "userAgent")

In Google Sheets, give the arguments ranges and the answers spill down from the cell you typed in. Custom functions there run synchronously and in isolation, so dragged cells cannot be coalesced — the range form is how a column becomes one call. The "field" pair is required here: a per-row two-column table has nowhere to spill. Use a full column per input (A2:A100, not A2) — a single-cell reference is read as row 1 only and the rest of the column comes back blank.

In Excel, type the formula once and fill down — no range form and none needed, because its runtime is asynchronous and the add-in coalesces the calls a fill produces into a single batched request. Do not hand VERVE.CALL a range: Excel flattens it into positional arguments, so A2:A100 arrives as a hundred separate arguments and the cell reads #ERR rather than filling.

Either way, column A holds your ua values and the answers land beside them, one row each, blank rows skipped.

When a cell doesn't fill

A failed lookup returns readable text starting with #ERR rather than a spreadsheet error, because Excel cannot show a custom message on a real error — you would get a bare #VALUE! with no reason. The trade-off is that IFERROR() will not catch it; test with LEFT(cell, 4) = "#ERR" instead. Error handling covers the rest.

Cell reads	What happened
`#ERR Not connected`	No API key saved. Open the side panel and connect your account.
`#ERR Replace <name> with a cell or value`	A preview formula was copied as-is. Swap the placeholder for a cell reference.
`#ERR No "x" in botdetector`	An option name this source does not take. The message lists the ones it does.
`#ERR No data point "…"`	The `"field"` path is not in the response. Check it against the table above.
`#PREMIUM(field)`	The field exists but your plan does not include it.
`#ERR Out of credits`	The cycle's credits are spent. Usage resets on your billing date.

Before the formula works

The add-in reads the API key you saved once in the side panel — the key never goes in the formula, so a shared sheet does not leak it and a collaborator without access simply sees the last calculated values.

Install the add-in for Google Sheets or Excel.
Open the side panel and sign in, or paste a key from your dashboard.
Type the formula above into any cell.

Use cases

Analytics Filtering: Exclude bot traffic from your analytics to get accurate visitor metrics and user behavior data
Access Control: Implement different behavior for bots vs real users, such as rate limiting or content restrictions
Security Monitoring: Identify potentially malicious crawlers and scrapers attempting to access your content
SEO Insights: Track which search engine bots are crawling your site and how frequently

Other ways to use Detect Bots

Set up Detect Bots on VerveSheets, or reach the same source a different way. Your VerveSheets account and credits work on all of them — one key, one balance.

Call it as a REST APIOne HTTPS endpoint and an x-api-key header, with SDKs for Node, Python and .NET.APIVerve →Reference →

Give it to an AI agentConnect over MCP and your agent calls it as a native tool — Claude, Cursor, ChatGPT.VerveKit →Reference →

Ground an agent on itA cited, machine-checkable fact your model can't produce on its own.VerveContext →Reference →