OpenRouter announced on its official blog that it is joining Stripe. The announcement carries no price tag, only a note that the deal is subject to customary closing conditions and is expected to close within a few weeks. The price comes from outside reporting: Bloomberg put the figure at more than $7 billion, and Axios followed up saying the deal is cash and stock worth more than $8 billion.
The same post laid out the company's scale: it forwards more than 10 trillion tokens a day, connects to more than 400 models, serves more than 10 million developers and companies, has grown its business volume at least tenfold a year, and runs on a team of about 90 people.
Its last public funding round was a $113 million Series B led by Google, at a post-money valuation of $1.3 billion. At a $7 billion sale price, that works out to a 5.4x markup.
What justifies $7 billion for 90 people
Start with a rough calculation from the public numbers. At 10 trillion tokens forwarded per day, using a blended rate of roughly $0.50 per million tokens as a rough midpoint — somewhere between cheap open-weight models and flagship closed ones — daily throughput comes to about $5 million, or roughly $1.8 billion annualized. OpenRouter's model is to take a cut of that flow; its public rate is around 5%, putting annualized revenue in the ballpark of $90 million.
$7 billion is more than 70 times that revenue figure. The buyer clearly isn't paying for current profit — it's paying for the position itself.
What makes that position distinctive is that it holds two things at once: model selection and metering. Developers hand their requests to OpenRouter, which decides which provider gets the call, at what price tier, and who it falls back to after a timeout; every single forwarded request also has to be billed, settled and invoiced. The first decision determines where the money goes; the second determines how it's counted.
Why a payments company wants a router
Stripe's core business is payment infrastructure, which at its foundation is metering and settlement. AI calls have reshaped what that looks like: unit prices as small as a thousandth of a cent, frequency running into the trillions per day, and the payer is a piece of software rather than a person at a checkout page.
Seen from that angle, model routing and a payment gateway have a strikingly similar structure — both make real-time choices among multiple backends and then record every single transaction precisely. Stripe has spent the past two years pushing agent-side payment protocols and account infrastructure; folding in a middle layer that already chooses models on developers' behalf effectively merges the entry point with settlement in one move.
OpenRouter's announcement made three promises: the brand and mission stay the same; existing integrations don't need to change; and routing decisions will still be based on just one thing — "what's best for you."
The first two are easy to keep. The third is where the real variable in this deal sits. A neutral router's value rests entirely on not favoring any particular model provider. Once it belongs to a payments company, providers have to start asking a new question: could my model's ranking in this channel end up tied to settlement terms?
The middle layer starts getting absorbed
Over the past year, price competition at the model layer has squeezed margins thin, pushing value toward both ends of the stack — the providers holding the compute and the weights on one side, and the entry points holding the users and the billing on the other. Routing, gateways and observability tooling in between have often been dismissed as a thin layer of glue. This deal's price tag suggests the buyer sees it very differently.
For developers, there's essentially no change in the near term: integrations stay the same, billing stays the same. In the medium term, two things are worth watching — how much transparency there is around routing weightings, and whether the bar for onboarding new providers goes up. Neither of those will show up in a press release; they'll only become visible months later, in pricing sheets and latency curves.
There's also a practical consideration for teams based in mainland China. OpenRouter has been a default channel for many teams calling overseas models, and once ownership changes, compliance review, the settlement entity and data flow will all need to be revisited. Teams relying on it would do well to line up a backup channel ahead of time.
Sources: OpenRouter's official announcement, Bloomberg, CocoLoop, Axios, Fortune. The official announcement was used to verify daily forwarding volume, model count and team size; the acquisition amount is cited from Bloomberg and Axios in parallel, and the valuation multiple is calculated against the $1.3 billion Series B mark.