I read that Stripe is reportedly paying north of $7 billion for OpenRouter and my first thought wasn’t about payments infrastructure or whether that number is sane. It was: right, that’s the company a huge share of AI tools have been quietly handing my text to.

OpenRouter is a gateway. You give it one API key, it speaks to Anthropic and OpenAI and Google and DeepSeek on your behalf, and you get unified billing plus a nice model-picker dropdown. Enormously useful piece of plumbing. Also a hop, and a hop is a company, and a company can be bought.

Count the hops

Take a normal AI tool that lets you “choose your model.” You type something into its interface. That text goes to the tool’s backend, because the tool needs to attach a system prompt and its own API credentials. The backend calls a gateway. The gateway calls the provider. Four parties touched your words before a model ever saw them, and you only ever agreed to the privacy policy of one.

Now take a browser extension holding your own key in local storage. You type. The extension makes an HTTPS request straight to api.anthropic.com or wherever you pointed it. One hop. Your key never leaves the machine, there is no vendor backend in the middle to log anything, and the only privacy policy that governs the exchange is the one you picked when you created the key.

That’s the whole architectural difference, and it survives an acquisition unchanged.

Nobody sends you an email when the path changes

Here’s what I find genuinely uncomfortable about gateway acquisitions, and it isn’t a privacy-policy question so much as a nobody-noticed question: the tool you use doesn’t change, its version number doesn’t change, its UI doesn’t change, and the API contract it’s calling doesn’t change either, so the day the ownership of that middle hop transfers, absolutely nothing on your screen tells you that your prompts now flow through a different corporate entity with different retention defaults and a different appetite for what to do with the logs.

Stripe is a serious company with real compliance obligations. I’m not predicting they’ll do something gross with inference logs. But the acquisition is the proof of the mechanism, not the harm. Twelve months ago the answer to “who sees this” was a Y Combinator startup in San Francisco. Today it’s a payments giant. Nobody asked you.

And the failure mode doesn’t have to be an acquisition. LiteLLM got popped last year, which we wrote about at the time, and the lesson was the same: the proxy is a target precisely because so much passes through it.

Repricing is the boring version

Gateways get repriced. Free tiers get retired. Routing rules change and suddenly your “auto” model is a cheaper one. This is normal business, not villainy, and it still lands on you.

Your key and your login are the same bet

The part I keep coming back to is that key-in-the-browser and logged-in-tab-in-the-browser are one idea wearing two hats.

When Dassi runs in a side panel, it reads the page you already have open. No OAuth grant to Gmail, no service account for your CRM, no scraper credentialed as some third party. The authentication already happened, in your browser, when you logged in this morning. The agent borrows the session that’s sitting right there instead of asking a server somewhere to impersonate you.

Bringing your own key is the same trick applied one layer down. The credential lives where you are. The request goes out from where you are. Nothing in between needs to be trusted, because nothing in between exists. You can point Dassi at Claude, GPT, Gemini, DeepSeek, or Kimi, and if a provider changes terms on a Tuesday you switch on Tuesday afternoon by pasting a different key. Or you skip keys entirely and log in with a ChatGPT subscription you already pay for. Either way the data path is short and you can describe it in one sentence.

There’s a longer argument for this in why AI companies don’t trust each other with data, which came out of watching these firms write contracts against each other while telling users not to worry.

Dassi is free and lives in the Chrome Web Store, if you want to see the difference rather than take my word for the routing diagram.

Anthropic’s CEO called the current backlash a crisis of trust, which feels about right, though I think trust is the wrong frame for something you can just remove from the equation. You don’t have to trust a middleman you never introduced into your setup. Stripe will probably run OpenRouter competently for years. I’d just rather my prompts weren’t part of anyone’s $7 billion asset.