Dome Systems

Together AI API and Dome

Open models on Together AI, with every call governed.

One Together AI key reaches a long list of open models. Connect it to Dome and each agent gets the families you pick: a rule keeps a support agent on Llama, and DeepInfra answers Llama calls when Together can't.

PeopleAgentsDomeTogether AI modelsCallersPeopleAgentssupport-agentAgentssummarizerAgentsresearch-agentGatewaysprod-gatewayLlama 3.3 70Bmeta-llama/Llama-3.3-70B-Instruct-TurboKimi K3moonshotai/Kimi-K3DeepInfraLlama failover, priority 1RulesGuardsAuditsaudit-trail
support-agent→llama-3.3-70b· as m.alvarezAllowed

How Dome helps

Dome provides model brokering and routing for Together AI

New models wait for you

Dome holds the Together key and sends it as a bearer token. A model Together adds reaches no agent until you add a connection for it.

Same model, second provider

DeepInfra serves the same Llama 3.3 70B. Pool the two and a failed call on Together goes to DeepInfra.

One family per agent

Tag each connection with its model family. A rule keeps an agent on Llama, whatever else Together serves.

Get started

Connect Together AI in three steps

Add one Together model, back it with DeepInfra, then point agents at the Gateway.

  1. 01

    Add the connection

    The provider id is together. Dome uses https://api.together.xyz/v1 and Together's own model ids.

    $ dome models add llama-together \
    --provider together \
    --model meta-llama/Llama-3.3-70B-Instruct-Turbo \
    --api-key "$TOGETHER_API_KEY" \
    --attributes '{"family":"llama"}' \
    --gateway prod-gateway
  2. 02

    Pool it with DeepInfra

    Add the same model on DeepInfra as a second connection. Members are tried in priority order, and agents send the pool's name.

    $ dome models pool create llama-3.3-70b \
    --failover-max all --gateway prod-gateway
     
    $ dome models pool member add llama-3.3-70b llama-together --priority 0
    $ dome models pool member add llama-3.3-70b llama-deepinfra --priority 1
  3. 03

    Point your agent at the Gateway

    Any OpenAI-compatible client works. The agent's Dome key replaces the Together key.

    from openai import OpenAI
     
    client = OpenAI(base_url=f"{GATEWAY_URL}/v1", api_key=DOME_AGENT_KEY)
    client.chat.completions.create(
    model="llama-3.3-70b",
    messages=[{"role": "user", "content": "Draft a reply to this support ticket."}],
    )

Commands and rules tested against a Dome workspace on October 1, 2026. For anything about Together AI itself, see Together AI's documentation.

Rules

This agent uses Llama only

Applied to one agent with --agent, this refuses any connection not tagged family: llama. Kimi and DeepSeek stay one connection away, and out of reach.

forbid (principal, action == Dome::Action::"llm:invoke", resource is Dome::LLMModel)
unless { resource has family && resource.family == "llama" };

Agent workflow

Bringing it together

Connecting Together AI to registered agents, tools, and identity in Dome completes a governed agent application.

Dome

Control point

Gateway

  • Rules
  • Guards
  • Quotas

Every call decided and audited

FAQ

Common questions

How does Dome connect to Together AI?

Through Together's OpenAI-compatible API at https://api.together.xyz/v1, with your key sent as a bearer token. The key stays in Dome's vault.

Can an agent call a Together model I haven't approved?

No. Agents reach only the connections on their Gateway. A model Together lists this week stays out of reach until you run dome models add for it.

What happens when Together AI is unavailable?

The llama-3.3-70b pool sends the call to DeepInfra, which serves the same Llama 3.3 70B. The agent's request doesn't change.

Next 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.