Report card

Do AI agents pick Clerk?

How often agents choose Clerk when a developer needs authentication — measured across Claude, GPT, Gemini.

Clerk

#1 of 6 auth
15%Pick Rate
95% CI 10%21%

When developers ask an AI agent for auth, Clerk is picked 15% of the time — ranking #1 of 6 measured across Claude, GPT, Gemini.

Picked 15% Named, not picked 15% Never surfaced 71%

Top pick in the category. 🟢

Awareness

5.9M package downloads / week

Known but not preferred — widely used, but agents pick competitors. That's a preference problem, not awareness.

0 docs in FineWeb (10BT sample) · 412 URLs in Common Crawl

In the raw web crawl, but thin in the filtered corpus models actually train on — an awareness gap at the source.

AdoptionDid the pick convert to installs? Public Adoption = npm downloads of your packages. The proof half of the funnel.

23.0M installs / month ▲ 8% MoM

Installs are roughly flat month over month.

Get the full report

The per-model and per-surface breakdown for Clerk — where it wins, where it loses, and to whom — plus an alert when the Pick Rate moves.

About Clerk

Clerk is a user authentication and identity management platform built for web applications.

Clerk handles sign-up, sign-in, session management, and user profiles so developers don't have to build auth infrastructure from scratch. It supports multiple authentication strategies including passwords, magic links, OAuth providers, and multi-factor authentication. Clerk is aimed at developers building web apps who want a fully managed auth solution with pre-built UI components.

Where to start

Start by creating a Clerk application in the Clerk dashboard to get your API keys, then install the Next.js SDK and wrap your app with the Clerk provider to enable authentication.

Install

Links and summary verified from public sources.

The rest of the Authentication ranking

← Full Authentication leaderboard · How this is measured