chore(router): address the hosted router by hostname, TLS verification on

router.allaigate.com now resolves and serves a valid certificate, so the hosted routing API no longer has to be reached by bare IP with certificate verification switched off. Make https://router.allaigate.com the default [router].url with verify_tls = true. Existing configs still pointing at 138.226.222.209 (with or without a scheme or a trailing slash) are moved to the hostname on load and have verification restored, then saved: it is the same machine, and this is the difference between a verified connection and a blind one. A self-hosted router URL is left untouched. README, docs/ROUTER.md (both languages), config/gateway.example.toml and bench/accuracy.py follow. Verified live: the migration rewrites a legacy config on startup, admin health reports the hostname reachable over verified TLS (389 ms), and real requests route through it - "math"/medium 0.416 and "translation"/low 0.268 with route_source=router.
2026-08-21 13:21:24 +03:00
parent f65f131c41
commit 9c15109f26
10 changed files with 107 additions and 23 deletions
@@ -175,9 +175,9 @@ print(resp.choices[0].message.content)
 `model: "cortiq-auto"` enables routing. Any **real** model name from the config
 (`"gpt-4o-mini"`, `"local-qwen"`) is a direct passthrough, without routing.

-> **Using the hosted allaigate router?** Set `url = "https://138.226.222.209"`,
-> `verify_tls = false`, `taxonomy_id = "data-assistant"`, and a `cortiq_…` key in
-> `CORTIQ_ROUTER_KEY`. On hard prompts the router escalates to an oracle (~10 s), so
+> **Using the hosted allaigate router?** It is the default: `url =
+> "https://router.allaigate.com"` with `verify_tls = true`. Set `taxonomy_id =
+> "data-assistant"` and a `cortiq_…` key in `CORTIQ_ROUTER_KEY`. On hard prompts the router escalates to an oracle (~10 s), so
 > set `timeout_ms = 12000+` — otherwise the gateway gracefully degrades to the default model.

 ---