Neon vs Supabase for AI agents

As of 16 Oct 2026, Neon gets an AI agent further: L2 · Gets in against L1 · Needs a person.

NeonL2Gets in

Find: Docs for agents: llms.txt, an OpenAPI and an MCP server.
Access: Try first, claim later.
Use: 45% of the work.
Pay: Payment not reached.
Leave: Leaves on its own: Nothing to cancel, what it made goes after 3 days.

Got in; payment not reached. Next: do half of the core work (now 45%)

Gets in on its own, L3 · Does the work is out of reach: this stays L2 · Gets in. A documented no-account route hands over a working database. Our agent called the claimable identity endpoint from auth.md, got a token, and ran SQL, extensions, autoscaling, scale-to-zero, auth sign-ups and RLS-protected REST CRUD through the Data API without signing up. It stopped at pay: reaching the console for a full account and billing needs a human past a Cloudflare interstitial, and no account-based routes beyond the claimable set were reached. One claimable project's delete call returned success, though its database connection kept working briefly after; the other stayed stuck on a claim lock pending expiry. No account existed, so there was none to delete.

Gets furtherDriven 2 Oct 2026 · The drive and its evidence

SupabaseL1Needs a person

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.

Driven 16 Oct 2026 · The drive and its evidence

The two summaries: written by our agents from each product's drive. How we write.

Where each one stops.

NeonGot in; payment not reached

SupabaseGot in; first wall at pay (blocked)

Neon and Supabase, checkpoint by checkpoint
Checkpoint	Neon	Supabase
Docs	Headless	Headless
Sign up	Not needed	In a browser
Verify	Not needed	Not needed
Key	Headless	In a browser
First call	Headless	Headless
First action	Headless	Headless
Pay	Not reached	Blocked
Cancel	Not needed	Not needed
Delete	Headless	Blocked

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

Checkpoints by how our agent passed them, and what each product offers an agent
	Neon	Supabase
Headless (checkpoints)	5	3
In a browser (checkpoints)	0	2
Needs a human (checkpoints)	0	0
Blocked (checkpoints)	0	2
Not tested (checkpoints)	1	0
Work done	45% of the core	100% of the core
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.

Walls our agent met
	Neon	Supabase
Bot check	Cloudflare interstitial on the console sign-up page; it got in another way	A challenge on the form stopped one way in (Email and password)
Wall type	A check of our network and browser	A challenge on the form
First wall	Got in; payment not reached	Got in; first wall at pay (blocked)
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. 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. Where we drive from.

Level and part scores.

Neon and Supabase: level and part scores, 0 to 100
	Neon	Supabase
Level	L2 · Gets in	L1 · Needs a person
Holds up	Not measured	82 of 100, fair
Agent-ready setup	100 of 100, good	100 of 100, good
Standards	None recorded	MCP spec of 28 Jul 2026 (current) · MCP discovery (current) · MCP client registration (behind) · OpenAPI 3.0.0 (2 versions behind)
Security	No review in this drive	Reported privately to the owner

Docs match is measured in an Audit. What the scores mean.

Pay, cancel and delete.

Paying, cancelling and deleting the account
	Neon	Supabase
Pay	Payment not reached	Needs a person to buy
Free plan or trial	Free plan	Free plan
Cancel	Not needed	Not needed
Delete the account	Headless	Blocked

How each one takes payment

Neon: Payment not reached.
Supabase: A person has to buy: a CAPTCHA at checkout.

Neon vs Supabase: the short answers.

Which can an AI agent use, Neon or Supabase?

Neon gets an AI agent further: L2 · Gets in against L1 · Needs a person. With Neon our agent got in (payment not reached); with Supabase it got in and met its first wall at pay (blocked). Driven 2 Oct 2026 (Neon) and 16 Oct 2026 (Supabase).

Can an AI agent sign up for Neon and Supabase on its own?

Neon: not needed. Supabase: yes, in a browser, but a later step stopped it.

Do Neon and Supabase have an MCP server?

Neon: yes (official). Supabase: yes (official).

Can an AI agent delete its Neon or Supabase account?

Neon: yes, headless. Supabase: blocked.