Skip to main content

​
API Keys

  • Create unlimited keys from the dashboard.
  • Each key can have an optional list of allowed models.
  • Keys are opaque strings with no fixed prefix.
  • Revoke instantly at any time.
  • Best practice: use separate keys for different environments or tools.

​
ZDR mode (zero data retention)

Each API key has an optional ZDR mode toggle (default off). When enabled, that key’s requests are hard-restricted to the providers we classify as zero-data-retention. All other upstreams are excluded from key selection, including failover. See the Models page for the provider information behind each model. Behavior while ZDR mode is on:
  • Model availability shrinks. Models with no ZDR route (for example MiniMax M3) are hidden from GET /v1/models for that key, and calling them directly returns 403 with code model_not_available_in_zdr_mode. Models with at least one ZDR route remain available — GET /v1/models on that key lists exactly those.
  • Auto routing stays compliant. The Auto virtual model only picks candidates served by a ZDR provider.
  • BYOK is unaffected. Requests sent to your own upstream via BYOK do not pass through Openference-managed routing.
  • Toggles apply immediately (the auth cache is invalidated on save; the model list refreshes within its 60-second cache).
Trade-off — stability. ZDR mode reduces the routes available per model, so there is less failover during upstream incidents. Expect more 529 Overloaded responses on a ZDR key than on a standard key during provider outages. Note that ZDR classification is Openference’s operational classification — the actual retention commitment is each provider’s published terms for the tiers we use. See the FAQ for the full data-retention picture and each provider’s policy links. Enable it when creating a key (Advanced options) or later on the key’s detail page (Configuration → ZDR mode).