AI model routing platform OpenRouter has raised $113 million in Series B funding, with Alphabet's growth fund CapitalG leading the round. The deal values the company at about $1.3 billion post-money, up from an estimated $547 million after its Series A a year ago, according to figures cited in the source.
Valuation rose sharply as token volume accelerated
The source, citing The New York Times, said OpenRouter closed a $40 million Series A last year led by a16z, with Menlo Ventures and Sequoia participating. PitchBook estimated the company's valuation at that stage at $547 million. One year later, the new round puts the company at more than 2.4x that level.
Its usage growth has moved just as quickly. OpenRouter is now processing 100 trillion tokens per month, or roughly 25 trillion per week. Six months ago, weekly throughput stood at only 5 trillion tokens. That implies a 5x increase in weekly processing volume over half a year.
The bet is on the routing layer, not one winning model
OpenRouter's product is positioned as a unified AI gateway, a single access point for APIs across many models. The source frames CapitalG's move as a bet that no one can say with confidence which model will dominate five years from now, while demand for a common access layer is already visible.
That view is tied to how AI products are being used. The source says workflows are shifting from simple question-and-answer interactions toward agents that can run tasks with less manual prompting. Those systems often need to call multiple models and switch between them in real time. A routing layer becomes useful in that setup.
Low switching costs may matter more than model count
OpenRouter's website says, “The multi-model future is already here.” The business logic behind that line is straightforward: different use cases need different models. A model that performs well on code may not be the best fit for long-form summarization, and the cheapest inference option today may be replaced by a lower-cost rival tomorrow.
In that environment, OpenRouter's edge is not only the number of models it aggregates. The source points to switching costs. Developers that integrate through OpenRouter can change the underlying model without rewriting code, adjusting routing settings instead from a control panel. If model choices keep shifting, the layer that handles access and switching could become the more durable part of the stack.