Stripe is buying OpenRouter, the switchboard for 400 AI models
Bloomberg reports a deal above $7 billion for the gateway 8 million developers use to reach more than 400 models with one API.
One API, 400 plus models, 8 million users, a $7 billion price. The neutral AI router just got an owner.
Stripe has agreed to buy OpenRouter for more than $7 billion, Bloomberg reported on August 16. OpenRouter is the traffic switch a lot of AI products quietly stand on: one API key, one bill, and a router that forwards each request to any of more than 400 models from dozens of providers.
What Stripe is actually buying
OpenRouter gives about 8 million users a single gateway across models from OpenAI, Anthropic, Google, DeepSeek, and smaller labs. Teams use it to compare prices per million tokens, to fail over when one provider has an outage, and to swap models without rewriting integration code. TechCrunch notes the company raised a $113 million Series B in May at a $1.3 billion valuation. The reported price is more than five times that number, three months later.
Stripe already runs billing for a large share of AI startups, and metered AI usage is one of the fastest growing things it invoices. Owning the router puts the company that bills AI usage inside the request path that generates the usage. Stratechery's read is that Stripe is trying to aggregate model demand the way it aggregated payment rails.
The neutrality question
OpenRouter's value came from not caring which model you picked. A router owned by a payments company keeps that neutrality on paper, but the incentive map changes: Stripe now earns on the billing, the routing, and potentially the spread between them. Model vendors that compete with Stripe's partners will read the new terms closely. And the deal itself was reported, not closed: antitrust review of AI infrastructure acquisitions has been slow this year.
Why a build studio cares
We pick models per project: one client's chat feature wants a cheap fast model, another's document pipeline wants a long-context one. Gateways like OpenRouter are how small teams do that without maintaining five SDKs. If your product routes through OpenRouter today, nothing breaks tomorrow. The next contract renewal is the moment to check pricing, data retention terms, and whether a direct provider integration is worth the extra code.
Next step: list which of your AI features route through a gateway, and write down the one-day migration path to a direct API for each. You want that list before terms change, not after. Questions about model routing in a build? Write to hello@gattyworks.com.