tt-routing 0.1.0

Rule-based routing engine — evaluates per-org routes in priority order to select target model/provider.

Coverage
77.42%
48 out of 62 items documented0 out of 29 items with examples
Size
Source code size: 132.59 kB This is the summed size of all the files inside the crates.io package for this release.
Documentation size: 1.63 MB This is the summed size of all files generated by rustdoc for all configured targets
Ø build duration
this release: 17s Average build duration of successful builds.
all releases: 17s Average build duration of successful builds in releases after 2024-10-23.
Links
TokenTrimmer/tokentrimmer
1 0 2
crates.io
Dependencies
Versions
- 0.1.0 (2026-06-10)
Owners

Routing engine — match incoming requests against per-org rules to pick a target model (or pass through unchanged).

Mirrors the shape used by tt-plan-core's replay-time matcher so a Plan projection and the live Gateway agree on which route would fire for a given request. Differences from plan-core:

Input is the canonical [ChatCompletionRequest] + [RequestContext] (live runtime), not a historical RequestLog.
Token-count conditions use input_tokens estimated from the request (caller supplies; the engine never tokenizes itself — that's a hot-path responsibility owned by the caller's tokenizer cache).

Rules are stored sorted descending by priority. First match wins.