TLDRocket
Sign in

Forget the model wars, Stripe and Ramp just started the router wars

The New Stack Matthew Burns Covered by 4 sources

Stripe bought OpenRouter and Ramp launched its own router, almost at the same time. Now the fight is about which layer picks the model and cuts the bill, not which model wins.

Based on reporting by The New Stack, Matthew Burns — read the original for the full story.

Summary, retelling and take written by AI under human oversight; images are AI-generated illustrations. How we work · Report an error

Model choice is turning into a runtime decision, and Stripe and Ramp just made that painfully clear. On Wednesday, 70 minutes apart, Stripe bought OpenRouter while Ramp rolled out its own internal router. One bought the layer. The other built it.

That matters because model selection used to be buried in code, often no more than a config setting. Swap the model and you had work to do. A router changes that. It picks the model on the fly, request by request, instead of forcing developers to hard-code every choice.

OpenRouter already sits in a serious spot. It serves more than 400 models from over 80 providers and processes more than 10 trillion tokens a day. Andrej Karpathy has called it the transfer switch for AI. Ramp’s version is smaller, but it says it can cut costs by about 40% for the same output. The business case is obvious enough: the model name in your code is starting to look like a liability.

Stripe and Ramp are coming at the same problem from different ends. Stripe is pushing from the developer side, the same place it built its payments empire by hiding messy local payment methods behind one API. Ramp is leaning on finance, telling customers it already handles quadrillions of tokens a month and pitching itself as the place to monitor and control the AI bill across every provider. Stripe’s own investor letter says the next problem is the “intelligence pipeline,” not just the revenue one.

But neutrality is the real prize, and also the obvious tension. OpenRouter’s CEO says developers need a neutral layer to manage model providers, and Stripe’s backers are making the same case. The catch is that both companies still have reasons to steer traffic their way. And that’s exactly why routing is becoming such a big deal: whoever owns the decision layer gets to shape not just spend, but behavior.

My take — AI-written commentary, not fact-checked reporting

This is the kind of infrastructure fight that usually gets dressed up as “choice,” then quietly turns into control. The router is the new choke point, and companies pretending they only want to save money are kidding themselves. In AI, the boring middle layer is often where the power ends up hiding, which is very convenient for everyone selling it.

Read more about this at: The New Stack

Related stories

The daily briefing

Every AI story that matters, in your inbox by 8am.

TLDRocket reads all relevant sources, removes duplicate coverage, and summarises the day in two minutes. Follow companies and topics for alerts, or get the briefing in Slack. Free, no spam, unsubscribe anytime.