Data & AI · wired today
Drive Turso with governed agents
Models and datasets are infrastructure now, and agents need eyes on them. The Turso 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 Turso
| Tool | What it does |
|---|---|
list_organizations | List the Turso organizations this API token can see (slug, account type, plan and blocked-read/write status). Run this first: every other Turso tool needs an organization slug |
list_databases | List the databases in one Turso organization (name, UUID, libSQL hostname, group, primary region, blocked-read/write and delete-protection status), optionally filtered to one group |
get_database | Get one Turso database by name (UUID, libSQL hostname, group, primary and replica regions, blocked-read/write and delete-protection status) |
list_groups | List the database groups in one Turso organization (name, UUID, primary location, replica locations, libSQL server version, delete-protection status) |
Every tool above is read-only. Write surfaces ship only after live testing, and always behind approval gates.
What the Turso connector needs
You provide API token from your Turso 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: Turso's own API documentation ↗ covers creating and scoping the credential.
How proven is this?
This connector was blind shape-proven against the real Turso 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.
Turso integration FAQ
What can Quox agents do with Turso?
Agents can run 4 read-only tools against Turso: list organizations, list databases, get database, list groups. Every call is receipted in the evidence trail.
What does the Turso integration need?
You provide API token from your Turso 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 Turso 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 Turso connector?
This connector was blind shape-proven against the real Turso 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.