Cohere API and Dome
Cohere Command behind one Gateway, with every call governed.
Dome talks to Cohere through its OpenAI compatibility API, so Command and Embed sit behind the same Gateway as every other model. Mark the connections legal approved, and work done for legal stays on them.
How Dome helps
Dome provides model brokering and routing for Cohere
Cohere's key stays with Dome
No agent is handed the Cohere key. Each one authenticates with a Dome key of its own.
Approved connections for legal work
Tag the connections your legal team approved. A rule refuses every other connection when an agent acts for someone in legal.
Chat and embeddings
Command models answer chat completions and Embed models answer embeddings. Both run through the same Gateway.
Get started
Connect Cohere in three steps
Add Command and Embed connections, pool Command for a fallback, and repoint agents.
01
Add the connections
The provider id is cohere. Dome uses Cohere's compatibility endpoint, https://api.cohere.ai/compatibility/v1, and Cohere's own model ids.
$ dome models add command-a-plus-cohere \--provider cohere \--model command-a-plus-05-2026 \--api-key "$COHERE_API_KEY" \--attributes '{"approved_for":"legal"}' \--gateway prod-gateway$ dome models add command-a-cohere \--provider cohere \--model command-a-03-2025 \--api-key "$COHERE_API_KEY" \--attributes '{"approved_for":"legal"}' \--gateway prod-gateway02
Pool them
Command A Plus answers first and Command A second. The pool's name is what agents send.
$ dome models pool create command-a-plus \--failover-max all --gateway prod-gateway$ dome models pool member add command-a-plus command-a-plus-cohere --priority 0$ dome models pool member add command-a-plus command-a-cohere --priority 103
Point your agent at the Gateway
Change the base URL to the Gateway and the key to the agent's own. OpenAI-compatible SDKs need nothing else.
from openai import OpenAIclient = OpenAI(base_url=f"{GATEWAY_URL}/v1", api_key=DOME_AGENT_KEY)client.chat.completions.create(model="command-a-plus",messages=[{"role": "user", "content": "List the indemnity clauses in this contract."}],)
Commands and rules tested against a Dome workspace on October 1, 2026. For anything about Cohere itself, see Cohere's documentation.
Rules
Legal work stays on approved connections
When the person an agent acts for is in legal, only connections tagged approved_for: legal are allowed. Their group comes from the identity token the agent passes on.
forbid (principal, action == Dome::Action::"llm:invoke", resource is Dome::LLMModel)when { principal has act_as && principal.act_as.groups.contains("legal")}unless { resource has approved_for && resource.approved_for == "legal" };Try it
One call, two outcomes
Switch the caller or the argument and watch the same call decide differently. Every decision lands in audit.
Connection
- Agentcontract-reviewer is registered and active
- Callere.walsh verified, groups: legal
- RuleConnection is tagged approved_for: legal
Agent workflow
Bringing it together
Connecting Cohere to registered agents, tools, and identity in Dome completes a governed agent application.
Acting for
Control point
Gateway
- Rules
- Guards
- Quotas
Every call decided and audited
Models
Provider
Cohere
This page
Provider
OpenAI
See how
FAQ
Common questions
How does Dome connect to Cohere?
Through the compatibility API at https://api.cohere.ai/compatibility/v1. Dome attaches the Cohere key as a bearer header.
Which model ids go on a Cohere connection?
The ones the compatibility API accepts, such as command-a-plus-05-2026 or embed-v5.0-pro.
Do Cohere embeddings work through Dome?
Yes. Cohere connections serve chat completions and embeddings.
Does Dome call Cohere's native Chat API?
No. Dome speaks Cohere's OpenAI compatibility API, the same request shape as every other OpenAI-compatible provider.
Explore
More of what Dome works with
Model
Claude Fable
Fable 5.1 from Anthropic and Amazon Bedrock in one failover pool, open to one group and capped by quota.
Read moreMCP server
GitHub
The GitHub MCP server behind the Tool Gateway, with rules that decide each call on its owner and repository.
Read moreIdentity
Okta
Okta tokens verified on every agent call, so rules and audit name the person each agent acted for.
Read moreRuntime
OpenAI Agents SDK
OpenAI Agents SDK agents with their models on the Model Broker and their MCP tools on the Tool Gateway.
Read moreClient
Claude Code
Claude Code on a Dome Gateway with per-developer sign-in, rules on every tool call, and audit by name.
Read moreAgent service
TinyFish
TinyFish's web agents behind the Tool Gateway, with rules that decide each run on the site it targets.
Read moreNext steps
Talk with our FDE team
Our forward deployed engineers work with your platform team to get your agents into production and under control: the first one governed on your own systems, and a pattern your teams can repeat for every agent after it.
No card required to start. Register your first agent in minutes.
LLM providers for AI agents: one governed path to every model
Connect a provider once. Its key stays in Dome, and every agent call to it is authorized, metered and audited.
See them all