Routes & Policies
How operators configure provider selection, failover, and request overrides for API keys.
Routes (routing policies) define how LatentKit executes requests for an API key. Application code sends task payloads; routes decide provider/model attempts.
What operators configure
- Ordered provider/model attempts and failover
- Capability eligibility (chat, embeddings, image, etc.)
- BYOK vs Platform Access connections
- Optional request overrides such as
response_profile - Budgets and guardrails (workspace-dependent)
What developers send
Developers send endpoint-specific bodies only — for example messages for chat or input for embeddings. Do not send:
modelproviderroutepolicy
Publishing
Draft routes can be edited in the console. Published routes are what runtime requests use. Assign a published route to each API key.
Response profiles
When enabled on a route, applications may pass:
{ "response_profile": "balanced" }Allowed values: fast, balanced, deep. If overrides are disabled, the route default applies even when a profile is sent.
Testing routes
Use AI Router in the console to verify route health, run browser test requests, and copy snippets against the selected key.
If the route test fails in the console, fix provider connection, model eligibility, credits, or route publish state before changing application code.