Clerk vs WorkOS for AI agents

As of 2 Nov 2026, both reach L3 (Does the work). With each, our agent got in and met its first wall at deleting the account (blocked).

AgentDrives StudyClerk: 2 drives, last 1 Nov 2026 (169 attempts). WorkOS: 1 drive, last 2 Nov 2026 (200 attempts). Method v50.

ClerkL3Does the work
  • Find Docs it can act on
  • Get in No key needed, try first, claim later
  • Use 100% of the work
  • Pay No payment made
  • Leave Nothing to cancel; its key still works after leaving

Got in; first wall at deleting the account (blocked). Next: remove what it made

Clerk is a service that adds sign-in and user management to apps. An agent got a working development app and key with one open call, no account needed, and ran users, organizations, single sign-on, webhooks and subscriptions on it.

Driven 1 Nov 2026 · The drive and its evidence
WorkOSL3Does the work
  • Find Docs it can act on
  • Get in Try first, claim later
  • Use 90% of the work
  • Pay No payment made
  • Leave Nothing to cancel; its key still works after leaving

Got in; first wall at deleting the account (blocked). Next: remove what it made

WorkOS is a developer service for sign-in, single sign-on and user management. An agent got a working test key with one call and no account, and used almost all of the core features on its own. It stopped at the dashboard sign-up, which asks for a mobile phone number.

Driven 2 Nov 2026 · The drive and its evidence

The two summaries: written with AI from each product's drive.

Step by step

What our agent got done at each step, and what it saw there.

Find

ClerkDocs it can act on

llms.txt, auth.md, SKILL.md, OpenAPI 3.0.3 specs (Backend 263 ops, Platform 70 ops) and every docs page as .md, all fetched without a browser.

WorkOSDocs it can act on

Docs public as Markdown with llms.txt and an OpenAPI 3.1.1 spec (269 operations); auth.md tells agents how to get in.

Get in

ClerkNo key needed, try first, claim later

The 201 of the accountless POST carries a full-scope development secret key (sk_test_). No route makes a scoped Clerk key without an account.

WorkOSTry first, claim later

No documented route makes a scoped key for the WorkOS API or revokes the environment key; organization API keys were created, validated and revoked without a browser.

Use

Clerk100% of the work

WorkOS90% of the work

Pay

ClerkNo payment made

Only a card checkout, which an agent can finish once a person gives it a card.

WorkOSNo payment made

Pays only through a card checkout a person does.

Leave

ClerkNothing to cancel; its key still works after leaving

The two accountless apps stay: their users, orgs, connections, directories, machines, OAuth apps, templates, domains and the webhook (Svix) app were deleted through the API and read back empty, but the apps have no delete route without a Clerk account and both secret keys still answer 200; two rejected waitlist entries refuse deletion (409); session 2's two test users and machine were deleted and read back gone (users count 0, machines 0).

WorkOSNothing to cancel; its key still works after leaving

Everything the drive made inside it was deleted by API, except a few items with no delete route.

Every attempt of each drive: Clerk WorkOS

Where each one stops

ClerkGot in; first wall at deleting the account (blocked)

WorkOSGot in; first wall at deleting the account (blocked)

Clerk and WorkOS, checkpoint by checkpoint
CheckpointClerkWorkOS
DocsOn its ownOn its own
Sign upOn its ownOn its own
VerifyNot neededNot needed
KeyOn its ownOn its own
First callOn its ownOn its own
First actionOn its ownOn its own
PayNot triedNot tried
CancelNot neededNot needed
DeleteBlockedBlocked

On its own, or in a browser

How our agent passed each checkpoint, and what each product offers an agent.

Checkpoints by route, API, MCP, CLI and SDK
Checkpoints by how our agent passed them, and what each product offers an agent
ClerkWorkOS
Passed on its own55
Passed in a browser00
Needed a person00
Blocked11
Work done100% of the core90% of the core
APIYesYes
OpenAPIYesYes
MCP serverYes (official)Yes (official)
CLIYesYes
SDKYesNo
llms.txtYesYes

Bot checks, and where a person was needed

Walls our agent met
ClerkWorkOS
Bot checkClerk's own bot protection (client.protect.clerk.com probes) stopped one way in (CLI code login) at sign up; it got in another wayCloudflare let it through at sign up
Wall typeA check of our network and browserNo bot-check wall
First wallGot in; first wall at deleting the account (blocked)Got in; first wall at deleting the account (blocked)
A person helpedNoNo

A check of our network and browser: It judged where our agent connected from and its browser, not a person. Our agent, working on its own from a data center, didn't get through; the owner can open the check to agents. How agents in a person's own browser fare isn't measured yet. Where we drive from.

Level and part scores

Clerk and WorkOS: level and part scores, 0 to 100
ClerkWorkOS
LevelL3 · Does the workL3 · Does the work
Holds up62 of 100, poor67 of 100, poor
Docs match76 of 100, fair80 of 100, fair
StandardsMCP client registration (current) · OpenAPI 3.0.3 (2 versions behind)MCP client registration (current) · OpenAPI 3.1.1 (1 version behind)
SecurityReported privately to the ownerReported privately to the owner

Pay, cancel and delete

Paying, cancelling and deleting the account
ClerkWorkOS
PayNo payment madeNo payment made
Free plan or trialFree planFree plan
CancelNot neededNot needed
Delete the accountBlockedBlocked
How each one takes payment
  • Clerk: No payment made: paying needs an account.
  • WorkOS: No payment made: paying needs an account.

Clerk vs WorkOS: the short answers

Which can an AI agent use, Clerk or WorkOS?

Both reach L3 (Does the work). With each, our agent got in and met its first wall at deleting the account (blocked). Driven 1 Nov 2026 (Clerk) and 2 Nov 2026 (WorkOS).

Can an AI agent sign up for Clerk and WorkOS on its own?

Clerk: yes, on its own. WorkOS: yes, on its own.

Do Clerk and WorkOS have an MCP server?

Clerk: yes (official). WorkOS: yes (official).

Can an AI agent delete its Clerk or WorkOS account?

Clerk: blocked. WorkOS: blocked.

The drives and the category

Put your own shortlist side by side

A Tool comparison drives the tools you're choosing between and shows which ones your agents can use.