Riverflow
Explore Riverflow models on TrustedRouter with current routes, token pricing, policy sources, privacy posture, regional availability, and API support.
Riverflowriverflow
No provider claim
These privacy labels describe Riverflow, the upstream model provider. ZDR is a retention policy; verified confidential inference additionally requires attested provider compute and end-to-end encryption.
| Provider | Riverflow |
|---|---|
| Routing status | Not routable |
| Provider website | https://www.riverflow.ai/ |
| Models | 0 public models |
| Credits routes | 0 |
| Zero data retention | not claimed |
| Verified confidential inference | Not verified |
| Policy note | Riverflow is a variable-credit media workflow API, not a shared token-priced chat endpoint. Its configured credential is rejected by the live MCP endpoint, and no exact per-job billable receipt is exposed. It remains fail-closed until both contracts are available. Policy source |
Models served by Riverflow.
Each row links to pricing, provider, benchmark, and API pages for the model.
| Model | AI IQ | Context | Input | Cached input | Output |
|---|
Questions
Does Riverflow have zero data retention?
TrustedRouter does not currently mark Riverflow 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 Riverflow end-to-end encrypted?
TrustedRouter does not currently mark Riverflow 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 Riverflow models are available through TrustedRouter?
This page currently lists 0 public Riverflow models, with live pricing, route count, context length, measured performance when available, and links to each model's provider and benchmark pages.