clerk.com llms.txt
In short
clerk.com serves a 5.8 KB llms.txt with 15 H2 sections and 54 links, graded A on the llmstxt.org structure (6 of 6 checks). It passes every check. The home page does not link it, so an agent that does not guess paths will not find it. An llms-full.txt is served too. Read 4 November 2026.
llms.txt 5.8 KB, 103 lines
# Clerk
> Clerk is user management for developers: sign-up, sign-in, and prebuilt UI components, multi-tenant organizations, enterprise SSO, subscription billing, and machine-to-machine auth, with SDKs for Next.js, React, and most web and mobile frameworks.
For AI agents and automation, use the tools and markdown surfaces below. Append `.md` to any `/docs`, `/articles`, `/blog`, `/changelog`, or `/glossary` URL to get the page as markdown.
## When to use Clerk
Use Clerk when an application needs sign-up, sign-in, and user management: prebuilt UI components, social login, MFA, multi-tenant organizations, enterprise SSO and SCIM, subscription billing, or machine-to-machine and API-key auth. Point a coding agent at the skill below or install the CLI; API specs are under API references.
## Agent setup
- [Clerk Skills](https://clerk.com/SKILL.md): One file that routes a coding agent to the right framework-specific skill
- [Clerk CLI](https://clerk.com/docs/cli.md): Commands, flags, and agent workflows. Install with `npm install -g clerk` or the [install script](https://clerk.com/install)
- [Clerk MCP server](https://mcp.clerk.com/mcp): Sign in once and let an agent read and configure your Clerk apps from an MCP client. Follow the [setup guide](https://clerk.com/docs/guides/ai/mcp/clerk-mcp-server.md)
- [Agent registration](https://clerk.com/auth.md): Provision an accountless Clerk application and keys without an account
- [Skills discovery](https://clerk.com/.well-known/agent-skills/index.json): Every individually published skill
- [Ship auth with AI agents](https://clerk.com/agents): How agent-driven Clerk setup works, end to end
## SDKs
Quickstart for each official Clerk SDK.
- [Next.js](https://clerk.com/docs/nextjs/getting-started/quickstart.md)
- [React](https://clerk.com/docs/react/getting-started/quickstart.md)
- [Expo](https://clerk.com/docs/expo/getting-started/quickstart.md)
- [TanStack React Start](https://clerk.com/docs/tanstack-react-start/getting-started/quickstart.md)
- [React Router](https://clerk.com/docs/react-router/getting-started/quickstart.md)
- [Android](https://clerk.com/docs/android/getting-started/quickstart.md)
- [Astro](https://clerk.com/docs/astro/getting-started/quickstart.md)
- [Chrome Extension](https://clerk.com/docs/chrome-extension/getting-started/quickstart.md)
- [Electron](https://clerk.com/docs/electron/getting-started/quickstart.md)
- [iOS](https://clerk.com/docs/ios/getting-started/quickstart.md)
- [JavaScript](https://clerk.com/docs/js-frontend/getting-started/quickstart.md)
- [Nuxt](https://clerk.com/docs/nuxt/getting-started/quickstart.md)
- [Vue](https://clerk.com/docs/vue/getting-started/quickstart.md)
- [Express](https://clerk.com/docs/expressjs/getting-started/quickstart.md)
- [C#](https://github.com/clerk/clerk-sdk-csharp/blob/main/README.md)
- [Fastify](https://clerk.com/docs/fastify/getting-started/quickstart.md)
- [Go](https://clerk.com/docs/go/getting-started/quickstart.md)
- [Java](https://github.com/clerk/clerk-sdk-java)
- [PHP](https://github.com/clerk/clerk-sdk-php)
- [Python](https://github.com/clerk/clerk-sdk-python/blob/main/README.md)
- [Ruby on Rails](https://clerk.com/docs/ruby/getting-started/quickstart.md)
## Products
- [User Authentication](https://clerk.com/user-authentication): Sign-up, sign-in, MFA, social login, and prebuilt components
- [Enterprise Authentication](https://clerk.com/enterprise-authentication): SAML, OIDC, and SCIM for B2B SaaS
- [Multi-tenancy](https://clerk.com/multi-tenancy): Organizations, roles, and invitations
- [Billing](https://clerk.com/billing): Subscriptions without payment code
- [Platform](https://clerk.com/platform): White-label Clerk for the apps your customers build
- [Waitlist](https://clerk.com/waitlist): Gather interest and invite early testers
## Documentation
- [Documentation home](https://clerk.com/docs.md): Explore by feature, frontend framework, and backend framework
- [Documentation index](https://clerk.com/docs/llms.txt): Every docs page with a one-line description
- [Documentation search](https://clerk.com/docs/search.md): Search the docs with `?q=<query>`, optional `&sdk=<sdk>`; returns markdown links to `.md` pages
## Dashboard
- [Dashboard index](https://dashboard.clerk.com/llms.txt): Every Dashboard route, grouped by auth scope, with access notes
## API references
- [Backend API](https://clerk.com/openapi.json): OpenAPI spec as JSON, or [YAML](https://clerk.com/openapi.yaml)
- [Frontend API](https://clerk.com/docs/reference/spec/fapi/latest.json): OpenAPI spec as JSON, or [YAML](https://clerk.com/docs/reference/spec/fapi/latest.yml)
- [Platform API](https://clerk.com/docs/reference/spec/platform/latest.json): OpenAPI spec as JSON, or [YAML](https://clerk.com/docs/reference/spec/platform/latest.yml)
First 69 of 103 lines.
Parse graded A, 6 of 6
file: https://clerk.com/llms.txt
Clerk
Clerk is user management for developers: sign-up, sign-in, and prebuilt UI components, multi-tenant organizations, enterprise SSO, subscription billing, and machine-to-machine auth, with SDKs for Next.js, React, and most web and mobile frameworks.
15 sections, 54 links, an Optional section.
Ora's cached score: 90, grade A, scanned 5 November 2026.
The parse
clerk.com lists 54 links: 50 point at clerk.com or a relative path, 4 point elsewhere. The hosts it links most: clerk.com (48), github.com (4), dashboard.clerk.com (1), mcp.clerk.com (1).
| H2 section | Links |
|---|---|
| When to use Clerk | 0 |
| Agent setup | 8 |
| SDKs | 21 |
| Products | 6 |
| Documentation | 3 |
| Dashboard | 1 |
| API references | 6 |
| Pricing | 1 |
| Security and compliance | 1 |
| Articles | 1 |
| Blog | 1 |
| Changelog | 1 |
| Glossary | 1 |
| Legal | 1 |
| Optional | 2 |
Grade against the llmstxt.org structure
The file passes all six checks. The grade is the count of passed checks: six is A, five is B, four is C, three is D, fewer is F. It measures structure only. Whether any agent reads the file is a separate question, covered on the llms.txt reference.
| Check | Result | Detail |
|---|---|---|
| Starts with an H1 naming the site or project | Pass | H1: Clerk |
| Has a blockquote summary under the H1 | Pass | Blockquote summary found. |
| Has at least one H2 section that lists links | Pass | 15 H2 sections, 14 with links. |
| At least 80 percent of links point at the same site | Pass | 50 of 54 links stay on clerk.com (93 percent). |
| Under 100 KB | Pass | 5901 bytes as served. |
| Plain markdown, no HTML | Pass | No HTML document markers in the body. |
Ora's cached score
Ora's cached report for clerk.com gives it 90 of 100, grade A, scanned on 5 November 2026. Its Access layer, which holds the read-layer checks below, scored 61 of 64 check points. Read from GET ora.ai/api/score/clerk.com on 5 November 2026. The score is Ora's, not this site's, and the structure grade above is a different measure: it grades the llms.txt file against the llmstxt.org proposal, while Ora's score covers the whole site. Ora's report for clerk.com has every layer.
| Ora check (Access layer) | Result | Points |
|---|---|---|
| Sitemap exists | Pass | 2 of 2 |
| Content without JavaScript | Partial | 2 of 3 |
| Not blocked by bot detection | Pass | 2 of 2 |
| Markdown URL fallback | Partial | 1 of 2 |
| llms.txt exists | Pass | 1 of 1 |
| llms.txt formatting | Pass | 2 of 2 |
| JSON-LD structured data | Pass | 4 of 4 |
| Metadata completeness | Pass | 2 of 2 |
| llms.txt links resolve | Pass | 2 of 2 |
| Markdown alternate link | Fail | 0 of 1 |
| Redirect hygiene | Pass | 1 of 1 |
| Page token budget | Pass | 1 of 1 |
| Code fence validity | Pass | 1 of 1 |
| Content behind auth | Pass | 2 of 2 |
| OpenAPI spec published | Pass | 7 of 7 |
| Markdown agent docs | Pass | 1 of 1 |
| Markdown negotiation with Vary | Pass | 1 of 1 |
| Markdown for agent user agents | Fail | 0 of 1 |
| Agent crawler reachability | Pass | 2 of 2 |
Linking and the companion file
The home page of clerk.com does not link the file in its HTML. Ora's lab found (2026-10-19) that 86 percent of llms.txt fetches by agents arrived through a link, so an unlinked file is mostly a file nobody opens. An llms-full.txt is served at the same root.
How it compares
At 5.8 KB the file is larger than 39 percent of the 2,529 plain-text llms.txt files in this edition, and its 54 links put it ahead of 63 percent of them on link count. The home page declares no generator. Size bucket: 2 to 10 KB. Tranco rank 3,144. Category: Identity & Auth.
Live file: https://clerk.com/llms.txt. Read 4 November 2026. If the file has since changed or gone, the live URL is the authority; this page records what the crawl read on that date.
Sources
- clerk.com llms.txt https://clerk.com/llms.txt, read 4 November 2026
- llms.txt proposal (llmstxt.org) https://llmstxt.org/, read 4 November 2026
- Tranco list 746WX (crawl universe) https://tranco-list.eu/list/746WX, read 4 November 2026
- Ora: AgentReady launch post (the 86 percent finding) https://ora.ai/blog/agentready-launch, read 4 November 2026
- Ora llms.txt (GET /api/score/{domain} looks up a cached score) https://ora.ai/llms.txt, read 5 November 2026
Last reviewed 5 November 2026