Routing and PDP
The extra routing fields use the same names as other routers, so migrating only needs a new base URL.
| Field | Meaning |
|---|---|
| models | Fallback list, max 5, tried in order. |
| provider.order | Provider slugs tried first. |
| provider.only / provider.ignore | Allow or exclude providers. |
| provider.allow_fallbacks | false: only the first endpoint of each model. |
| provider.sort | price | throughput | latency |
| provider.require_parameters | Skip providers that don't support every parameter. |
| provider.data_collection | deny: only providers that neither train on nor retain prompts. |
| provider.zdr | Zero-data-retention endpoints only. |
| provider.max_price | USD per 1M tokens: { prompt, completion }. |
| provider.region | Data-region allow-list, e.g. "id". |
Model suffixes
| Field | Meaning |
|---|---|
| :free | Zero-priced endpoints only. |
| :floor | = provider.sort: price |
| :nitro | = provider.sort: throughput |
PDP mode
PDP mode is set on the account or per key (off, pdp, id_only), not per request. The effective mode is the stricter of key and account. A request can only tighten it (provider.region, data_collection: deny), never loosen it. If no provider qualifies: 404 no_eligible_endpoint. This is a routing-policy match, not a legal compliance certification.