Data & AI · wired today
What can agents actually do with DeepSeek?
Models and datasets are infrastructure now, and agents need eyes on them. The DeepSeek connector is one of 222 executable connectors and gives agents 2 tools, with the credential held in the vault and every call receipted.
The DeepSeek tool list, exactly as agents see it
list_models— List the DeepSeek Coder and Chat models available to this API keychat_completion— Send a chat completion to a DeepSeek-hosted model. This spends the account's token usage, so it is HITL-gated and never fired by the shape-proof harness (write:true means blind proof always SKIPs it; a real credential would also need --include-writes)
What the DeepSeek connector needs
You provide API key from your DeepSeek 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: DeepSeek's own API documentation ↗ covers creating and scoping the credential.
How proven is this?
DeepSeek answers every unauthenticated request identically, so its endpoint paths rest on DeepSeek's own published API reference (cited in the connector spec). The credential wire format was verified against the real host. Like every factory connector, it is Beta: it has not yet been run with a real credential.
- Credentialed The vault stores, tests and just-in-time resolves its credential; agents never see the secret.
- Approvable Its write tools execute only after a human approves them in the inbox.
- 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.
DeepSeek integration FAQ
What can Quox agents do with DeepSeek?
Agents can run 2 tools against DeepSeek: list models, chat completion. Every call is receipted in the evidence trail.
What does the DeepSeek integration need?
You provide API key from your DeepSeek 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 DeepSeek 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 DeepSeek connector?
DeepSeek answers every unauthenticated request identically, so its endpoint paths rest on DeepSeek's own published API reference (cited in the connector spec). The credential wire format was verified against the real host. Like every factory connector, it is Beta: it has not yet been run with a real credential.