Data & AI · wired today
Drive Exa with governed agents
Models and datasets are infrastructure now, and agents need eyes on them. The Exa connector is one of 222 executable connectors and gives agents 3 read-only tools, with the credential held in the vault and every call receipted.
What agents can run against Exa
| Tool | What it does |
|---|---|
search | Run a neural web search and return ranked results with title, url, publish date and a relevance score. A non-mutating POST, so write:false; this is also the spec's auth-proving test call |
get_contents | Fetch the cleaned full text of specific URLs (get the URLs from search results). A non-mutating POST, write:false |
find_similar | Find pages similar to a given URL, ranked by relevance. 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 Exa connector needs
You provide API key from your Exa 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: Exa's own API documentation ↗ covers creating and scoping the credential.
How proven is this?
This connector was blind shape-proven against the real Exa 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.
Exa integration FAQ
What can Quox agents do with Exa?
Agents can run 3 read-only tools against Exa: search, get contents, find similar. Every call is receipted in the evidence trail.
What does the Exa integration need?
You provide API key from your Exa 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 Exa 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 Exa connector?
This connector was blind shape-proven against the real Exa 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.