Skip to content
🚀 EDDI 6.5.0

19 LLM providers, knowledge bases that crawl your site and read your files, and conversations that follow compatible agent versionsWhat's new

Managed Cloud Get Started
All models
GoogleFrontier

Gemini 3.1 Pro

Google's current Pro model, in preview on the Gemini API, tuned for complex reasoning, software engineering and precise multi-step tool use.

Strengths

  • Text, image, video, audio and PDF input
  • Efficient thinking
  • Reliable multi-step tool execution
  • 1M-token context

Best For

  • Complex problem-solving
  • Agentic coding
  • Multimodal understanding

Run It in EDDI

The fastest route is the Manager: open the agent wizard or the Platform Operator and pick the provider and model. To configure it yourself, follow these steps for the provider you want.

Google Gemini API · type: "gemini"

Model ids: gemini-3.1-pro-preview, gemini-3.1-pro-preview-customtools

1. Store the credential

Add the provider's API key to the Secrets Vault in the Manager, or with PUT /secretstore/secrets/default/gemini-key, under the name used below. Configurations reference it as ${vault:…}, so the key never appears in plain text.

${vault:gemini-key}

2. Configure the LLM task

Use this as the langchain.json of the agent's workflow, or paste the parameters into the LLM editor in the Manager.

{
  "tasks": [
    {
      "actions": [
        "send_message"
      ],
      "id": "chat",
      "type": "gemini",
      "parameters": {
        "apiKey": "${vault:gemini-key}",
        "modelName": "gemini-3.1-pro-preview",
        "maxOutputTokens": "8192",
        "systemMessage": "You are a helpful assistant",
        "addToOutput": "true"
      }
    }
  ]
}

Or create the whole agent in one call

setup_agent writes the rules, LLM configuration and workflow, then deploys the agent. Call it over MCP or POST /administration/agents/setup.

setup_agent(
  agentName: "My gemini-3.1-pro-preview agent",
  systemPrompt: "You are a helpful assistant.",
  provider: "gemini",
  model: "gemini-3.1-pro-preview",
  apiKey: "${vault:gemini-key}"
)

Notes for EDDI

  • Gemini 3 needs its thought signature echoed back during tool calls. EDDI does this by default (returnThinking and sendThinking are on for the gemini type); leave them on.
  • For Gemini 3 with tools use type: gemini, not gemini-vertex: the Vertex path cannot carry the thought signature. gemini-vertex is fine without tools.

Related Models

Sources

The facts on this page come from the vendor's documentation, checked on 2026-09-30. Models change quickly, so confirm limits with the vendor before you rely on them. Prices are not listed here: see the vendor's pricing page.

Vendor documentation ↗ · Pricing ↗