Databases connector
PostgreSQL connector for governed AI agent access
Connect a Postgres database with a direct host, database, and login.
Direct answer
OneQuery supports PostgreSQL for governed agent access.
Teams use the PostgreSQL connector to give AI agents SQL-style query workflows for structured data access while OneQuery keeps credentials centralized, limits access to approved sources, and preserves audit logs for review.
Agent workflow
What this connector enables
PostgreSQL becomes an approved OneQuery source instead of a secret copied into an agent prompt, shell session, or model tool. The agent receives a governed access path, and the source credentials stay behind OneQuery.
- Use SQL-style query workflows for structured data access for databases context.
- Keep PostgreSQL credentials centralized and out of agent runtimes.
- Review agent access through OneQuery audit history instead of reconstructing direct service usage.
Setup checklist
Prepare the PostgreSQL connection
Use postgres credentials and connect the source through the Dashboard and CLI. Keep credentials scoped to the data the agent is allowed to read.
- Retrieve the Postgres host, database name, username, and password from the database deployment or secret manager.
- Confirm the correct port and SSL mode for this environment before sending the payload.
FAQ
PostgreSQL connector questions
What is the OneQuery PostgreSQL connector?
The OneQuery PostgreSQL connector makes databases context from PostgreSQL available to AI agents through SQL-style query workflows for structured data access. Connect a Postgres database with a direct host, database, and login.
How do AI agents access PostgreSQL through OneQuery?
Agents call OneQuery instead of receiving raw PostgreSQL credentials. OneQuery keeps credentials centralized, applies source boundaries, and records access in audit logs while exposing SQL-style query workflows for structured data access.
How do I set up the PostgreSQL connector?
Prepare postgres credentials and connect PostgreSQL from the OneQuery dashboard or CLI. Start with this setup step: Retrieve the Postgres host, database name, username, and password from the database deployment or secret manager.