Stripe is reported to be closing an acquisition of OpenRouter for more than seven billion dollars, roughly ninety days after OpenRouter raised a 1.3 billion dollar Series B. The last public revenue figure for OpenRouter was about 140 million dollars annualized, which puts the deal at roughly a fifty-times multiple — high in absolute terms but unremarkable by the standards of the current top tier of AI infrastructure companies. What makes the price interesting is less the multiple than what is being bought: OpenRouter is not a model lab and owns no weights. It is a routing and metering layer that sits between applications and several hundred models from dozens of providers, normalizing APIs, arbitraging price and latency, and settling payment.
The strategic logic is straightforward once you take the routing layer seriously as a business rather than as glue code. Stripe's core asset is payment rails plus a developer-facing API surface; OpenRouter's is inference rails plus a developer-facing API surface. Both monetize per unit of activity flowing through them, both benefit from becoming the default integration point rather than the best individual product, and both get stronger as the number of upstream suppliers grows rather than consolidates. If the model market stays fragmented — many capable models at many price points, with the frontier lead measured in months rather than years — then the layer that abstracts across models captures durable margin while the labs compete away theirs. That is the bet.
Stratechery's framing is that this is an aggregation play in the classic sense: OpenRouter does not need to own supply, it needs to own the demand relationship and the switching decision, and it needs suppliers to be commoditized enough that switching is cheap. It also notes the business-model inversion, since a payments company acquiring an inference broker means the same rail can meter tokens and settle dollars in one place, which is exactly the primitive that agentic commerce needs when software agents start paying for their own API calls. The related launch of payment middleware for agent frameworks the same week — deterministic per-session budgets, signed micropayments, and traced spending — suggests the market is converging on that primitive from several directions at once.
The caveats are real. A fifty-times multiple on 140 million dollars assumes routing volume keeps compounding, which requires that developers keep wanting a neutral broker rather than contracting directly with one or two labs. Vertical integration by the labs is the obvious threat, and several already offer their own multi-model gateways. There is also a concentration risk that runs the other way: if a broker becomes the default, its ranking and default-model choices become an enormous, quiet influence on which models get used, with no obligation to disclose the economics behind those defaults.
- Stratechery reads it as an aggregation bet: own the switching decision, not the models.
- Latent Space notes the roughly fifty-times revenue multiple against $140M annualized, ninety days post-Series B.
- Hacker News discussion focused on whether the labs will simply build their own gateways and squeeze the broker.