What does Stripe buying OpenRouter mean for developers?
Nothing yet: Stripe announced on August 19, 2026 that it agreed to acquire OpenRouter, and OpenRouter's own post that day said its name, product, roadmap and integrations stay as they are. Neither company has announced that the deal closed, and OpenRouter's fees are the same as before.
What was announced
| Who | What they said | Source |
|---|---|---|
| Stripe | It agreed to acquire OpenRouter "to help businesses optimise token routing and usage", next to its existing Token Billing product. No price or terms | Stripe newsroom |
| OpenRouter | "Same mission, same name, same product, same roadmap." The deal is "subject to customary closing conditions" and was expected to close "in the coming weeks" | OpenRouter blog |
What changes, and what doesn't (yet)
| Topic | Status | Source |
|---|---|---|
| Your integration | Unchanged. OpenRouter: "If you build on OpenRouter today, nothing about your integration changes" | Post |
| Fees | 5.5% on credit purchases on Standard, 8% on Business; your own keys free up to $25,000 a month of list-price inference, then 5% | Pricing |
| Routing | OpenRouter says routing "will remain driven by one thing: what's best for you, the user" | Post |
| Ownership | Pending. No closing announcement from either company when we checked | Newsroom |
Still unannounced: the price, any fee change after closing, how request data is handled under Stripe, and whether OpenRouter will tie into Stripe's billing products.
If you're reconsidering
| Option | Pick it when | How you pay |
|---|---|---|
| Standard Compute | Your coding agents need a fixed monthly bill. The router picks a model per request from the lineup you choose | $19 to $249 a month, each plan with a published compute budget; at 100%, new requests get HTTP 402 |
| Requesty | You want pay-as-you-go like OpenRouter, with a monthly cap on each key | List price plus 5% per top-up; 0% on your own keys |
| LiteLLM | You want to run the gateway yourself on your own provider keys | Open source; you pay the providers and the servers |
The catch
Neither company has said what happens to fees or data handling after closing. If you stay, keep each agent's config to one base URL and one key, so switching later takes minutes.
Where Standard Compute fits
Standard Compute speaks the APIs your agents already use with OpenRouter: Chat Completions at https://api.stdcmpt.com/v1, Anthropic Messages for Claude Code and Responses for Codex. You pay a flat monthly plan from $19 with the compute included, and the router sends routine steps to cheaper models.
FAQ
How much did Stripe pay for OpenRouter?
Neither company disclosed a price or deal terms.
Has the Stripe and OpenRouter deal closed?
Not publicly. OpenRouter expected it to close "in the coming weeks" after August 19, 2026; neither company had posted a closing announcement when we checked.
Is it safe to keep using OpenRouter?
The deal hasn't changed the service so far. Review OpenRouter's privacy policy and provider data settings as you would have before, and look again if either changes after closing.
Can I move from OpenRouter to Standard Compute without code changes?
Yes. Set the base URL to https://api.stdcmpt.com/v1, swap the key, and set the model to standardcompute. For Claude Code, set ANTHROPIC_BASE_URL to https://api.stdcmpt.com; Codex uses the same key through /v1/responses.