Live decision
2.7ms
Pi → role-model → Kimi K3
Application
Sends a classified request
Domain
Engineering
Role
coder
Task
implement
Scope
repo
Router · role-model
Ranks eligible endpoints · balanced
Kimi K3
0.841 · Winner
GPT 5.6 Sol
0.808 · Rank 2
DeepSeek V4 Flash
0.792 · Rank 3
Gemini 3.6
0.776 · Rank 4
Opus 5
Excluded
Model
Selected from the pool · serves answer
Latency
18.2s
Tokens
31k
Cost
$0.08
Status
Success
When the top pick fails
Scored fallbacks stay on the decision
If the winner is cold, excluded, or over budget, the next eligible member is already listed on the same RouterDecision — continuity without guessing at request time.
01 · Applications
Requestors
Chat, agents, and tools emit normalized intent — domain, role, task, and scope.
02 · Router
Capability-aware pick
Narrow by role and task, score measured quality, emit winner + fallbacks.
03 · Model endpoints
Answerers
Candidates compete on eligibility and evidence. Only the winner serves.
How the router decides
Normalize → narrow → eligibility → score → emit — deterministic enough to inspect later.
Normalize
Build effective intent and policy from the request.
Narrow
Keep endpoints that match role, task, and scope.
Eligibility
Reject capability, modality, tool, locality, and budget failures.
Score
Measured evidence first, then declared, then defaults.
Emit
Return winner, fallbacks, exclusions, and reasons.
Hard eligibility
Reject endpoints that fail the request before scoring begins.
Capability
Capability & modality
Tools
Tool classes
Locality
Local preference gates
Budget
Cost and token bounds
Binding
Binding requirements
Score with evidence first
Compare quality, latency, throughput, cost, and reliability in order.
1st
Measured evidence
From benchmarks and Observe
2nd
Declared capability
And preference data
3rd
Neutral defaults
When evidence is thin
What the path emits
The Live route ends in a RouterDecision — winner, fallbacks, exclusions, and reasons you can read.
RouterDecision{ "chosen": "kimi-k3", "strategy": "balanced", "fallbacks": ["gpt-5.6-sol", "opus-5"], "reason": "highest measured quality for role-coder" }
Selection signals
domain · Engineering
role · coder
task · implement
scope · repo
winner · Kimi K3