What it is
OpenRouter, a company that earns a fee on credit purchases and on large volumes routed through its own keys. Its interest is in being the layer between you and every model vendor.
Instead of separate contracts and connections with each AI vendor, a developer connects once to OpenRouter and names the model. Model prices are passed through at the vendor’s own rate; OpenRouter adds a fee on credit purchases. Routing rules travel with each request: an ordered list of preferred vendors, an allow-list or block-list, a price cap, a speed floor, and a switch that restricts requests to vendors that do not retain prompts.
The default policy avoids vendors that have just had an outage and then prefers the cheapest. Prompts are not logged by default. Companies can also use their own vendor keys through the same connection.
What marketing teams should take from it
- Access to AI models can be separated from any one provider. That is what makes the switching test in finding 02.2 possible without three vendor contracts.
- The data-handling switches matter more to marketing than the price rules. A request can be told to use only vendors that do not keep the prompt, which is the setting for customer lists and unreleased campaign material.
- Running the same brief through three models at pass-through prices is a comparison, not a decision. Your own quality bar still decides.
- It is plumbing that developers call. There is no writing tool, no company content and no approval workflow in it.
Where to start
Keep your instructions, sources and quality bar outside the provider, then run the same ten accounts through a second model before a renewal. If the second provider holds up, you have a negotiating position even if you never switch.
Before any workflow touches customer data, have your company’s AI lead set the no-retention rule and have legal confirm it. Put the cheapest-vendor rule on high-volume, low-stakes jobs such as tagging and first-pass summaries, and a named vendor on final copy.
Keep in mind
Data-handling guarantees rest on the downstream vendor’s policy, which OpenRouter reports and routes by but does not itself enforce. A CMO never touches it directly; it sits behind a tool someone builds.