OpenRouter
OpenRouter · Model API · US · openrouter.ai
services/openrouter.yamlVendor data-handling terms
“On your account settings page, you can set whether you would like to allow routing to providers that may train on your data (according to their own policies). / If you opt out of training in your account settings, OpenRouter will not route to providers that train.”
“Each AI provider on OpenRouter has its own data handling policies for logging and retention. / Providers also have their own data retention policies, often for compliance reasons.”
“For enterprise customers, OpenRouter supports in-region routing in the EU and US.”
Domains and endpoints
observed means seen in Unseen deployments; vendor-documented means listed by the vendor. Vendors do not publish complete lists.
| Host | Role | Source |
|---|---|---|
| openrouter.ai | app | observed |
Assessment
Reasoning: A routing layer over many model providers. Its own terms are transparent; the exposure is whichever provider a request lands on, and the account settings decide that. A developer key with defaults may reach providers that train; with the opt-out and in-region routing it is one of the more controllable ways to reach many models. The key itself is the thing to govern.
Flags: Provider-dependent training and retention · Application credentials (who holds the key) · Assessed 2026-09-16. The assessment is Unseen's; the terms above are the vendor's.
Changelog
- 2026-09-16Documented. Routing, retention, and region terms verified against the OpenRouter provider-logging documentation.
- 2026-09-15Listed from the Unseen catalogue with observed domains.
Corrections
Pull request on GitHub, or the form below. Changes are reviewed and recorded in the changelog.