The August 17 acquisition report now has official confirmation of an agreement. The companies’ announcements do not establish a completed closing or an official purchase price.
What changed after the original report
Stripe's August 19 announcement confirms an agreement to acquire OpenRouter, a gateway spanning more than 400 models and 80 providers. It describes combining model-routing decisions with the economics of token usage. The release does not disclose the price.
OpenRouter's own announcement explicitly says the transaction remains subject to closing conditions, with closing expected in the following weeks. It also says existing integrations, product, name and roadmap remain unchanged. Those are the company's stated commitments, not evidence that all future commercial terms are fixed forever.
The older price in this article's URL is retained to preserve the address; it is not an official price confirmation. We have corrected the earlier assertion that the deal was already closed.
Routing and billing solve different problems
A router selects where a request is executed. A billing system records usage and turns agreed pricing rules into charges. Putting these capabilities under one parent does not make the lowest token rate the best route for every task.
Consider two invented providers. Provider A costs $0.01 per attempt and passes eight of ten fixed tasks; B costs $0.015 and passes all ten. Across those ten attempts, A costs $0.10 for eight acceptable results, or $0.0125 each; B costs $0.15 for ten, or $0.015 each. A is cheaper per accepted result in this example, but it still leaves two tasks unresolved. A deadline or strict completion requirement may change which route is appropriate. These are illustrative numbers, not provider benchmarks or current prices.
Check the contract your application depends on
An acquisition announcement alone is not a reason to redirect production traffic. Preserve an explicit list of requirements: allowed providers, region, data handling, tool calls, response streaming, model identity and spending limits.
If changing a routing configuration, replay representative fixtures in a test environment. Verify that tool-call identifiers survive the adapter, interrupted streams are handled, usage is recorded and retries do not trigger duplicate downstream actions. Log the actual model and provider so quality changes can be investigated.
The useful question is whether the route meets the application's quality, cost and reliability requirements while preserving these controls. A neutral-routing pledge helps describe product intent; observable behaviour and the applicable service terms determine what an individual deployment can rely on.
Update August 17 report with official August 19 acquisition agreement and OpenRouter closing conditions; price remains unconfirmed, integrations unchanged according to company, add routing/billing explanation.