Data & AI · wired today
Drive dbt Cloud with governed agents
Models and datasets are infrastructure now, and agents need eyes on them. The dbt Cloud 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 dbt Cloud
| Tool | What it does |
|---|---|
list_accounts | List the dbt Cloud accounts the service token can see, with plan and state. Returns the account IDs every other dbt Cloud call is scoped by |
list_projects | List the projects on one dbt Cloud account (get the account_id from list_accounts) |
list_jobs | List the job definitions on one dbt Cloud account, optionally narrowed to a single project (get the IDs from list_accounts and list_projects). Definitions only: no job is triggered |
list_runs | List job runs on one dbt Cloud account, newest first, optionally narrowed to a single job definition (get the IDs from list_accounts and list_jobs). Returns status, git ref and timings per run |
Every tool above is read-only. Write surfaces ship only after live testing, and always behind approval gates.
What the dbt Cloud connector needs
You provide API token, account ID from your dbt Cloud account; Quox sends it as an API key sent as a header. 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: dbt Cloud's own API documentation ↗ covers creating and scoping the credential.
How proven is this?
This connector was blind shape-proven against the real dbt Cloud 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.
dbt Cloud integration FAQ
What can Quox agents do with dbt Cloud?
Agents can run 4 read-only tools against dbt Cloud: list accounts, list projects, list jobs, list runs. Every call is receipted in the evidence trail.
What does the dbt Cloud integration need?
You provide API token, account ID from your dbt Cloud account; Quox sends it as an API key sent as a header. 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 dbt Cloud 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 dbt Cloud connector?
This connector was blind shape-proven against the real dbt Cloud 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.