Stripe's acquisition of OpenRouter is officially closed. On November 10, Stripe announced on X that OpenRouter, the AI model-routing platform, is now officially part of Stripe, and that the two companies will work together to help businesses explore new business models and optimize token routing and usage. The deal was agreed on August 19 and closed almost three months later; the official price has still not been disclosed. Bloomberg reported in August that it was worth more than $7 billion, the New York Times put it at $7.5 billion, and Reuters and the Financial Times put it at around $8 billion.
OpenRouter does not train models — it acts as the switchboard between them: developers call more than 400 models through a single API, and the platform routes each request across more than 80 providers based on task complexity, price, speed and reliability, with fallbacks, cost tracking and enterprise controls. In its August announcement, Stripe said the platform processes more than 10 trillion tokens a day and serves over 10 million developers and businesses, with customers including Nvidia, Zoom and Lovable. After the acquisition, OpenRouter keeps its name, its product and its roadmap, and has reaffirmed its neutrality commitment — essential for a service whose whole point is connecting multiple model providers at once.
What Stripe is buying is the new ledger of the AI era. Inference usage is becoming a major recurring expense for companies, and OpenRouter sits between model calls and billing: whoever controls routing controls how token spending is allocated — and the data that comes with it. For a payments company, moving into this layer extends the business from helping companies collect money to helping them spend it — providing the metering, optimization and settlement infrastructure for AI usage. It is also Stripe's largest acquisition to date, marking its shift from a payments company toward the economic infrastructure of AI.
Three things to watch next:
- Whether Stripe connects OpenRouter's usage data with its own billing and risk systems, and whether routing prices and fees change.
- Whether other model gateways are forced to pick a side, and how much room is left for independent routing platforms.
- For developers, nothing changes in the short term: the same API, the same models, the same roadmap. Routing choices are worth real money on their own — a recent test showing MCP burning 42 times the tokens of CLI on the same task already shows that picking the wrong way to call a model can multiply the bill by dozens of times.
