Mistral and Dome
Run Mistral Large 3 from Mistral and NVIDIA under one name. Mistral Large 3 has open weights, so Mistral's API is not the only place to run it. Pool it with NVIDIA NIM, and agents ask for mistral-large-3. A rule keeps work for EU staff on connections tagged eu.
Dome provides model brokeringand routing for Mistral.
Mistral first, NVIDIA next
Mistral serves Large 3 as mistral-large-2512, and NVIDIA NIM serves the same open weights. When Mistral fails, the call goes to NVIDIA.
EU work on EU connections
Tag each connection with a region. When the person behind a call is in the EU group, a rule refuses anything not tagged eu.
Spend per person
Cap what one person's agents spend on models at $50 a month. It counts every agent that acts for them.
Mistral with failoverin five steps.
Tag Mistral and NVIDIA by region, pool them, add the EU rule, then cap spend per person.
Connect Mistral
The provider id is mistral. The region attribute is your label, and rules read it.
shelldome models add mistral-api \ --provider mistral \ --model mistral-large-2512 \ --api-key "$MISTRAL_API_KEY" \ --attributes '{"family":"mistral","region":"eu"}' \ --gateway prod-gatewayConnect NVIDIA NIM
The same open weights, under NVIDIA's model id.
shelldome models add mistral-nvidia \ --provider nvidia \ --model mistralai/mistral-large-3-675b-instruct-2512 \ --api-key "$NVIDIA_API_KEY" \ --attributes '{"family":"mistral","region":"us"}' \ --gateway prod-gatewayPool them for failover
Mistral's API leads and NVIDIA follows, while agents only ever send mistral-large-3.
shelldome models pool create mistral-large-3 \ --failover-max all --gateway prod-gateway dome models pool member add mistral-large-3 mistral-api --priority 0dome models pool member add mistral-large-3 mistral-nvidia --priority 1Point your agent at the Gateway
Mistral's API speaks the OpenAI format, so the agent's OpenAI client works once it points at the Gateway.
pythonfrom openai import OpenAI client = OpenAI(base_url=f"{GATEWAY_URL}/v1", api_key=DOME_AGENT_KEY)client.chat.completions.create( model="mistral-large-3", messages=[{"role": "user", "content": "Draft a reply to this leave request."}],)Cap spend per person
An act-as quota follows the verified person, across every agent that acts for them.
shelldome quotas set --subject act-as --act-as l.moreau \ --dimension llm --unit provider_usd --limit 50 --window monthly
EU workstays on EU connections.
Applied to an agent with --agent, this refuses any connection not tagged region: eu when the person the agent acts for is in the eu group. Everyone else can use either connection.
cedar
forbid (principal, action == Dome::Action::"llm:invoke", resource is Dome::LLMModel)when { principal has act_as && principal.act_as.groups.contains("eu") }unless { resource has region && resource.region == "eu" };One call,two outcomes.
Switch the caller or the argument and watch the same call decide differently, with every decision landing in audit.
Connection
agent hr-assistant · acting as l.moreau
llm:invoke(model: "mistral-api")
- Agenthr-assistant is registered and active
- Callerl.moreau verified, groups: eu
- RuleConnection is tagged region: eu
- Quota$21 of $50 this month
DecisionAllowed
Bringing it alltogether.
Connecting Mistral to registered agents, tools, and identity in Dome completes a governed agent application.
Acting for
Control point
GatewayEvery call decided and audited
RulesGuardsQuotas
Models
Common questionsabout Mistral.
More of whatDome works with.
Provider
Anthropic
The Claude API behind the Model Broker: the key held in Dome, every call authorized, metered and audited.
MCP server
GitHub
The GitHub MCP server behind the Tool Gateway, with rules that decide each call on its owner and repository.
Identity
Okta
Okta tokens verified on every agent call, so rules and audit name the person each agent acted for.
Runtime
LangGraph
LangGraph agents with their model calls on the Model Broker and their MCP tools on the Tool Gateway.
Client
Claude Code
Claude Code on a Dome Gateway with per-developer sign-in, rules on every tool call, and audit by name.
Agent service
TinyFish
TinyFish's web agents behind the Tool Gateway, with rules that decide each run on the site it targets.
Talk with ourFDE team.
Or start free, and register your first agent in minutes. Connect it through a gateway, give it rules, and see every call it makes in one audit trail.
Talk with our FDE team
Our engineers design, build and run governed agents for the part of your business you want to change. You see what they deliver.
AI models for enterprise agents: failover, rules and quotas
Every model your agents call goes through the Model Broker. Pool providers for failover, decide who may call each model, and cap what it costs.