Add PSAI Auto Router submission - #207
Open
subhajeet-sapient wants to merge 1 commit into
Open
subhajeet-sapient wants to merge 1 commit into
subhajeet-sapient wants to merge 1 commit into
Conversation
Router: PSAI-Auto-Router (Publicis Sapient, proprietary) Splits: full (8,400 queries + 3,236 optimality entries), robustness (420) Arena Score 75.49 Accuracy 77.99% Cost $3.65 total, $0.434 per 1K queries Robustness 73.33 Routing is driven by a DeBERTa-v3-base complexity classifier over a five-model pool spanning roughly a 10x spread in output-token price: gpt-5-nano, google/gemini-3.1-flash-lite, gemini-3-flash-preview, deepseek/deepseek-v4-flash and Qwen/Qwen3-Coder-Next. All five already have entries in model_cost/model_cost.json and universal_model_names.py, so no shared file is modified and no router implementation is added. The classifier was trained exclusively on Publicis Sapient production data. No RouterArena query, label, or split file was used to train or fit it. Claude-Session: https://claude.ai/code/session_01PtWH2P2ax2LPvzx24t5NHH
Author
|
/evaluate |
Router Evaluation ResultsRouter: RouterArena Metrics
Optimality Metrics
Evaluation completed by RouterArena automated workflow |
Author
|
@yl231 Can we get this on the leaderboard ? |
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.
Add SapientAI Auto Router submission
Router: SapientAI Auto Router
Organisation: Publicis Sapient — proprietary, closed-source
Author: Subhajeet Dey (@subhajeet-sapient)
Split evaluated:
full(8,400 queries) +robustness(420 queries)Summary
SapientAI Auto Router is Publicis Sapient's production LLM router. It is a
proprietary, privately hosted service: the routing decision is produced by an
internal endpoint, and neither the classifier weights nor the serving code are
included in this pull request. This submission therefore contains prediction
artefacts only — we want to include this submission to the official leaderboard.
All five models in the pool already have entries in
model_cost/model_cost.jsonand
universal_model_names.py, so this PR touches nothing outside its own threefiles.
Results
Methodology
1. Complexity and Boosting classifier
The routing signal is a DeBERTa-v3-base sequence classifier fine-tuned on
Publicis Sapient's own production traffic — real customer prompts accumulated
across live engagements over an extended period, with outcome labels derived from
observed model sufficiency in production.
The classifier emits a single scalar complexity score in [0, 1] per prompt
2. Cost-versus-complexity analysis
Each candidate model is profiled offline on two axes: realised unit cost
(blended input/output token price at production traffic ratios) and capability
ceiling (the complexity level beyond which the model's answer quality degrades).
This produces a cost/capability frontier. Models on the frontier form an ordered
ladder of tiers; models dominated on both axes are excluded from serving. The
router's task reduces to selecting the cheapest tier whose capability ceiling
clears the query's predicted complexity.
3. Proprietary tier boosting
A pure threshold cut on the complexity score under-serves queries near a tier
boundary, where classifier uncertainty is highest and the cost of an
under-powered answer is asymmetric with the cost of a stronger model.
The tier boosting layer promotes a query above its base tier when boundary
conditions warrant it, trading a bounded cost increase for the reduction in
failure probability. Boosting is applied per-query at decision time based on
routing and token-length signals, and domain/task priors.
4. Serving pool
Five models, spanning roughly a 10× spread in output-token price:
gpt-5-nanogoogle/gemini-3.1-flash-litegemini-3-flash-previewdeepseek/deepseek-v4-flashQwen/Qwen3-Coder-NextReproducibility
The routing endpoint is private infrastructure and cannot be called by the
evaluation workflow. The submitted
generated_resultfields are the verbatimoutputs from the run described above, and the evaluation harness recomputes
accuracy and cost from them using the repository's own scorers and
model_cost.jsonprices.Compliance
The complexity classifier was trained exclusively on Publicis Sapient production
data. No RouterArena query, label, or split file was used to train or fit the
classifier.
Files
router_inference/config/PSAI-Auto-Router.jsonrouter_inference/predictions/PSAI-Auto-Router.jsonrouter_inference/predictions/PSAI-Auto-Router-robustness.json