Stripe posted on X yesterday that OpenRouter is now officially part of Stripe. The deal is closed.
I use OpenRouter. A lot of you do too. It's the one API endpoint that lets you call 400-plus models from dozens of providers without wiring up a new integration every time a better model ships. So the question isn't whether the acquisition is big — reported at roughly $7.5 billion, it's Stripe's biggest ever — it's what happens to the router now that a payments company owns it.
Here's what we know, what's actually changing, and what I'd be watching if my stack routes through OpenRouter.
What happened
Stripe and OpenRouter agreed the deal on August 19, 2026. Yesterday, November 10, Stripe confirmed on X that the acquisition has closed and OpenRouter is officially part of Stripe.
The price was never confirmed by either company. The New York Times reported around $7.5 billion; Bloomberg reported over $7 billion; Reuters and the FT reported roughly $8 billion in cash and stock. Take the exact number with a grain of salt — the reports disagree, and neither company has put a figure on it. What isn't in dispute is the scale: this is Stripe's largest acquisition by a wide margin.
For context on how fast OpenRouter grew into that price tag: founded in 2023 by Alex Atallah and Louis Vichy, it raised a $113 million Series B at a $1.3 billion valuation in May 2026, led by CapitalG. By November 2, OpenRouter said its annualized run rate had passed 10 quadrillion tokens — up 6x from 1.5 quadrillion in May. More than 10 million developers and businesses use it, and OpenRouter takes roughly a 5% cut of the spend that flows through it.
What Stripe says changes — and what doesn't
The official line, from both companies: same name, same product, same roadmap, same mission. Routing decisions stay driven by what's best for the user, not by which provider pays more. Stripe already processed OpenRouter's payments before the deal, so the billing relationship isn't new — it's just deeper now.
Stripe's stated focus is on optimizing token routing and usage, usage-based billing, and agentic commerce. Patrick Collison put it this way: "Stripe is building the economic infrastructure for AI, and together with OpenRouter we'll help businesses maximize profitability by routing their requests intelligently and spending their tokens efficiently."
That framing is worth reading twice. Stripe isn't describing OpenRouter as a model company. It's describing it as economic infrastructure — a place where tokens get spent efficiently. That's a payments company's way of looking at inference: a meter running, and a bill at the end of it.
The honest question: neutrality
Here's the part I keep coming back to. OpenRouter's entire value is neutrality. You trust it because it has no reason to prefer one provider's model over another — it takes its cut either way, and its job is to send your request to the best model for the job at the best price.
That neutrality is now owned by a company with very specific commercial interests. Stripe doesn't build models, so there's no obvious provider to favor. That's genuinely reassuring. But Stripe does build billing infrastructure, and it does have partnerships — and the incentives of a payments company are to grow the volume flowing through the pipe and to make billing for that volume as sticky as possible.
None of that has happened yet. I'm not claiming it will. But the whole reason developers route through OpenRouter instead of going direct to each provider is trust in the routing layer. That trust was built when OpenRouter was an independent company whose only product was the router. Now the router has a parent with a much bigger agenda, and the neutrality promise is something Stripe has to keep proving, not something you can take for granted.
Why the timing matters: agents burn tokens
There's a number in OpenRouter's November 2 announcement that explains why Stripe paid this much: AI agents now burn roughly 7x more tokens than humans. Inference is becoming the biggest line item on a software company's bill, and it's growing fast.
That's the real story here. Stripe didn't buy a model router. It bought a front-row seat to the fastest-growing metered spend in software — and the company that decides which model that spend goes to. Usage-based billing for AI agents is a product Stripe clearly wants to own, and OpenRouter is the routing layer it sits on top of.
What to watch
If you route through OpenRouter, here's what I'd actually keep an eye on over the next few months:
Pricing and the take rate. OpenRouter takes around 5% today. Watch whether that moves, and whether Stripe bundles routing with its billing products in ways that make leaving harder.
Provider neutrality in practice. The promise is that routing stays user-driven. The test is whether a provider ever gets quietly deprioritized or a Stripe-partnered model gets a nudge. Watch the routing decisions, not the press releases.
Usage-based billing features. This is where Stripe will almost certainly build. Expect new billing tooling for agent workloads — and read the terms on who owns the usage data.
The roadmap. "Same roadmap" is easy to say on day one. The first time a feature ships that serves Stripe's billing business more than it serves developers, you'll know the answer.
What I'd actually do
I'm not migrating off OpenRouter. Nothing has changed in the product today, the team is staying, and the routing still works the way it did last week. Panic-migrating off a tool because of an acquisition announcement is how you burn a weekend for nothing.
What I am doing: keeping my provider fallback paths warm. If you route everything through OpenRouter with no direct provider keys as backup, that's a single point of failure you chose, not one Stripe imposed. A couple of direct API keys — OpenAI, Anthropic, Google — sitting in your secrets manager cost you nothing until the day you need them. And if you care about neutrality, keep an eye on the routing decisions in your own logs. The data will tell you before any announcement does.
The deal is done. The router works the same today as it did yesterday. The question is whether it still works the same way a year from now — and that's a question only Stripe's actions can answer.
Are you routing through OpenRouter? Does a payments company owning your router change how you think about it — or is it just a bigger balance sheet behind the same API?
