Repository navigation
Conversation
Author
|
/evaluate |
Router Evaluation ResultsRouter: RouterArena Metrics
Evaluation completed by RouterArena automated workflow |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Tirtha is an OpenAI-compatible gateway by Spanda Works (https://tirtha.ai). This entry is Tirtha 1.0 as served in production on 2026-11-10.
In auto mode a small model answers first; a second model gives a second opinion and a yes/no checker compares the two. The request climbs to a larger model only when the check fails. The served model is the routing choice.
Predictions. Every prompt of the full split (8,400) and the robustness split (420) was sent to the production setup and the served model recorded. Model pool:
google/gemma-4-31b-it-turbo(Base),deepseek-ai/DeepSeek-V4.1-Flash-1017(Plus, and the second opinion),Qwen/Qwen3.8-Max(Max; not reached in this setup).Prices. Our public per-level prices (https://api.tirtha.ai/v1/pricing, read 2026-11-11), not provider list prices, because they are what a customer pays. The checker (
baseten/elephant-1) is priced at its maker's list price.Router-side calls are in
router_usage. The first answer on climbed rows is measured. The second-opinion call and the checker call are estimated from measured averages (second opinion = the first answer's token counts; checker = 515 input tokens), as stated in each row'spurposefield. Together they are about 63% of the cost.Data use. This is Tirtha 1.0 as served in production on 2026-11-10. Its answer checker was chosen on 2026-11-08 by a pre-registered test on GSM8K and TriviaQA questions taken from their original public sources, not from RouterArena's files; some of those public questions may also be in RouterArena's set. Later that day we ran RouterArena's sub_10 split to compare setups, as the README suggests. A climb-to-larger-model variant that scored best there is not this submission. No part of the router was trained, fitted or tuned on RouterArena data or labels. Every model call the router makes is listed in router_usage.
Local check on main @ 18383b4:
check_config_prediction_files.py tirtha fulland... robustnessboth pass;compute_cost.py tirtha --split full= $0.3320 per 1K queries.