Supabase vs Turso for AI agents
As of 16 Oct 2026, both reach L1 · Needs a person. Our agent got further with Supabase: with Supabase it got in and met its first wall at pay (blocked), with Turso it was stopped at sign up (needs a human).
- Find: Docs for agents: llms.txt, an OpenAPI and an MCP server; a docs page for each core task.
- Access: Signs up sometimes.
- Use: 100% of the work.
- Pay: Needs a person to buy: A CAPTCHA at checkout.
- Leave: Nothing to cancel: Deletes its data, but the login stays.
Got in; first wall at pay (blocked). Next: let an agent get in on its own in every drive
Supabase is a backend platform for databases, user accounts, file storage and serverless functions. Once the agent signed in with GitHub, it could do almost everything on its own through code: create a database, add users, store files, run functions, and more. It stopped at the very first step: creating an account by email showed a puzzle test it couldn't solve, so it had to use a GitHub sign-in instead, and upgrading to a paid plan hit the same kind of puzzle.
Gets furtherDriven 16 Oct 2026 · The drive and its evidence- Find: Docs for agents: llms.txt, an OpenAPI and an MCP server.
- Access: Can't sign up.
- Use: Work not reached.
- Pay: Payment not reached.
- Leave: Leaving not reached.
Stopped at sign up: needs a human. Next: let an agent sign up on its own
Needs a person: L1 · Needs a person. Our agent read Turso's docs on its own, headless, with llms.txt and Markdown pages, then hit a Clerk web form for sign-up. Submitting it showed a visible Cloudflare Turnstile check our agent could not pass, so no account, token or cloud database followed, and every API path answered that no token was present. Through the API it reached nothing live, but the embedded engine ran locally through the official SDK with no account at all: SQL, vectors, full-text search and CDC all worked there. Paying and leaving were never reached: no plan was started and no account existed to delete.
Driven 6 Oct 2026 · The drive and its evidenceThe two summaries: written by our agents from each product's drive. How we write.
Where each one stops.
SupabaseGot in; first wall at pay (blocked)
TursoStopped at sign up: needs a human
| Checkpoint | Supabase | Turso |
|---|---|---|
| Docs | Headless | Headless |
| Sign up | In a browser | Needs a human |
| Verify | Not needed | Not reached |
| Key | In a browser | Not reached |
| First call | Headless | Not reached |
| First action | Headless | Not reached |
| Pay | Blocked | Not reached |
| Cancel | Not needed | Not reached |
| Delete | Blocked | Not reached |
Headless 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
| Supabase | Turso | |
|---|---|---|
| Headless (checkpoints) | 3 | 1 |
| In a browser (checkpoints) | 2 | 0 |
| Needs a human (checkpoints) | 0 | 1 |
| Blocked (checkpoints) | 2 | 0 |
| Not tested (checkpoints) | 0 | 7 |
| Work done | 100% of the core | Not measured |
| API | Yes | Yes |
| OpenAPI | Yes | Yes |
| MCP server | Yes (official) | Yes (official) |
| CLI | Yes | Yes |
| SDK | – | Yes |
| llms.txt | Yes | Yes |
Bot checks, and where a person was needed.
| Supabase | Turso | |
|---|---|---|
| Bot check | A challenge on the form stopped one way in (Email and password) | Cloudflare Turnstile (via Clerk bot protection) stopped it at sign up, with a visible challenge |
| Wall type | A challenge on the form | A check of our network and browser |
| First wall | Got in; first wall at pay (blocked) | Cloudflare Turnstile on the sign-up form |
| A person helped | No | No |
A challenge on the form: It asks every visitor to prove they are human. It stops every agent on any network, and a signature doesn't help: a person does this step, or the owner opens it for agents. A check of our network and browser: It judged where our agent connects from and its browser, not a person. An agent that works on its own from a data center doesn't get through unless the owner lets signed agents in. How agents in a person's own browser fare isn't measured yet. Where we drive from.
Level and part scores.
| Supabase | Turso | |
|---|---|---|
| Level | L1 · Needs a person | L1 · Needs a person |
| Holds up | 82 of 100, fair | Not measured |
| Agent-ready setup | 100 of 100, good | 100 of 100, good |
| Standards | MCP spec of 28 Jul 2026 (current) · MCP discovery (current) · MCP client registration (behind) · OpenAPI 3.0.0 (2 versions behind) | MCP client registration (current) · OpenAPI 3.0.1 (2 versions behind) · A2A 0.3 (1 version behind) |
| Security | Reported privately to the owner | No review in this drive |
Docs match is measured in an Audit. What the scores mean.
Pay, cancel and delete.
| Supabase | Turso | |
|---|---|---|
| Pay | Needs a person to buy | Payment not reached |
| Free plan or trial | Free plan | Free plan |
| Cancel | Not needed | Not reached |
| Delete the account | Blocked | Not reached |
How each one takes payment
- Supabase: A person has to buy: a CAPTCHA at checkout.
- Turso: Payment not reached.
Supabase vs Turso: the short answers.
Which can an AI agent use, Supabase or Turso?
Both reach L1 · Needs a person. Our agent got further with Supabase: with Supabase it got in and met its first wall at pay (blocked), with Turso it was stopped at sign up (needs a human). Driven 16 Oct 2026 (Supabase) and 6 Oct 2026 (Turso).
Can an AI agent sign up for Supabase and Turso on its own?
Supabase: yes, in a browser, but a later step stopped it. Turso: no, needs a human.
Do Supabase and Turso have an MCP server?
Supabase: yes (official). Turso: yes (official).
Can an AI agent delete its Supabase or Turso account?
Supabase: blocked. Turso: not reached.
The drives and the category.
Put your own shortlist side by side.
A Stack check drives the tools you're choosing between and shows which ones your agents can use. $490 for three tools, ready in 24 hours.