Uploaded September 2026 | Updated September 2026, 1 hour ago
Your coding agent needs a database. You’re away from the keyboard. With Claimable Neon, it can keep building and let you claim the project later.
CHAPTERS
0:00 When signup stops your coding agent
1:01 Create a database now, claim later
2:40 How agents discover Neon’s auth.md
3:41 Build auth.md on existing APIs
5:33 Takeaways and resources
Chantastic joins Andre Landgraf from Neon for a demo of claimable Postgres databases powered by auth.md. Andre shows how a single Neon CLI command creates a temporary project without signing in, provides a database connection string, and gives the user a link to transfer the project into their own Neon organization.
We look at how agents discover the flow through Neon’s auth.md file, where the CLI and REST API fit, and what happens if nobody claims the project within 72 hours. The demo also touches on the Data API and Managed Better Auth.
Then Andre explains how he built the integration using Neon’s existing public APIs, a subdomain, and a Markdown file. It’s a practical example of making an existing service accessible to agents without redesigning its human signup process.
LINKS
Full interview with Andre Landgraf:
youtu.be/i0OrcGqPAUk
WorkOS case study:
workos.com/blog/neon-claimable-postgres-auth-md-case-study
Neon announcement:
neon.com/blog/an-agent-provisions-a-neon-backend-a-human-claims-it-later
Neon’s video on X:
https://x.com/neondatabase/status/2098050196127273272/video/1
Your coding agent needs a database. You’re away from the keyboard. With Claimable Neon, it can keep building and let you claim the project later.
CHAPTERS
0:00 When signup stops your coding agent
1:01 Create a database now, claim later
2:40 How agents discover Neon’s auth.md
3:41 Build auth.md on existing APIs
5:33 Takeaways and resources
Chantastic joins Andre Landgraf from Neon for a demo of claimable Postgres databases powered by auth.md. Andre shows how a single Neon CLI command creates a temporary project without signing in, provides a database connection string, and gives the user a link to transfer the project into their own Neon organization.
We look at how agents discover the flow through Neon’s auth.md file, where the CLI and REST API fit, and what happens if nobody claims the project within 72 hours. The demo also touches on the Data API and Managed Better Auth.
Then Andre explains how he built the integration using Neon’s existing public APIs, a subdomain, and a Markdown file. It’s a practical example of making an existing service accessible to agents without redesigning its human signup process.
LINKS
Full interview with Andre Landgraf:
youtu.be/i0OrcGqPAUk
WorkOS case study:
workos.com/blog/neon-claimable-postgres-auth-md-case-study
Neon announcement:
neon.com/blog/an-agent-provisions-a-neon-backend-a-human-claims-it-later
Neon’s video on X:
https://x.com/neondatabase/status/2098050196127273272/video/1
