Data & AI · wired today
Drive Neon with governed agents
Models and datasets are infrastructure now, and agents need eyes on them. The Neon connector is one of 205 executable connectors and gives agents 4 read-only tools, with the credential held in the vault and every call receipted.
What agents can run against Neon
| Tool | What it does |
|---|---|
list_projects | List the Neon projects this API key can see, with region, Postgres version, proxy host and ownership |
get_project | Get one Neon project by ID, with region, Postgres version, history retention and storage size |
list_branches | List the branches in one Neon project, with state, parent branch, logical size and default or protected status |
list_databases | List the databases on one branch of a Neon project, with owning role and creation time |
Every tool above is read-only. Write surfaces ship only after live testing, and always behind approval gates.
What the Neon connector needs
You provide API key from your Neon account; Quox sends it as a bearer token. The credential is stored encrypted in the vault and resolved just-in-time, so agents use it without ever seeing it.
Where to get it: Neon's own API documentation ↗ covers creating and scoping the credential.
How proven is this?
This connector was blind shape-proven against the real Neon API: every endpoint it declares answered measurably differently from a deliberately bogus control request, without any account or credential involved. It is Beta: proven against the live API surface, not yet run with a real credential.
Neon integration FAQ
What can Quox agents do with Neon?
Agents can run 4 read-only tools against Neon: list projects, get project, list branches, list databases. Every call is receipted in the evidence trail.
What does the Neon integration need?
You provide API key from your Neon account; Quox sends it as a bearer token. The credential is stored encrypted in the vault and resolved just-in-time, so agents use it without ever seeing it.
Do agents see my Neon credentials?
No. Credentials live encrypted in the Quox vault and are resolved server-side at call time. Agents invoke tools; they never receive the underlying secret.
How proven is the Neon connector?
This connector was blind shape-proven against the real Neon API: every endpoint it declares answered measurably differently from a deliberately bogus control request, without any account or credential involved. It is Beta: proven against the live API surface, not yet run with a real credential.