Operational transparency
Trust the route you can inspect.
Read Zoryntel policies for named upstream routes, model substitution, token and cache visibility, data handling and reliability claims.
Named upstream route
Every enabled public model page states the intended provider and model ID. We do not silently redirect a named model to a cheaper model.
Request-level usage
Input, output and eligible cache-hit token quantities are shown separately where the upstream reports them.
Content-handling boundary
Requests must pass through the gateway and selected upstream. Operational logging and retention behavior remain under ongoing production review; no stronger no-retention claim is made.
No invented reliability claims
The service does not yet have a mature public incident history. We publish measured status once sufficient production evidence exists.
Data path
What passes through the service
Your request is authenticated, routed to the selected upstream, measured for usage and returned to your client. Operational metadata may be retained for billing, abuse prevention and incident diagnosis. See the privacy policy for the current terms.