Meta via OpenRouter
Explore Meta via OpenRouter models on TrustedRouter with current routes, token pricing, policy sources, privacy posture, regional availability, and API support.
Meta via OpenRoutermeta
These privacy labels describe Meta via OpenRouter, the upstream model provider. ZDR is a retention policy; verified confidential inference additionally requires attested provider compute and end-to-end encryption.
| Provider | Meta via OpenRouter |
|---|---|
| Routing status | Active |
| Provider website | https://www.meta.com/ |
| Models | 0 public models |
| Credits routes | 0 |
| Zero data retention | no |
| Verified confidential inference | Not verified |
| Policy note | TrustedRouter sends requests through its attested gateway to OpenRouter, which routes them to Meta. This downstream route is not marked zero-retention, confidential-compute, or end-to-end encrypted. Policy source |
Models served by Meta via OpenRouter.
Each row links to pricing, provider, benchmark, and API pages for the model.
| Model | AI IQ | Context | Input | Cached input | Output |
|---|
Questions
Does Meta via OpenRouter have zero data retention?
TrustedRouter does not currently mark Meta via OpenRouter as provider-level zero data retention. Use trustedrouter/zdr or provider.min_privacy=zdr to select a different eligible route, and review the linked policy source for changes.
Is Meta via OpenRouter end-to-end encrypted?
TrustedRouter does not currently mark Meta via OpenRouter as end-to-end encrypted at the provider boundary. The TrustedRouter gateway is still attested, but the selected provider normally receives the request in order to run the model. Use trustedrouter/e2e for the stronger route requirement.
Which Meta via OpenRouter models are available through TrustedRouter?
This page currently lists 0 public Meta via OpenRouter models, with live pricing, route count, context length, measured performance when available, and links to each model's provider and benchmark pages.