clerk.com — AI Readiness Score: 90/100

doclight — ai Readiness Report

clerk.com

Pages analyzed (12)

llms.txt included https://clerk.com/llms.txt 200
llms-full.txt included https://clerk.com/llms-full.txt 200
llms.txt included https://docs.clerk.com/llms.txt 200
llms-full.txt included https://docs.clerk.com/llms-full.txt 200
marketing included https://clerk.com/ 200
pricing included https://clerk.com/pricing 200
docs included https://clerk.com/docs/quickstart 200
api https://dashboard.clerk.com/~/api-keys 404
docs included https://docs.clerk.com/ 200
docs https://docs.clerk.com/docs/guides/development/integrations/overview 404
docs https://docs.clerk.com/docs/reference/overview 404
marketing https://dashboard.clerk.com/ 404

llms.txt found

AI READINESS SCORE

Clerk is a comprehensive user management and authentication platform offering embeddable UI components, flexible APIs, SDKs across 20+ frameworks, and admin dashboards. It handles sign-up/sign-in, user profiles, organization (B2B) management, session management, billing/subscriptions, and machine authentication (API keys, M2M tokens). Developers can integrate it via prebuilt React-style components, hooks, backend SDKs, a CLI, and a Backend API.

Dimension Breakdown

Discoverability

Clear product positioning, llms.txt index files, and multiple framework-specific entry points make this trivially discoverable and categorizable.

Comprehension

The product's purpose as auth/user management is stated explicitly across marketing, docs, and llms.txt with feature breakdowns.

Setup clarity

Step-by-step quickstarts, a CLI with clerk init auto-detection, and copy-paste prompts make setup very clear for agents.

Documentation

Extensive docs with full llms-full.txt content, SDK references, and backend method-level documentation are available for agents.

Pricing clarity

Pricing tiers, MRU limits, add-ons, and per-unit costs are detailed and even offered in markdown form, though some volume discounts are hidden behind expanders.

Integration examples

Many code snippets, CLI commands, and component examples exist, but no formal OpenAPI/Swagger spec was found for the Backend API.

Agent Journey

✓

Discover

✓

Understand

✓

Setup

✓

Use

Confusion Points

low Some pricing volume discounts and limitations are hidden behind 'Show' expanders not present in crawled text https://clerk.com/pricing
low proxy.ts vs middleware.ts naming depends on Next.js version, which could confuse an agent applying defaults https://clerk.com/docs/quickstart

Missing Information

Is there a formal OpenAPI/Swagger spec for the Backend API for automated client generation?
What are the exact rate limits and quotas for API Keys and M2M tokens per plan?
What authentication scheme and base URLs does the raw Backend API use directly (without the CLI/SDK)?

Improvements

Publish a machine-readable OpenAPI/Swagger spec for the Frontend and Backend APIs to enable automated client generation.
Include full pricing details (volume discounts, hidden limitations) directly in the markdown pricing version rather than behind UI expanders.
Add explicit raw HTTP examples (curl with auth headers and base URLs) alongside SDK examples for agents not using the CLI/SDK.
Clarify version-dependent setup choices (e.g., proxy.ts vs middleware.ts) with a decision rule an agent can deterministically follow.