TAKSHA ROUTER · SHIPPING IN THE TAKSHA LINEUP

The router that shows its receipts.

Send a request to taksha-auto and it is classified, routed to the model that measures best on that kind of work, and answered with a receipt — every routing decision cites the graded runs behind it. The routing table is public. Nothing about the choice is a black box.

Talk to us about the router Explore Sovereign Coding

HOW IT ROUTES

Classified, measured, routed, receipted.

Classify

Every request to taksha-auto is classified into a task class — the same classes our graded battery measures, so the router speaks the same language as the evidence.

Route on measurement

The request goes to the model that measures best on that class. The routing table is generated from execution-graded battery ledgers — results earned by running the output, never by asking a model to grade itself, and never hand-written.

Apply the protocol

Where a class has a specialist protocol — the discipline that made the specialist pass its gate — the router applies it automatically. You get the specialist's method, not just its name.

Answer with a receipt

The response carries an x-taksha-router-receipt header: which class, which model, and the measured results the decision rests on. Auditable per request, not per press release.

THE ROUTING TABLE IS PUBLIC

Read the table before you send a token.

The full routing table is served at /v1/router/table. Every cell carries its pass rate — pass over n — and the ledger files it was computed from, so any developer, auditor, or regulator can trace a routing decision back to the graded runs that justify it. When the battery is re-run, the table is regenerated from the new ledgers; nobody edits it by hand.

GET /v1/router/table
→ 200 · public · pass/n + ledger files in every cell

POST /v1/chat/completions  (model: taksha-auto)
→ x-taksha-router-receipt:
    class:  <task class>
    model:  <routed tier>
    basis:  pass/n on this class
    ledger: <battery ledger files>
    mode:   auto | cost | quality

Generated, never hand-written

The table is compiled from execution-graded battery ledgers. If the measurements change, the routing changes — there is no marketing override.

Every cell shows its denominator

Each class-model cell carries pass/n and names its ledger files. A number without a denominator and a source is not a measurement.

A receipt on every response

The x-taksha-router-receipt header rides on each response, citing the class, the chosen model, and the measured basis for the choice.

Availability-aware

The router tracks which tiers are actually serving and routes around what is down, instead of failing your request on principle.

THREE MODES · ONE EVIDENCE BASE

Pick the trade-off. The ledgers stay in charge.

Auto

Default

The measured default.

Routes each request to the model that measures best on its task class, availability-aware. This is the mode the receipts were built for.

Cost

Lighter where the ledgers allow.

Prefers the lighter tier on classes where the graded runs say it holds up, and escalates where they say it does not. The trade-off is governed by measurements, not vibes.

Quality

The strongest measured option.

Always routes to the strongest-measuring model for the class — for the work where you want maximum capability and the receipt to prove you got it.

Stop trusting the picker. Audit it.

The Taksha Router is shipping in the Taksha lineup. Bring your workload and we will walk you through the routing table, the ledgers behind it, and the receipt on every response.

Talk to us about the router Explore the Sovereign Coding platform