Convex vs Turso for AI agents
As of 6 Oct 2026, Convex gets an AI agent further: L3 · Does the work against L1 · Needs a person.
- Find: Docs for agents: llms.txt, an OpenAPI and an MCP server.
- Access: Runs locally: Can't sign up for one.
- Use: 70% of the work.
- Pay: Payment not reached.
- Leave: Leaves on its own: Nothing to cancel, made nothing to delete.
Got in; payment not reached. Next: let an agent sign up for an account on its own (without one it does 70% of the core work)
Gets in on its own, L3 · Does the work: a documented no-account route provisions a local deployment, where our agent pushed schema and functions, inserted and patched documents, ran an HTTP action, a cron and a scheduler, and set env vars, each checked back. The cloud side stopped at sign-up: a visible Cloudflare "Verify you are human" challenge blocked account creation, so no cloud project, deploy key or MCP session followed. Core backend work, plus file storage, text and vector search, custom-JWT auth and live subscriptions, ran on the local deployment; cloud paying and account deletion stayed out of reach, since both sit behind that same human checkpoint and the dashboard.
Gets furtherDriven 2 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 and checked by our agents from each product's drive. How we write.
Where each one stops.
ConvexGot in; payment not reached
TursoStopped at sign up: needs a human
| Checkpoint | Convex | Turso |
|---|---|---|
| Docs | Headless | Headless |
| Sign up | Not needed | Needs a human |
| Verify | Not needed | Not reached |
| Key | Not needed | Not reached |
| First call | Headless | Not reached |
| First action | Headless | Not reached |
| Pay | Not reached | 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
| Convex | Turso | |
|---|---|---|
| Headless (checkpoints) | 3 | 1 |
| In a browser (checkpoints) | 0 | 0 |
| Needs a human (checkpoints) | 0 | 1 |
| Blocked (checkpoints) | 1 | 0 |
| Not tested (checkpoints) | 1 | 7 |
| Work done | 70% of the core | Not measured |
| API | Yes | Yes |
| OpenAPI | Yes | Yes |
| MCP server | Yes (official) | Yes (official) |
| CLI | Yes | Yes |
| SDK | Yes | Yes |
| llms.txt | Yes | Yes |
Bot checks, and where a person was needed.
| Convex | Turso | |
|---|---|---|
| Bot check | Cloudflare human check on the sign-up page; it got in another way | Cloudflare Turnstile (via Clerk bot protection) stopped it at sign up, with a visible challenge |
| Wall type | A check of our network and browser | A check of our network and browser |
| First wall | Got in; payment not reached | Cloudflare Turnstile on the sign-up form |
| A person helped | No | No |
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.
| Convex | Turso | |
|---|---|---|
| Level | L3 · Does the work | L1 · Needs a person |
| Agent-ready setup | 100 of 100, good | 100 of 100, good |
| Standards | None recorded | MCP client registration (current) · OpenAPI 3.0.1 (2 versions behind) · A2A 0.3 (1 version behind) |
Holds up: not measured in these drives. Docs match is measured in an Audit. What the scores mean.
Pay, cancel and delete.
| Convex | Turso | |
|---|---|---|
| Pay | Payment not reached | 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
- Convex: Payment not reached.
- Turso: Payment not reached.
Convex vs Turso: the short answers.
Which can an AI agent use, Convex or Turso?
Convex gets an AI agent further: L3 · Does the work against L1 · Needs a person. With Convex our agent got in (payment not reached); with Turso it was stopped at sign up (needs a human). Driven 2 Oct 2026 (Convex) and 6 Oct 2026 (Turso).
Can an AI agent sign up for Convex and Turso on its own?
Convex: not needed. Turso: no, needs a human.
Do Convex and Turso have an MCP server?
Convex: yes (official). Turso: yes (official).
Can an AI agent delete its Convex or Turso account?
Convex: 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.