Check a route and locate the request
Connect an application to the corporate gateway and inspect its route.
Before you start
Use an application key, an available model and a harmless short question.
Click path
- Find the intended model in Модели.
- Open Playground (
/playground). Use Маршрут for routing decisions or Чат for a complete model response. - Enter a harmless question and the available model identifier.
- Run the selected check; inspect the policy action, provider, model and perimeter.
- After a full request, open История запросов (
/history) and find the request by time or request ID. - Open Routing Audit to inspect why that route was selected.
2026-10-15 · Actual staging application. Synthetic client, public definitions or aggregate test-stand metrics only; not customer statistics or a benchmark. Original pixels are unmodified; personal profile and private data excluded. Dry-run checks route selection and does not call the LLM.
- Route
- Chat
- Harmless
- Code
- Confidential
- Restricted
- Model for route dry-run
- Route
Verify and recover
A Route result is a decision; a Chat result includes inference. Check the perimeter explicitly. Provider failure requires a health check; policy denial requires checking the organization’s permissions. Respect client rate limits for 429.