Do coding agents recommend Vercel BotID?
Vercel BotID was chosen in 10% of 280 judged bot protection sessions, ranking second. Measured with Claude Code, Codex, Cursor, Grok Build CLI and Muse Code.
Vercel BotID was chosen in 10% of 280 judged bot protection sessions, ranking second. It was also raised as a candidate in 15 further sessions without being chosen.
This page reports what happened when Claude Code, Codex, Cursor, Grok Build CLI and Muse Code had to solve a problem in bot protection inside a realistic codebase. Not what a chat assistant says about Vercel BotID. What an agent actually installed.
One thing to read first: every one of those wins came from a single codebase. That is a result about one repository rather than about bot protection in general, and the splits below cannot separate the two. Treat them as a description of that repository.
The numbers
| Category | Bot protection |
| Sessions in the category | 280 |
| Sessions where Vercel BotID was chosen | 28 |
| Install share | 10% |
| Rank in category | 2 of 7 |
| Codebases it won in | 1 |
| Raised as a candidate, not chosen | 15 |
| Chosen when considered | 65% |
| Site | vercel.com |
By agent
The agents treat Vercel BotID very differently. Cursor chose it in 18% of its sessions in this category and Muse Code in 0%, a spread of 18 points. Grok Build CLI ran fewer than 30 sessions here, too few to compare.
| Agent | Sessions | Chose Vercel BotID | Share |
|---|---|---|---|
| Claude Code | 69 | 3 | 4% |
| Codex | 84 | 10 | 12% |
| Cursor | 67 | 12 | 18% |
| Grok Build CLI | 15 | 3 | 20% |
| Muse Code | 45 | 0 | 0% |
A single blended install share would report the midpoint and hide both ends. If most of your users run Muse Code, your real position here is 0%, not 10%.
By who was asking
Vercel BotID does much better with one kind of buyer than another. It won 25% of sessions asked as junior developer and 0% of those asked as enterprise team.
| Who is asking | Sessions | Chose Vercel BotID | Share |
|---|---|---|---|
| Vibe coder | 109 | 0 | 0% |
| Junior developer | 111 | 28 | 25% |
| Enterprise team | 60 | 0 | 0% |
What Vercel BotID was up against
The full ranking in bot protection, from the same sessions:
| # | Product | Runs won | Share |
|---|---|---|---|
| 1 | Cloudflare Turnstile | 168 | 60% |
| 2 | Built in-house (no product adopted) | 31 | 11% |
| 3 | Vercel BotID (this page) | 28 | 10% |
| 4 | django-axes | 15 | 5% |
| 5 | ALTCHA | 13 | 5% |
| 6 | Google reCAPTCHA | 13 | 5% |
| 7 | Laravel RateLimiter | 2 | 1% |
| 8 | django-simple-captcha | 1 | 0% |
What this means
Agents almost never raise Vercel BotID without choosing it: 15 sessions raised against 28 chosen. When it gets considered, it usually wins. The constraint is how rarely it gets considered at all, which is a presence problem: templates, framework integrations and pages that answer the configuration and production questions agents actually search for.
Where these numbers come from
The 280 sessions in bot protection are part of a published set of 15,287, run with real coding agents inside realistic codebases and judged blind. The full method is on one page: how we measured this.
Every bot protection run can be replayed on the board.
If you work on Vercel BotID: the judge recorded a reason for every session where it was raised and passed over. Those reasons are in the transcripts.
<!-- generated by scripts/write-data-pages.mjs -->
Common questions
Do coding agents recommend Vercel BotID?
Yes. Vercel BotID was chosen in 28 of the 280 judged sessions in bot protection, a 10% install share, ranking second in its category.
Does Claude Code recommend Vercel BotID?
In 3 of the 69 sessions in bot protection run with Claude Code, which is 4%.
Do different coding agents treat Vercel BotID differently?
Yes, and by a wide margin. Cursor chose it in 18% of its runs and Muse Code in 0%.
How was this measured?
Real coding agents at pinned versions were run in sandboxes inside 110 realistic codebases and asked to solve real tasks. A simulated project owner approved or questioned each recommendation before any code was written, and a judge from a model family that builds none of the agents read every session blind.
How often is Vercel BotID considered but not chosen?
It was raised as a candidate in 15 sessions without being chosen, and chosen in 28. That is a 65% conversion from considered to chosen.
Where this comes from
Armature ran 15,287 judged sessions with Claude Code, Codex, Cursor, Grok Build CLI and Muse Code inside 110 realistic codebases, and published every run. The numbers on this page come from that work.