Relace
Explore Relace models on TrustedRouter with current routes, token pricing, policy sources, privacy posture, regional availability, and API support.
Relacerelace
No provider claimThese privacy labels describe Relace, the upstream model provider. ZDR is a retention policy; verified confidential inference additionally requires attested provider compute and end-to-end encryption.
| Provider | Relace |
|---|---|
| Routing status | Active |
| Provider website | https://relace.ai/ |
| Models | 2 public models |
| Credits routes | 2 |
| Zero data retention | no |
| Verified confidential inference | Not verified |
| Policy note | Relace's public API documentation does not publish contractual zero retention, confidential compute, or end-to-end encryption for hosted open-model requests. This route is Standard. Policy source |
Measured performance
32 samplesContinuously sampled across Relace's routed models: p50 TTFT, effective throughput, and success rate. Effective throughput uses provider-reported output tokens over complete request time. Unsupported route and probe-configuration rows are separated from provider downtime. No prompt or output content stored.
| p50 TTFT | 1940 ms |
|---|---|
| Effective throughput | — |
| Uptime | 96.88% |
| Model | p50 TTFT | Effective throughput | Uptime | Config excluded | Availability samples |
|---|---|---|---|---|---|
| deepseek/deepseek-v4-flash-0731 | 1940 ms | — | 93.75% | — | 16 |
| moonshotai/kimi-k3 | 2552 ms | — | 100.00% | — | 16 |
Relace performance history · Full provider & model leaderboard.
Models served by Relace.
Each row links to pricing, provider, benchmark, and API pages for the model.
| Model | AI IQ | Context | Input | Cached input | Output |
|---|---|---|---|---|---|
deepseek/deepseek-v4-flash-0731DeepSeek: DeepSeek V4 Flash 0731 |
— | 1,048,576 | $0.068575/1M | $0.01688/1M | $0.1899/1M |
moonshotai/kimi-k3MoonshotAI: Kimi K3 |
IQ 121#27 | 1,048,576 | $3.165/1M | $0.3165/1M | $15.825/1M |
Questions
Does Relace have zero data retention?
TrustedRouter does not currently mark Relace 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 Relace end-to-end encrypted?
TrustedRouter does not currently mark Relace 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 Relace models are available through TrustedRouter?
This page currently lists 2 public Relace models, with live pricing, route count, context length, measured performance when available, and links to each model's provider and benchmark pages.