Skip to main content
This page lists routing strategies, failover limits, resolution order, and the match_when predicate dialect. Refer to Pools concept for how routing works. Configure on Pools.

​
Routing strategies

strategy_scope: workspace shares round-robin and least-loaded state across agents; caller tracks per agent. Priority-weighted routing ignores strategy_scope.

​
Failover

Authorization and streaming failover rules are on Pools.

​
Pool resolution

Dome resolves a request’s model value in this order:
  1. A pool with that exact name
  2. A direct model connection with that exact name
  3. A direct connection whose upstream model identifier matches
  4. The first pool in the configured order whose match_when predicate matches
  5. The workspace default pool
Exact names beat conditional routes. match_when inputs: By default every condition must match. Use any, all, or not to combine differently. An unknown condition, missing value, or unverified act-as attribute never matches. Routing does not replace authorization.

​
Next steps

Create pools and attach them to Gateways:
  • Pools concept for members, routing, and reachability
  • Pools to create pools, manage members, and attach Gateways
  • Models reference for provider and credential catalogs
  • LLM gateway concept for dispatch on the wire