Data & AI · wired today
What can agents actually do with Tavily?
Models and datasets are infrastructure now, and agents need eyes on them. The Tavily connector is one of 222 executable connectors and gives agents 2 read-only tools, with the credential held in the vault and every call receipted.
The Tavily tool list, exactly as agents see it
search— Run a Tavily agent-search and return ranked results with title, url, content excerpt and a relevance score, plus an optional synthesized answer. A non-mutating POST, so write:false; this is also the spec's auth-proving test callextract— Extract the raw text content of specific URLs. A non-mutating POST, write:false
Every tool above is read-only. Write surfaces ship only after live testing, and always behind approval gates.
What the Tavily connector needs
You provide API key from your Tavily 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: Tavily's own API documentation ↗ covers creating and scoping the credential.
How proven is this?
This connector was blind shape-proven against the real Tavily 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.
- Credentialed The vault stores, tests and just-in-time resolves its credential; agents never see the secret.
- Read-only It ships read tools only, so there is nothing to approval-gate.
- Agent-owned No dedicated agent owns it yet; the orchestrator can drive it on request.
- Schedulable Not yet exposed in the workflow builder; that integration is on the connector roadmap.
- Evidenced Per-call evidence envelopes are on the roadmap; vault credential use is already receipted.
Tavily integration FAQ
What can Quox agents do with Tavily?
Agents can run 2 read-only tools against Tavily: search, extract. Every call is receipted in the evidence trail.
What does the Tavily integration need?
You provide API key from your Tavily 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 Tavily 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 Tavily connector?
This connector was blind shape-proven against the real Tavily 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.