Data & AI · wired today
Drive Google Gemini with governed agents
Models and datasets are infrastructure now, and agents need eyes on them. The Google Gemini connector is one of 222 executable connectors and gives agents 2 tools, with the credential held in the vault and every call receipted.
What agents can run against Google Gemini
| Tool | What it does |
|---|---|
list_models | List the Gemini models available to this API key, with their display name, supported generation methods and token limits |
generate_content | Generate content from a Gemini 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) (write) |
What the Google Gemini connector needs
You provide API key from your Google Gemini 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: Google Gemini's own API documentation ↗ covers creating and scoping the credential.
How proven is this?
This connector was blind shape-proven against the real Google Gemini 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.
- 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.
Google Gemini integration FAQ
What can Quox agents do with Google Gemini?
Agents can run 2 tools against Google Gemini: list models, generate content. Every call is receipted in the evidence trail.
What does the Google Gemini integration need?
You provide API key from your Google Gemini 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 Google Gemini 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 Google Gemini connector?
This connector was blind shape-proven against the real Google Gemini 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.