Can an AI agent use SuperTokens?
Rank among the 246 products we drove
- Steps on its own
- tied #3
- 4/ 5
- Find to Leave, no person
- Core work done
- tied #1
- 100%
- 10 of 10 core tasks
- Time to get in
- tied #83
- 8minutes
- Getting in on its own
Yes. Our agent signed up for SuperTokens on its own in a browser with an email and password, got an API key and used its API, MCP server and CLI.
The record
Level confirmed
Not yet
Level from one drive; a second must agree.
- Got in by
- Sign-up in a browser8 minutes
- Got as far as
- Pay: ready to payPayment not yet proven; stopped at the pay button of the $0.02 charge
Connects by
API, CLI, SDK
Agent payments
None found
On its own · 430 doc pages read
Docs it can act on: llms.txt.
On its own · 8 minutes
No key needed, runs locally, sign-up in a browser.
On its own · 10 of 10 core tasks
Did: create, list, find, update and delete end users; create, check and revoke sessions.
Partly
Ready to pay. Payment not yet proven; stopped at the pay button of the $0.02 charge.
On its own
Nothing to cancel. It deletes its account.
- On its own
- Partly
To reach L5: Pay without a person.
See how it ranks among auth providers for agents.
Own SuperTokens? 7 things to fix. Get your findings, free
Checked 17 Nov 2026: llms.txt changed since the check before, sign-up page unchanged since the check before.
Find
How an agent connects
API, CLI, SDK and llms.txt found.
MCP server
All testedA server for searching the docs only.
4 tools mapped in our drive
API
192 of 205 testedCore Driver Interface (REST, api-key header) plus the Frontend Driver Interface served by the backend SDKs; 205 operations on the docs reference.
205 operations mapped in our drive
OpenAPI
UnknownCLI
All testedsupertokens CLI manages a self-hosted core process (start, list, stop, uninstall).
5 commands mapped in our drive
SDK
All testedsupertokens-node 24.1.0; Python and Go backend SDKs documented.
- npmsupertokens-node
- npmsupertokens-auth-react
- npmsupertokens-web-js
- PyPIsupertokens-python
- npm@supertokens/rownd-react
12 methods mapped in our drive
llms.txt
YesAgent payments
None foundWalked to the last click ("Deploy Production Core") and stopped: Production core (usage-based), $0.02 a call. It checks out through Stripe Checkout. No CAPTCHA at checkout.
Docs
In partCovers getting started, auth, error codes and code examples.
Describes each operation only in part: completeness 50 of 100.
10 of 10 documented ways to do the core work worked.
430 of 530 pages read
Changed since it was driven
Checked daily
- llms.txt: 9 links added, 268 removed and 4 sections changed
Get in
Getting in
Our agent tried 3 of 4 ways in; 3 worked without a person.
The way that worked
Sign-up in a browser8 minutes
- An inboxNeeded
- A browserNeeded
- A personNot needed
- Agent on a serverAPI, MCP, CLIPartlyGets in without a browser (runs locally) and does 2 of its 10 core tasks that way. For a full account, it stops at sign-up: it works only in a browser.
- Assistant in its own browserLike ChatGPT agentPartlySigns up and does all of the core work. Payment: ready to pay, payment not yet proven; stopped at the pay button of the $0.02 charge.
- Signed agentKnown to CloudflareYesThe site opens.
Every way in
| Way in | What happened | Why |
|---|---|---|
| Sign-up in a browser | Worked | |
| Runs locally | Worked | Part of the work done |
| No key needed | Worked | |
| Company single sign-on | Not tried | Not part of this drive |
Use
What an agent can do with SuperTokens
All 10 core tasks done, and 21 of 22 others.
Core tasks
- done there
| Task | Result | Through |
|---|---|---|
| Register an end user in your app with email and password | Done | API: done there |
| Send an end user a passwordless magic link or OTP code | Done | API: done there |
| Configure a social or enterprise login provider for your app | Done | API: done there |
| Create a session for an end user | Done | API: done there |
| Revoke an end user's sessions | Done | API: done there |
| List and look up your app's end users | Done | API: done there |
| Delete an end user | Done | API: done there |
| Create a role with permissions and assign it to an end user | Done | API: done there |
| Create a tenant for an organisation | Done | API: done there |
| Enrol an end user in TOTP multi-factor authentication | Done | API: done there |
Surface audit: 230 documented operations: 216 run, 8 blocked by sandbox or plan limits and 6 left out because they spend money or reach real people. Of the 216 run, 210 passed and 6 didn't; 8 behaved differently from the docs. By surface, 192 on the API, 12 in the SDK, 5 in the CLI, 4 on the MCP server and 3 elsewhere, such as sign-in and webhooks.
Holds up
92of 100
- Reliability100
- Handles mistakes83
The mean of the two, 91.5, with a half rounded to the even number.
Docs match
82of 100
- Docs accuracy96
- Docs completeness50
Docs accuracy counts 70%, completeness 30%.
Surface tested
94of 100
210 of 224 passed: the 230 documented operations less the 6 that spend money or reach real people
What it can't do, and why
- Sign up for SuperTokens Cloud without a browser Only a web form was found; no documented sign-up API.
- Create or revoke Cloud API keys through a documented API The agent did it in the dashboard; no documented API or CLI for keys was found.
- Switch on paid-style features like MFA from code The feature switches were only found in the dashboard.
- Use the Attack Protection Suite It is a paid add-on, switched off on the free test server.
- Pay for a production core without a person No agent payment route or documented billing API was found.
- Delete the account through an API The agent deleted it in the dashboard; no documented delete API was found.
21 of 22 other tasks done
- Verify an end user's email addressDone
- Reset an end user's passwordDone
- Link two end user accounts into oneDone
- Store custom metadata on an end userDone
- Register a passkey for an end userDone
- Import users from another auth providerDone
- Map an external user ID to an end userDone
- Register an OAuth2 client for unified loginDone
- Issue a machine-to-machine access tokenDone
- Create a signed JWTDone
- Add a SAML connection for a tenantDone
- Ban or unban an end userDone
- Impersonate an end user for supportDone
- Customise the prebuilt sign-in and sign-up formsDone
- Send auth emails through your own SMTP serverDone
- Add login to an agent tool server you hostDone
- Read active user countsDone
- Add a dashboard admin userDone
- Create an app in a multi-app setupDone
- Restrict core access by IP addressDone
- Start or stop a self-hosted core instanceDone
- Detect suspicious sign-ins with the Attack Protection SuiteIt is a paid add-on, switched off on the free test server.Paid plan
- Export auth traces with OpenTelemetryNot tried
The plans they need
- Enrol an end user in TOTP multi-factor authenticationMFA add-on ($0.01/MAU, minimum $100/month per pricing)
The drive used the free plan.
Tips for agent builders
- Self-host the core image (supertokens/supertokens-postgresql) for a no-account sandbox with an in-memory database.
- On Cloud, do sign-up and key retrieval once in the browser, then drive everything over the CDI with the api-key header.
- Send the rid header (emailpassword, passwordless, thirdparty) on the shared /recipe/user paths.
- Call /recipe/oauth/auth on the core as POST with a params object, and send access_token and id_token objects to /recipe/oauth/token.
- Switch on MFA, account linking, SSO and M2M in the dashboard's Features page: they are free in development.
- For FDI WebAuthn routes, use the paths the SDK serves (/webauthn/options/register, /webauthn/options/signin).
Pay
Paying
Ways to pay checked 3 Nov 2026.
- ResultPartly. Ready to pay. Payment not yet proven; stopped at the pay button of the $0.02 charge.
- CheckoutWalked to the last click ("Deploy Production Core") and stopped: Production core (usage-based), $0.02 a call. It checks out through Stripe Checkout. No CAPTCHA at checkout.
- TrialIt has a free plan.
Leave
Leaving
- ResultOn its own. Nothing to cancel. It deletes its account.
- Its accountYes, in a browser, without a human. The agent deleted the account in the browser (Delete Account, typed confirmation). Sign-in then answered 'Account Deletion in Progress' and within minutes the core host stopped resolving. No documented API to delete an account was found.
Daily checks
Checked every day
What our agent finds on the product's own site each day, without an account.
Sign-up page,
Loads on the newest check; 15 of 15 days
llms.txt,
Found on the newest check; 15 of 15 days
MCP server,
Answers with an error on the newest check; 4 of 15 days
OpenAPI,
Found on the newest check; 1 of 15 days
Compare
How SuperTokens compares
In Auth and identity
None of the 9 products we drove in Auth and identity is higher; 1 other shares L4. As of 15 Nov 2026.
| Product | Level | Find to leave |
|---|---|---|
| FusionAuth | L4 | Find: On its own, Get in: On its own, Use: On its own, Pay: Not tried, Leave: On its own. |
| PropelAuth | L1 | Find: On its own, Get in: Stopped, Use: Not reached, Pay: Not reached, Leave: Not reached. |
| SuperTokens (this page) | L4 | Find: On its own, Get in: On its own, Use: On its own, Pay: Partly, Leave: On its own. |
| Clerk | L3 | Find: On its own, Get in: On its own, Use: On its own, Pay: Not tried, Leave: Partly. |
| WorkOS | L3 | Find: On its own, Get in: On its own, Use: On its own, Pay: Not tried, Leave: Partly. |
| Auth0 | L3 | Find: On its own, Get in: On its own, Use: On its own, Pay: Stopped, Leave: Partly. |
| Kinde | L3 | Find: On its own, Get in: On its own, Use: On its own, Pay: Partly, Leave: Partly. |
| HumanMirror | L3 | Find: Partly, Get in: On its own, Use: Partly, Pay: On its own, Leave: Partly. |
| Web3Auth (MetaMask Embedded Wallets) | L3 | Find: Partly, Get in: On its own, Use: Partly, Pay: Partly, Leave: Partly. |
For the team behind SuperTokens
Agents get stuck at Pay
7 things to fix for agents: 3 small, 3 medium and 1 large
One fix can cover several findings.
Agent blockers: 6 foundAgent surfaces: 8 issues found
Get your findings, freeWhat a drive covers
We mail a private link to an address at supertokens.com.
It opens the two findings that matter most in full, and every other by title. There is nothing to sign in to.
- FindClear
- Get inClear
- UseClear
- PayBlocks agents
- LeaveClear
Or claim SuperTokens to see where each issue is and ask for a free drive after a fix.
Want SuperTokens driven every month? See Watch
On our standard
Best or ahead on 4 of 24 criteria, behind on 6. Each against the other auth and identity products we measured on it.
- Every way in works for an agentAhead of 6 of 7 others, 1 the same.
- Docs an agent can navigateAhead of 5 of 7 others, 2 the same.
- Versions an agent can pinAhead of 3 of 5 others, 2 the same.
- Delete by API, checkedAhead of 5 of 7 others, 1 the same, 1 higher.
- A path written for agentsBehind 4 of 7 others, 3 the same.
- Results sized for a context windowBehind 3 of 5 others, 2 the same.
- Errors a program can readBehind 4 of 6 others, 2 the same.
- Answers sized for an agentThe lowest result All 4 others higher.
All 24 criteria
- The best way in is built for agentsLevel with 4 of 7 others, 3 lower.
- Prices an agent can readLevel with 5 of 7 others, 2 lower.
- Real status codesLevel with 6 of 7 others, 1 lower.
- A way in with no personLevel with 7 of 8 others, 1 lower.
- llms.txt that worksLevel with 6 of 8 others, 1 lower, 1 higher.
- Fast to the first callThe same as all 6 others.
- Terms allow an agent's accountThe same as all 8 others.
- Structured resultsIn the middle 2 of 5 others lower, 1 the same, 2 higher.
- Errors say what to do nextThe same as all 6 others.
- Export before leavingIn the middle 2 of 7 others lower, 3 the same, 2 higher.
- An agent payment rail on the coreLevel with 7 of 8 others, 1 higher.
- Pages fit one fetchLevel with 6 of 7 others, 1 higher.
- Spend an agent can see and capLevel with 6 of 7 others, 1 higher.
- A request id on every answerIn the middle 1 of 7 others lower, 3 the same, 3 higher.
- One way to page through listsTied for the lowest result 2 of 4 others the same, 2 higher.
- Limits known before they hitTied for the lowest result 2 of 4 others the same, 2 higher.
Where SuperTokens fits
- Tasks
- Standards
- llms.txtits docs, listed for agents
- Topics
- Docs and llms.txtFind step
- Sign-upGet in step
- Card checkoutPay step
- Delete the accountLeave step
- Rivals
- FusionAuthL4
- Auth0L3
- ClerkL3
History
Level by drive
One drive so far, on 3 Nov 2026.
One drive so far.
Read more on this step
Pay is where our agent stopped at SuperTokens.
- Guide · 18 Nov 2026How AI agents pay for software: x402, MPP and checkoutsCard checkouts, x402 and MPP: what an agent can pay with today, and what most products ask instead.Read
- Guide · 31 Oct 2026Bot checks on SaaS checkouts: where AI agents stopAs of 31 Oct 2026: 42 of 59 SaaS checkouts our agent reached on 31 Oct 2026 carried a bot check; under 5 made it solve one. 80 of 139 stopped earlier. What to fix so an agent can buy.Read
- Guide · 28 Oct 2026Tell an AI agent a feature needs a paid planHow to answer an AI agent at a paid-plan wall: 402 or 403, a Problem Details body with the required plan, and an upgrade link a person can open.Read
Every earlier drive is in the history. The level follows these rules. Data under CC BY 4.0.
Found an error? Tell us on this page or read how corrections work.
Questions people ask about SuperTokens
- Can an AI agent create a SuperTokens account on its own?
- Yes, in a browser, without a person. Cloud sign-up through the browser form at supertokens.com/auth (name, email, password). No CAPTCHA. Asked for a full name; our agent answered. The self-hosted core needs no account.
- Does SuperTokens have an MCP server, and can an agent connect to it?
- SuperTokens's docs have an MCP server for searching them. The drive found no MCP server that works the product itself. The server lists 4 tools and speaks the 25 Nov 2025 MCP spec. A new agent can get in on its own: in the drive of 3 Nov 2026, our agent signed up and got its key without a person.
- How does an AI agent get a SuperTokens API key?
- In the drive of 3 Nov 2026, our agent got its SuperTokens API key in a browser, without a person. On Cloud the agent generated, listed and deleted core API keys in the dashboard in its own browser; no documented API for keys was found. Using the key is done without a browser. A revoked key got 401 within seconds. Self-hosted keys are set in config (API_KEYS), without a browser.
- Can an AI agent delete its SuperTokens account?
- Yes, in a browser, without a human. The agent deleted the account in the browser (Delete Account, typed confirmation). Sign-in then answered 'Account Deletion in Progress' and within minutes the core host stopped resolving. No documented API to delete an account was found.
- Can an AI agent pay for SuperTokens?
- Partly. Ready to pay: payment not yet proven; stopped at the pay button of the $0.02 charge. It has a free plan.
Cite this page
The page as a reference, in plain text, APA and BibTeX.
Cite this
AgentDrives, “SuperTokens: AI agent test drive”, 3 November 2026, https://agentdrives.com/tools/supertokens. CC BY 4.0.
AgentDrives. (2026, November 3). SuperTokens: AI agent test drive. https://agentdrives.com/tools/supertokens
@misc{agentdrives_supertokens_2026,
author = {{AgentDrives}},
title = {SuperTokens: AI agent test drive},
year = {2026},
month = nov,
url = {https://agentdrives.com/tools/supertokens},
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.