How Neon made Postgres claimable for agents with auth.md

Neon’s Claimable Neon implementation uses the auth.md protocol to let agents provision a temporary, restricted Postgres project when no human account or API key is available, allowing development to continue until a person can take ownership. Agents discover the appropriate registration flow through Neon’s published metadata, use anonymous registration to request supported capabilities such as Postgres, the Data API, and Managed Better Auth, and must inspect which services were actually granted. Unclaimed projects are limited to 72 hours, 100 MB of storage, and 1 GB of transfer, while some services require a completed claim. Neon separates a durable registration assertion from short-lived access tokens, reducing reliance on a person’s existing credentials but requiring agents to protect the assertion until the project is claimed, expires, or is revoked. A human can claim a project through a short-lived URL, after which Neon transfers it to an organization, revokes temporary access, rotates database credentials, and ultimately invalidates the agent’s assertion. The approach demonstrates how auth.md can provide agents with discoverable, bounded access to stateful infrastructure while preserving service-defined controls, quotas, and explicit human ownership transfer.

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.