1 minTime to key
YesNo-human path
0Gates to a test key
10/10Onboarding score
Live keys only:Email verification
Fastest path to a key
- zero-account: POST https://claimable.neon.tech/v1/agent/identity {type:anonymous, capabilities:[postgres,data_api,auth], source:<agent>} returns identity_assertion + project
- exchange the assertion (jwt-bearer grant) at /v1/oauth2/token for a bearer token; GET /v1/projects/{id}/credentials returns DATABASE_URL (or CLI: `neon claim create` writes .env)
- later: `neon claim accept --no-open` / POST /claim returns a verification_uri_complete; human signs in and accepts the transfer (code TTL 900s, project TTL 72h)
- with an account: `npm i -g neon && neon login` (browser OAuth) then `neon api-keys create` mints an API key from the CLI
- MCP: `npx neon@latest mcp` (writes config for detected agents) or the Claude connector directory, OAuth
- Working API key
Biggest gap
Unclaimed projects die at 72h and DATABASE_URL rotates on claim, so the agent must re-fetch credentials. The domain move from neon.tech and the CLI rename from neonctl to neon may confuse agents trained on older data
Worth copying
auth.md: a spec-like, agent-addressed provisioning procedure (anonymous identity, jwt-bearer token, credentials, device-code claim) that is reachable straight from llms.txt
Add the badge to your README
[](https://agentsready.dev/c/neon.com)