Skip to content

Build Not yet confirmed elsewhere1 publisher 3 min read Published

Experiential Labs bets its open-source router's traces will train cheaper replacements for rented models

The router picks a cheaper model for work that resembles work it has already seen, and falls back to the strongest one when nothing matches. The same traces that enable that call are the proposed training set.

The Engineer · Build desk

How we use AI Send a correction

Illustration accompanying Experiential Labs bets its open-source router's traces will train cheaper replacements for rented models
Generated illustration

What happened

  • Kion Fallah and Silen Naihin open-sourced a model router in July that reads an AI agent's production history to decide which model should handle each new request.
  • Their company, Experiential Labs of San Francisco, is in Y Combinator's Summer 2026 batch and sits between an agent and its models behind one OpenAI-compatible endpoint covering hosted, local and custom models.
  • Self-run results put the router 66.5% cheaper on RouterBench with performance down 1.7%, 44.5% cheaper on TauBench with performance up 6.3%, and 64% cheaper on Terminal Bench 2.
  • The repository bundles gateway and optimization workflow, builds routers from OpenTelemetry traces, and carried more than 380 GitHub stars when the supplied research was compiled.

Why it matters

  • constraint Because anything without a close neighbour in the trace history stays on the strongest known model, achievable savings are bounded by how repetitive a given agent's traffic is, and diverse workloads keep paying frontier prices on the tail.
  • exposure The asset and the liability are the same pile: to get a trainable corpus you must retain full production traces, prompts and tool output included, in the path of a component you did not write.
  • decision Anyone comparing gateways now has to price trace retention and weight ownership alongside the per-token spread, which can favour a slower router that leaves you with usable data.
  • contradiction The guaranteed floor and the vendor's own TauBench number disagree, so the saving a buyer can actually enforce lives in the contract rather than in the benchmark table.

The load-bearing part is the K-nearest-neighbour fit over embedded requests [6]. Such a fit answers one question, which is which model previously handled work that looked like this. The value of the answer scales with how much of your traffic has a close neighbour in your own trace history. An agent hitting the same six tools all day has dense coverage. An agent taking tasks from users has whatever its tail looks like, and the tail is where the expensive errors live.

Which is why the confidence gates are the part I would point at in review. When the evidence is weak, or a request looks unlike the router's training examples, it stays on the strongest known model [8]. That is the correct default, and it fixes the failure mode: unfamiliar traffic costs full price rather than producing bad output. Read the savings figures accordingly, as a measurement of how repetitive the traffic being routed was.

Upstream of the router sits the piece that is harder to verify. World Model Optimizer ingests traces and constructs text simulations of the tools and environments an agent encounters, then runs candidate models against those simulated tasks [5]. A cheaper model is therefore promoted on evidence gathered against a reconstruction of your API rather than your API. Anywhere the reconstruction is more forgiving than production, the routing table inherits the error. Fallah led development of a mixed-reality simulator at Waabi for testing autonomous vehicles [9], so simulator fidelity is a problem this team has already met under harsher conditions.

Experiential Labs says plainly that the published numbers are configurations it chose and ran itself [14]. Their spread is the interesting bit. RouterBench came in 66.5% cheaper for a 1.7% performance drop [1], which leaves 33.5% of baseline spend, about a third [18]. TauBench came in 44.5% cheaper with performance 6.3% higher [12]. Terminal Bench 2 came in 64% cheaper [13]. Elsewhere the company advertises up to 97% lower cost on some tasks [21], which sits 30.5 points beyond its own best published benchmark [20], and a guaranteed 50% saving at equal or better quality [21] that its own TauBench figure misses by 5.5 points [19]. The guarantee reads as commercial terms rather than a result.

For any of those figures to move to your workload you would need a comparable candidate model set, a comparable task mix, and comparable prompt cache hit rates, since the router prices caching into its estimate of what a request effectively costs [7]. Change the cache economics and the cheap option changes with them.

The adoption cost is legible. You run the gateway locally, connect provider keys, and build the router from OpenTelemetry traces [11], which means instrumenting the agent and retaining traces in a form the optimizer can read. That retained corpus is the actual bet, not the routing table. Experiential Labs says customers will own the weights its training workflow produces [16], and a commenter on the launch thread asked for precisely the artefact that would test it: a model trained with the method, shown against its base [15]. Until that exists, this is a cost control with an option attached, and the option is denominated in traces you have to start keeping before you know what they are worth.

What to watch

  • An independent run of RouterBench, TauBench or Terminal Bench 2 by anyone other than Experiential Labs.
  • Whether the repository's licence and export path let a customer walk away with both the trace corpus and the trained weights.
  • Any published customer count or revenue figure, neither of which Experiential Labs has released.

Clarity's read

What the record supports and how the coverage leans. The claims behind it follow.

Reality

Evidence34
Adoption17
Hype gap+41
Incentives74
Confidence52
Why these scores

Claim ledger

Ranked by verification strength, evidence, and original report placement.

  1. [1]

    On RouterBench, Experiential Labs reported the router cut cost by 66.5% while performance fell 1.7%.

    Reported Supported Source: Experiential Labs self-run result2 sources— create a free account to open themView cited source
  2. [2]

    Kion Fallah and Silen Naihin open-sourced a model router in July that uses an AI agent's production history to decide which model should handle each new request.

    Reported Supported Source: runtimewire.com, citing a July Hacker News postView cited source
  3. [3]

    Experiential Labs is a San Francisco company in Y Combinator's Summer 2026 batch; it sits between an agent and the models it calls, offering one OpenAI-compatible endpoint for hosted providers, customer-owned API keys, local models and custom models.

    Reported SupportedView cited source

Sources

1 independent publisher whose own reporting we read for this story.

  1. runtimewire.com

    1 article · August 27, 2026

    Experiential Labs open-sources a router that learns from agent traffic

Share your take

Let Clarity write the post for you.

Signed-in readers get a short post drafted on this story in the register they choose — narrative, analytical, or a direct position — editable to the last word before it goes anywhere. The share buttons at the top of this story work without an account.

Topics and entities

Follow any of these and your For You feed starts watching them — no settings page required.

Loading related stories