Skip to main content
Integrations · Gemini
Guild agents call Google’s Gemini models through task.llm, with no API key in agent code. Guild holds the credential server-side, checks your model policies on every call, and attributes spend to the workspace, agent, and user that made it.

Book a demo

See how teams govern agents that use Gemini.

Start free

Connect Gemini and scope your first agent.

Gemini’s schema rules, handled for you

Gemini accepts a narrower JSON Schema than other publishers. Guild rewrites tool and structured-output schemas to fit before it sends them. Guild also requests Gemini’s thoughts, so the session can show reasoning progress.

How it works

1

Add a credential

In Access & setup > Models & providers, click Add API key and choose a provider that serves Gemini models. Check Gemini under Models. On a managed account, you can skip this while Guild holds a managed Gemini key.
2

Write a model policy

Bind the credential’s Gemini access to the account, a workspace, or an agent, and list the models it may call, such as gemini-*-flash.
3

Call it from task.llm

Name "gemini" in llmPreferences, or leave preferences out and let your policies choose. Guild resolves the credential at runtime.

Every Gemini call goes through your policies

Agents never hold the key. Guild stores the credential server-side and shows only a masked value, so you can rotate it without touching agent code or the model policies bound to it. Policies are an allowlist: a workspace, agent, or installed agent can call a Gemini model only if a rule allows it. Set a daily token limit to cap spend, and see each call by workspace, agent, and user in Usage. A raw API key in an agent’s environment reaches every model the key can. A policy reaches only the models you name.

About Gemini models on Guild

Inference providers

You can reach these models through the Google AI API itself or through a third-party provider. Write the canonical model name, such as gemini-3.5-flash, everywhere in Guild. Guild maps it to each provider’s own model ID.

Models

Guild prices and recognizes these Gemini model IDs. A policy or preference can also name any other model your credential can reach. Third-party providers route more models than this list, and their catalogs change; see each provider’s page for what it serves.

Set up Gemini

On a managed account, agents can use Gemini models without a credential, as long as Guild holds a managed key for Gemini. To use your own Gemini account instead, add a credential. Adding your first credential switches the whole account to bring your own key (BYOK).
1

Open Models & providers

Click Access & setup in the left nav, then Models & providers. In an organization, only admins can open it.
2

Add a credential

Click Add API key and choose an inference provider from the table above.
3

Enter the provider's secret

Give the credential a Name and paste your provider’s API key. AWS Bedrock asks for an IAM role and region instead.
4

Choose Gemini

Under Models, check Gemini. Keep gemini-3.5-flash as its default model or enter another from the list above. Then click Add Key.
To control which workspaces and agents can use Gemini models, add a model policy for the credential. For example, --models "gemini-*-flash" limits a policy to matching models:

Use it from an agent

Agent code never names a credential. Guild resolves the call against the workspace owner’s settings. To ask for Gemini explicitly, put it in llmPreferences:
The first entry asks for gemini-3.1-pro-preview. The second falls back to the default model of the matching policy. Preferences are strict: if no credential or policy allows any of them, the call fails rather than using another publisher. See LLM preferences.

Notes

  • Guild requests Gemini’s thoughts, so the session can show reasoning progress.
  • Gemini accepts a narrower JSON Schema than other publishers. Guild rewrites tool and structured-output schemas to fit before it sends them.
  • In traces, Gemini calls carry the provider name gcp.gemini, following the OpenTelemetry GenAI conventions.

Frequently asked questions

Yes, on a managed account, when Guild holds a managed key for Gemini. Usage then draws from your Guild tokens balance. Adding any credential switches the whole account to bring your own key (BYOK).
No. Gemini models aren’t on either. Reach them through the Google AI API or OpenRouter.
Yes. Add a model policy for the agent with --models "gemini-*-flash". Policies are an allowlist, so the agent can call only matching models.
With the provider name gcp.gemini, following the OpenTelemetry GenAI conventions.

Put a governed agent on Gemini this week

Book a demo

See how teams govern agents that use Gemini.

Start free

Connect Gemini and scope your first agent.
Also runs on Guild: Anthropic · OpenAI · OpenRouter Read: Docs: Models & providers · LLMs · Usage
Last modified on October 20, 2026