Documentation
DocumentationRule-based routing
DOCS / UWA V1 RELEASE CONTRACT SELF-HOSTED GATEWAY

Rule-based routing

Explicit eligibility and deterministic ranking across Location × Category × Capability.

ONE GATEWAYCoordinates → eligible provider → canonical responseWhy UWA
On this page 3 sections

#Decision path

Validate → resolve location → determine eligible providers per category → rank by configured deterministic rules → attempt → validate schema & coordinate drift → fall back on classified failures. Routing decisions are 100% deterministic and never use LLM/AI inference.

#Verifiable lean ranking

In the default lean_v1 profile, DecisionEngine.SetLeanRanking(true) orders eligible candidates strictly by operator-configured priority, applying a bounded health penalty only after at least 10 actual observations and honoring recovery probe bonuses—without relying on synthetic latency or cost estimates.

#Interactive explorer and overrides

The Routing Explorer uses clearly labeled local illustrative fixtures (including Bhilai, Raipur, Berlin, London and New York) to teach the routing model. In the live API, the optional provider query parameter requests a specific adapter, but remains strictly subject to policy, eligibility and quota checks.

Canonical contracts: docs/openapi.yaml (lean_v1) and docs/openapi.experimental.yaml · Verify against your build before production use.

Search local documentation. No external requests.

↑↓ to move · Enter to openESC to close