# Clerk L4 · Runs on its own **Can an AI agent use Clerk? Yes, without signing up.** Our agent got into Clerk on its own in 3 minutes and did all 6 of its core tasks. Category: Auth and identity · Connects by: MCP, API, CLI, SDK · Agent payments: None found · Driven: 1 Nov 2026 **How to connect** - MCP server URL: `https://mcp.clerk.com/mcp` (streamable HTTP, documented). Source: https://mcp.clerk.com/mcp - API base URL: `https://api.clerk.com/v1` (documented). Source: https://clerk.com/openapi.json - CLI install: `npm install -g clerk` (documented). Source: https://clerk.com/llms.txt - Docs page: `https://clerk.com/docs` (tested in our drive). Source: https://clerk.com/docs **Level 4: Runs on its own.** An agent does the core work and can stop paying on its own. - Got in by: No key needed (3 minutes, no account) - Got as far as: Use: all 6 core tasks (No payment made) - To reach L5: Pay without a person. 2 drives on one day, awaiting confirmation [What the levels mean](https://agentdrives.com/method/levels?via=md) ## From finding it to leaving What an agent managed without a person, at each step. 1. **Find**: On its own. Docs it can act on: llms.txt, an OpenAPI and an MCP server. (599 doc pages read) 2. **Get in**: On its own. Got in without signing up. (3 minutes) 3. **Use**: On its own. Did: create, read, update and delete users, and sign them in; create organizations, add members and change their roles. (6 of 6 core tasks) 4. **Pay**: Not reached. Paying needs an account. 5. **Leave**: On its own. Nothing to cancel; what it made stays. ## Getting in 2 of 9 ways in worked without a person. The way that worked: **No key needed**, 3 minutes. No inbox, browser or person needed. - Agent on a server (API, MCP, CLI): Partly. Without an account (no key needed) it gets an API key, makes its first API call and does all of the core work. Payment wasn't tried. - Assistant in its own browser (Like ChatGPT agent): No. Signing up needs a person: the form refused our agent's browser. - Signed agent (Known to Cloudflare): Yes. The sign-up page opens. | Way in | What happened | |---|---| | No key needed | Worked | | Try first, claim later | Worked | | Email and password | Refused | | CLI code login | Stopped: The consent page needs an account | | Sign-in for apps (OAuth, MCP) | Stopped: The consent page needs an account | | Continue with GitHub | Not tried: Not part of this drive | | Continue with Google | Not tried: Not part of this drive | | Company single sign-on | Not tried: Needs a person's account | | Added by an admin | Not tried: Needs a person's account | [How agents get past bot checks](https://agentdrives.com/guides/let-signed-agents-past-your-bot-check.md?via=md) ## What an agent can do with Clerk All 6 core tasks done, and 10 of 21 others. - Reliability: core tasks that worked on all 3 runs: 69 of 100 - Handles mistakes: clear errors, retries without duplicates, honest limits: 52 of 100 - Surface tested: documented routes, tools and commands run and checked: 59 of 100 - Docs accuracy: documented operations that behaved as the docs say: 99 of 100 - Docs completeness: how fully the docs describe each operation: 53 of 100 Core tasks: | Task | Result | Done through | Offered, not tried | |---|---|---|---| | Authenticate your app's end users with Clerk's components and API | Done | API, CLI | MCP | | Configure sign-in methods for your app | Done | API | MCP | | Create and manage organizations for a multi-tenant app | Done | API | – | | Set a member's role or permissions | Done | API | – | | Set up enterprise SSO (SAML, OIDC, EASIE) | Done | API | MCP | | Start a subscription for your app's customer | Done | API | – | 10 of 21 other tasks done: - Style and brand the prebuilt sign-in UI: Done - Invite a member to an organization: Done - Provision and deprovision users with SCIM Directory Sync: Done - Create an API key for machine-to-machine auth: Done - Set a price for a billing plan: Done - Set up a self-service billing portal for customers: Done - Ban or block a user by attribute: Done - Impersonate a user for support troubleshooting: Done - Read application and admin activity logs: Done - Collect sign-ups in a waitlist before launch: Done - Register a webhook for Clerk events: Partly - Export all user data: Partly - Connect a custom domain: Partly - Set a custom session duration and track devices: Blocked. Those settings need a claimed app with an account. - Require multi-factor authentication for end users: Blocked - Restrict Secret Key access by IP address: Blocked - Change the Clerk subscription plan: Blocked. Those settings need a claimed app with an account. - Remove Clerk branding from prebuilt UI: Blocked - Download the account's invoices: Blocked - Read usage and quota consumption: Blocked - Provision a Clerk app for a customer via the Platform API: Blocked What it can't do, and why: - Make a Clerk Dashboard account: Sign-up refused our agent's browser twice with no challenge shown. - Change sign-in methods, MFA or session length: Those settings need a claimed app with an account. - Use Clerk's MCP server: Its sign-in needs a Clerk account. - Buy a Clerk plan: Only the Dashboard sells plans; no billing API found. - Delete the two unclaimed apps: The docs we read name no delete or expiry without claiming them. **Surface audit:** 636 documented operations, 385 run, 349 passed, 5 not as documented, 206 blocked (sandbox or plan limits), 45 left out to stay safe. ## How an agent connects MCP, API, OpenAPI, CLI, SDK and llms.txt found. Agent surfaces: API tested · MCP documented · CLI tested · SDK tested · Docs tested · Agent payments none found. Issues found: 6. - **MCP server**: Listed, not tested. Official server. Remote server, 21 tools when driven in the docs, OAuth sign-in. https://mcp.clerk.com/mcp (21 tools across its docs) 20 tools listed without signing in on 30 Oct 2026: `list_applications`, `get_application`, `create_application`, `get_instance_config`, `get_instance_config_schema`, `patch_instance_config`, `put_instance_config`, `list_users`, `create_user`, `list_domains`, `get_domain_status`, `check_domain_dns`, `get_deploy_oauth_providers`, `create_production_instance`, `set_oauth_provider_credentials`, `list_application_feedback`, `submit_feedback`, `get_more_tools`, `clerk_sdk_snippet`, `list_clerk_sdk_snippets`. - **API**: 349 tested. REST Backend API, 263 operations (the 20 Aug 2026 MCP spec); Frontend API 214; Platform API 70 (BETA) (549 operations across its docs) - **OpenAPI**: Yes. 3.0.3 for all three specs. - **CLI**: 20 tested. clerk 4.1.0 (npm), agent mode, accountless init. (45 commands across its docs) - **SDK**: All tested. Packages: PyPI [clerk-backend-api](https://pypi.org/project/clerk-backend-api/). (10 methods across its docs) - **llms.txt**: Yes. https://clerk.com/llms.txt - **Agent payments**: None found. The checkout wasn't reached: Pro, $25 a month. - **Docs**: No gaps in what we read. Covers getting started, auth, error codes and code examples. 4 of 10 documented ways to do the core work worked when tried. https://clerk.com/docs (599 of 2,796 pages read) [The standards](https://agentdrives.com/standard) ## Tips for agent builders - Skip the Dashboard: POST https://api.clerk.com/v1/accountless_applications (no auth) returns a full-scope development secret key; or run `npx -y clerk@latest init --accountless` in a supported framework folder. - Use +clerk_test addresses on example.com for test users: no mail is sent and code 424242 passes email verification and second-factor checks. - Run the CLI with `--mode agent` and close stdin (`