Repository navigation
Add PSAI Auto Router v2 submission - #255
Open
lalitkumarps wants to merge 1 commit into
Open
lalitkumarps wants to merge 1 commit into
lalitkumarps wants to merge 1 commit into
Conversation
Author
|
/evaluate |
Router Evaluation ResultsRouter: RouterArena Metrics
Optimality Metrics
Evaluation completed by RouterArena automated workflow |
Author
|
@yl231 Can you review this and if accepted get this on 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 v2 submission
Router Display Name: SapientAI Auto Router v2
Router ID (Config / Predictions):
PSAI-Auto-Router-v2Organisation: Publicis Sapient — proprietary, closed-source
Author: Lalit Kumar (@lalitkumarps)
Split evaluated:
full(8,400 queries) +robustness(420 queries)Summary
SapientAI Auto Router v2 (
PSAI-Auto-Router-v2) is the second generation of Publicis Sapient's production LLM router. Like v1, it is a proprietary, privately hosted service: routing decisions are produced by an internal endpoint, so classifier weights, the routing index, and serving code are not included in this repository. This pull request submits router configuration and prediction artefacts for evaluation and inclusion on the official RouterArena leaderboard.All fourteen candidate models in our routing pool are already registered in
model_cost/model_cost.jsonand mapped inuniversal_model_names.py, so this PR modifies no core harness files and is strictly limited to its three submission files.Results
Methodology
1. Three-head prompt classifier
v2 replaces v1's single scalar complexity score with a multi-head non-autoregressive prompt classifier (a ModernBERT-large encoder with a custom classification head) fine-tuned on internal telemetry to predict three attributes per prompt in a single forward pass:
easy/medium/hardThe three predictions form a composite routing key
tier|task|domain. Prompts exceeding 4,000 characters are truncated (head + tail preservation) prior to classification to maintain strict routing latency bounds.2. Prior-telemetry routing index
Each
tier|task|domainkey maps to a ranked list of candidate models in a static routing index. Candidate rankings are pre-computed strictly from internal production evaluation logs and offline calibration benchmarks (measuring empirical accuracy and realised token cost per slice), prioritizing the lowest-cost deployment among models within an equivalent quality band.When a specific slice has insufficient prior support, lookup backs off hierarchically (
tier|task|domain→tier|task→tier→*) until a statistically validated routing entry is resolved.3. Serving pool
Fourteen models are registered in
router_inference/config/PSAI-Auto-Router-v2.json. Across the 8,400fullsplit queries, the router dispatched traffic across six active models:prediction)gemini-3-flash-previewgpt-4o-minigemini-3.8-flashgoogle/gemini-3.1-flash-liteqwen/qwen3-next-80b-a3b-instructgemini-3.1-pro-previewReproducibility & Evaluation
Because the routing endpoint resides on private infrastructure, the CI workflow evaluates the pre-computed prediction artefacts directly:
prediction): Every row in bothPSAI-Auto-Router-v2.json(8,400 queries) andPSAI-Auto-Router-v2-robustness.json(420 perturbed queries) reflects a live, uncached routing decision produced by the v2 classifier endpoint.generated_result): In accordance with RouterArena's response-reuse protocol, whenever v2 selected a(query, model)pair that already had a verified completion incached_results/or committed baseline predictions (including our v1 submission), that existing completion and token usage were reused (8,038 rows). The remaining 362(query, model)pairs not covered by existing cache artefacts were executed live against the respective model endpoints. All 420 rows in the robustness split also include populatedgenerated_resultpayloads (417 live, 3 cached) for full schema consistency.All metrics in the table above were produced by running RouterArena's local evaluation pipeline (
compute_scores.py) using the repository's native dataset verifiers andmodel_cost/model_cost.jsonpricing.Compliance
sub_10,full, orrobustness) were used during training, threshold tuning, or index construction.Files Added
router_inference/config/PSAI-Auto-Router-v2.jsonrouter_inference/predictions/PSAI-Auto-Router-v2.jsonrouter_inference/predictions/PSAI-Auto-Router-v2-robustness.json