Can an AI agent use WorkOS?

WorkOS is a developer service for authentication, single sign-on and user management, with organizations, roles, audit logs and SCIM directories.

workos.comAuth and identity

Driven 2 Nov 2026

Evidence sha256 89cc30e0JSONMarkdownFeedCite

L3

Does the work

  1. L0
  2. L1
  3. L2
  4. L3
  5. L4
  6. L5

Rank among the 246 products we drove

Time to get in
tied #6
1minute
Getting in on its own
Core work done
tied #50
90%
9 of 10 core tasks
Steps on its own
tied #35
3/ 5
Find to Leave, no person
Holds up
tied #92
67/ 100
Reliability under errors

Yes. Our agent got into WorkOS on its own without signing up, got an API key and used its API and CLI. It also has an MCP server. It offers agents a way to pay: Stripe Projects.

The record

Level confirmed

Not yet

Level from one drive; a second must agree.

Got in by
Try first, claim later1 minute, no account
Got as far as
Use: 9 of 10 core tasksNo payment made

Connects by

MCP, API, CLI

Agent payments

Stripe Projects; our agent didn't try it

  1. Find

    On its own · 600 doc pages read

    Docs it can act on: llms.txt, an OpenAPI and an MCP server.

  2. Get in

    On its own · 1 minute

    Got in without signing up. Email and code: stopped by a phone number; CLI code login: stopped by a phone number.

  3. Use

    On its own · 9 of 10 core tasks

    Did: create and delete organizations and add members; send, read and revoke invitations that reach a real inbox.

  4. Pay

    Not tried · 1 way for agents to pay

    Paying needs an account.

  5. Leave

    Partly

    Nothing to cancel. Its key still works after leaving.

  • On its own
  • Not tried
  • Partly

To reach L4: Remove what it made.

Checked 17 Nov 2026: MCP server asks for a sign-in, llms.txt and OpenAPI unchanged since the check before.

Find

How an agent connects

MCP, API, OpenAPI, CLI, agent payments and llms.txt found.

  • MCP server

    Listed, not tested

    Official server. Https://mcp.workos.com/mcp, OAuth only (PRM, CIMD, DCR). Sign‑in needed to see its tools.

    mcp.workos.com/mcp

    1 tool mapped in our drive, none of them called

  • API

    195 of 271 tested

    REST, OpenAPI 3.1.1.

    271 operations mapped in our drive

  • OpenAPI

    Yes

    A machine-readable description of the API.

  • CLI

    76 of 132 tested

    npm package workos 0.24.0 (npx workos@latest).

    132 commands mapped in our drive

  • SDK

    None found
  • llms.txt

    Yes
  • Agent payments

    Listed, not tested

    Stripe Projects.

    The checkout wasn't reached.

    Stripe Directory lists it as @workos, with Stripe Projects. Stripe Docs, 10 Nov 2026

  • Docs

    In part

    Covers getting started, auth, error codes and code examples.

    Describes each operation only in part: completeness 75 of 100.

    10 of 17 documented ways to do the core work worked.

    workos.com/docs

    600 of 946 pages read

Changed since it was driven

Checked daily

  • OpenAPI: 4 endpoints added
  • llms.txt: 23 links added, 839 removed and 37 sections changed
  • llms.txt: 1 link added
  • llms.txt: 4 links added

Get in

Getting in

Our agent tried 6 of 12 ways in; 1 worked without a person.

The way that worked

Try first, claim later1 minute

  • An inboxNot needed
  • A browserNot needed
  • A personNot needed
  • Agent on a serverAPI, MCP, CLIPartlySigns up, gets an API key, makes its first API call and does 9 of its 10 core tasks, then stops: its key still works after leaving. It can't delete what it made.
  • Assistant in its own browserLike ChatGPT agentPartlySigns up and does 9 of its 10 core tasks, then stops: its key still works after leaving. It can't delete what it made.
  • Signed agentKnown to CloudflareYesOur signed agent got through Cloudflare at sign-up.

Every way in

Every way in and what happened
Way inWhat happenedWhy
Try first, claim laterWorked
Registration through auth.mdStoppedThe consent page needs an account
Email and codeStopped by a phone number
Email and passwordNot reached
CLI code loginStopped by a phone number
Sign-in for apps (OAuth)StoppedThe consent page needs an account
Identity assertionStopped by the sign-in provider
Email linkNot triedThe same as another way
Continue with GoogleNot triedNot part of this drive
Company single sign-onNot triedNeeds a person's account
Added by an adminNot triedNeeds a person's account
A key from a personNot triedNeeds a person's account
  • CrawlersThe robots.txt on api.workos.com asks crawlers to stay off sign-up. Nothing to fix.
  • Bot checkCloudflare let our agent through at sign-up. Our agent signs every request (Web Bot Auth).

Use

What an agent can do with WorkOS

9 of 10 core tasks done, and 16 of 24 others.

Core tasks

  • done there
  • tried, not done
  • offered, not tried
Core tasks of WorkOS: the result and the surfaces they went through
TaskResultThrough
Create a user in AuthKitDoneAPI: done there
Create an organization for a customerDoneAPI: done thereCLI: offered, not tried
Set up an SSO connection for an organizationDoneAPI: done thereCLI: offered, not tried
Sign a user in through SSODoneAPI: done there
Sync users and groups from a corporate directoryDoneAPI: done thereCLI: done there
Record an audit log eventDoneAPI: done thereCLI: done there
Invite a user to an organizationDoneAPI: done thereCLI: offered, not tried
Create a role with permissionsDoneAPI: done thereCLI: offered, not tried
Delete a userDoneAPI: done thereCLI: offered, not tried
Check a sign-in attempt for bots and fraud with RadarThe API says Radar is not enabled and only support can enable it.BlockedAPI: tried, not done

Surface audit: 529 documented operations: 285 run, 225 blocked by sandbox or plan limits and 19 left out because they spend money or reach real people. Of the 285 run, 227 passed and 58 didn't; 52 behaved differently from the docs. By surface, 195 on the API, 76 in the CLI and 14 elsewhere, such as sign-in and webhooks.

  • Holds up

    67of 100

    • Reliability76
    • Handles mistakes58

    The mean of the two.

  • Docs match

    80of 100

    • Docs accuracy82
    • Docs completeness75

    Docs accuracy counts 70%, completeness 30%.

  • Surface tested

    45of 100

    227 of 509 passed: the 529 documented operations less the 20 that spend money or reach real people

  • What it can't do, and why

    • Check sign-in attempts with standalone Radar The API says Radar is not enabled and only support can enable it.
    • Create SSO connections through the API That part of the API is not enabled for the environment.
    • Open a dashboard account Sign-up asks for a mobile phone number.
    • Delete the test environment or revoke its key No documented route does either.
    • Pay for a production plan Billing is only in the dashboard; there is no billing API or agent payment rail.

16 of 24 other tasks done

  • Assign a role to an organization memberDone
  • Export audit log eventsDone
  • Define an audit log event schemaDone
  • Enroll an MFA factor for a userDone
  • Generate an Admin Portal link for a customer's IT adminDone
  • Check fine-grained access to a resourceDone
  • Encrypt and store an object in VaultDone
  • Register a webhook endpointDone
  • Read the events streamDone
  • Issue an API key to a customer organizationDone
  • Revoke a user sessionDone
  • Register an OAuth application with WorkOS ConnectDone
  • Run a local WorkOS emulator for testingDone
  • Import users from another auth providerDone
  • Block or allow an identifier in RadarDone
  • Configure redirect URIs and CORS originsDone
  • Verify an organization's domainPartly
  • Connect a custom domain for AuthKitPaid plan
  • Send a passwordless magic auth codeBlocked
  • Connect a user's third-party account with PipesBlocked
  • Turn a feature flag on for an organizationBlocked
  • Register an agent identity for sign-upBlocked
  • Set the AuthKit brandingBlocked
  • Invite a teammate to the WorkOS dashboardBlocked
  • Create a new environmentBlocked

The drive used the free plan.

Tips for agent builders

From this drive

6 tips
  • Read https://workos.com/auth.md and call POST /x/one-shot-environments to get an sk_test key; store the claim_token without logging it.
  • Define an audit log schema before sending events with that action.
  • Use POST /portal/generate_link with intent sso or dsync to configure SSO and SCIM; the SCIM endpoint and token let you provision directory users yourself.
  • Poll after DELETE /organizations: it answers 202 and the read returns 404 a moment later.
  • Use workos api <path> with an API key where the CLI's resource commands ask for a dashboard login.
  • Invite only real inboxes: domains without MX records are refused.

Pay

Paying

Ways to pay checked 2 Nov 2026.

  • ResultNot tried. Paying needs an account.
  • Ways to pay
    • Stripe Projects (through Stripe's catalog)
  • TrialIt has a free plan.

Leave

Leaving

  • ResultPartly. Nothing to cancel. Its key still works after leaving.
  • Its accountNo: our agent used WorkOS without an account, and it can't delete what it made. Everything the drive made inside it was deleted by API, except a few items with no delete route.

Daily checks

Checked every day

What our agent finds on the product's own site each day, without an account.

  • Sign-up page,

    Stopped on the newest check; 15 of 15 days

  • llms.txt,

    Found on the newest check; 15 of 15 days

  • MCP server,

    Asks for a sign-in on the newest check; 15 of 15 days

  • OpenAPI,

    Found on the newest check; 15 of 15 days

Compare

How WorkOS compares

In Auth and identity

2 of the 9 products we drove in Auth and identity are higher; 5 others share L3. As of 15 Nov 2026.

The products we drove in Auth and identity, in the directory's order, with WorkOS
ProductLevelFind to leave
FusionAuthL4Find: On its own, Get in: On its own, Use: On its own, Pay: Not tried, Leave: On its own.
PropelAuthL1Find: On its own, Get in: Stopped, Use: Not reached, Pay: Not reached, Leave: Not reached.
SuperTokensL4Find: On its own, Get in: On its own, Use: On its own, Pay: Partly, Leave: On its own.
ClerkL3Find: On its own, Get in: On its own, Use: On its own, Pay: Not tried, Leave: Partly.
WorkOS (this page)L3Find: On its own, Get in: On its own, Use: On its own, Pay: Not tried, Leave: Partly.
Auth0L3Find: On its own, Get in: On its own, Use: On its own, Pay: Stopped, Leave: Partly.
KindeL3Find: On its own, Get in: On its own, Use: On its own, Pay: Partly, Leave: Partly.
HumanMirrorL3Find: Partly, Get in: On its own, Use: Partly, Pay: On its own, Leave: Partly.
Web3Auth (MetaMask Embedded Wallets)L3Find: Partly, Get in: On its own, Use: Partly, Pay: Partly, Leave: Partly.

For the team behind WorkOS

Our agent got through Leave only in part, and didn't try Pay

9 things to fix for agents: 4 small, 4 medium and 1 large

One fix can cover several findings.

Agent blockers: 5 found, none stopped the driveAgent surfaces: 52 issues found

Get your findings, freeWhat a drive covers

We mail a private link to an address at workos.com.

  1. FindClear
  2. Get inClear
  3. UseClear
  4. PayNot tried
  5. LeavePartly

Or claim WorkOS to see where each issue is, read your safety findings with their fixes and ask for a free drive after a fix.

Want WorkOS driven every month? See Watch

On our standard

Best or ahead on 10 of 28 criteria, behind on 1. Each against the products we measured on it.

All 28 criteria
  • Limits known before they hitAhead of 3 of 4 others (auth and identity products), 1 the same.
  • Docs an agent can navigateAhead of 5 of 7 others (auth and identity products), 2 the same.
  • A path written for agentsAhead of 4 of 7 others (auth and identity products), 3 the same.
  • A person can claim what the agent madeAhead of 13 of 23 others (every product), 10 the same.
  • Answers sized for an agentTied for the best result 2 of 4 others (auth and identity products) the same, 2 lower.
  • Errors a program can readTied for the best result 3 of 6 others (auth and identity products) the same, 3 lower.
  • The best way in is built for agentsLevel with 4 of 7 others (auth and identity products), 3 lower.
  • Sign-in for agents acting for a personLevel with 3 of 5 others (auth and identity products), 2 lower.
  • Prices an agent can readLevel with 5 of 7 others (auth and identity products), 2 lower.
  • Real status codesLevel with 6 of 7 others (auth and identity products), 1 lower.
  • A way in with no personLevel with 7 of 8 others (auth and identity products), 1 lower.
  • llms.txt that worksLevel with 6 of 8 others (auth and identity products), 1 lower, 1 higher.
  • Fast to the first callThe same as all 6 others (auth and identity products).
  • Terms allow an agent's accountThe same as all 8 others (auth and identity products).
  • Errors say what to do nextThe same as all 6 others (auth and identity products).
  • An agent payment rail on the coreLevel with 7 of 8 others (auth and identity products), 1 higher.
  • Pages fit one fetchLevel with 6 of 7 others (auth and identity products), 1 higher.
  • Spend an agent can see and capLevel with 6 of 7 others (auth and identity products), 1 higher.
  • A plan an agent can buy by APILevel with 5 of 6 others (auth and identity products), 1 higher.
  • Every way in works for an agentLevel with 5 of 7 others (auth and identity products), 2 higher.
How each criterion is graded

Where WorkOS fits

History

Level by drive

One drive so far, on 2 Nov 2026.

Source: our drives of WorkOS. As of 2 Nov 2026.
  1. 11 Nov 2026Level L4 → L3Re-scored under method v47, drive of 2 Nov 2026

Related research

Guides and findings on the Use step.

Every earlier drive is in the history. The level follows these rules. Data under CC BY 4.0.

Found an error? or read how corrections work.

Questions people ask about WorkOS

Can an AI agent create a WorkOS account on its own?
Yes, over the API, without a browser. The dashboard sign-up separately stops at a Radar phone check.
Does WorkOS have an MCP server, and can an agent connect to it?
Yes. WorkOS has an official MCP server. The server is hosted and signs an agent in with OAuth. A new agent can get in on its own: in the drive of 2 Nov 2026, our agent signed up and got its key without a person.
How does an AI agent get a WorkOS API key?
In the drive of 2 Nov 2026, our agent got its WorkOS API key over the API, without a browser or a person. 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.
Can an AI agent delete its WorkOS account?
No: our agent used WorkOS without an account, and it can't delete what it made. Everything the drive made inside it was deleted by API, except a few items with no delete route.
Can an AI agent pay for WorkOS?
No payment made: paying needs an account. It has a free plan. WorkOS offers agents a way to pay: Stripe Projects.

Cite this page

The page as a reference, in plain text, APA and BibTeX.

Cite this
Plain
AgentDrives, “WorkOS: AI agent test drive”, 2 November 2026, https://agentdrives.com/tools/workos. CC BY 4.0.
APA
AgentDrives. (2026, November 2). WorkOS: AI agent test drive. https://agentdrives.com/tools/workos
BibTeX
@misc{agentdrives_workos_2026,
  author = {{AgentDrives}},
  title = {WorkOS: AI agent test drive},
  year = {2026},
  month = nov,
  url = {https://agentdrives.com/tools/workos},
  note = {Agent test drive, CC BY 4.0},
}

Something wrong on this page?

We check it against the drive and correct the page, with the date.