OneQuery Docs

OneQuery gives developers and agents one governed path to approved data sources. Connect a source once, use an identifier like postgres://warehouse, and keep raw credentials out of prompts, scripts, and agent environments.

Fast Path

1. Get started with the CLI and choose a shared, hosted, or local server path.
2. Connect one read-only source.
3. Run one query or provider API call.
4. Give agents only the source identifiers they need.

Getting started Install the CLI, choose a server path, connect a source, and run the first query.

Guide Step-by-step tasks for installing, choosing a server path, connecting, querying, and preparing agents.

Concepts Understand governed access, source identifiers, query boundaries, and audit history.

Integrations Connect databases, warehouses, observability tools, developer systems, and analytics sources.

Examples Apply OneQuery to production debugging, warehouse inspection, release review, and incident work.

Operations Run the gateway, keep credentials scoped, and review the security checklist before rollout.

Security Review the architecture, threat model, data handling, and cost-control guidance for agent access.

Support Collect the right troubleshooting context without sharing secrets or raw production data.

Reference Look up CLI commands, provider IDs, terminology, and common error guidance.