Relace
Try Relace on us. Starter credit covers your first requests, then one key reaches all 2 Relace models, with the privacy posture shown on every route.
Relacerelace
These privacy labels describe Relace, the upstream model provider. Confidential requires all three: verified provider compute, end-to-end encryption and explicit zero data retention. Account and billing metadata are outside the content-retention claim.
| Provider | Relace |
|---|---|
| API operator country | Not verified Legal home of the API operator, not an inference-location guarantee. |
| Headquarters | Not verified |
| 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 |
Inference locations
Provider API declarations are also available on each model's endpoint API. Direct chat and Responses replies separate advertised availability from serving location in usage.inference_location; the actual serving region remains unknown when not reported.
usage.provider_usage.gateway_region identifies the TrustedRouter gateway, not the provider's inference location. A value such as europe-west4 does not mean the model ran in Europe. usage.inference_location.serving_region remains null when the provider has not reported it. Older gateways may return the gateway-only field as provider_usage.region.
Where the upstream GPUs execute the model, not the provider's headquarters, API ingress, or data storage. ZDR and confidential inference do not by themselves restrict geography.
- Declared countries or regions
- Not verified
No inference-location declaration has been verified for this provider. - Can locations change?
- Not verified. Do not assume that the serving location is fixed.
- Provider region pinning
- Not verified.
- Pinning through TrustedRouter
- No verified provider-specific location pin documented here.
- Infrastructure declaration
- Inference location not verified; no country-specific residency commitment.
- Evidence
- Not yet reviewed.
Provider selection alone is not a region pin. TrustedRouter's US provider filter selects company jurisdiction, not GPU location. A regional gateway hostname does not pin a downstream GPU. For a binding residency requirement, confirm the model, region, failover scope and enforced controls before sending sensitive data.
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.07385/1M | $0.01477/1M | $0.1477/1M |
moonshotai/kimi-k3MoonshotAI: Kimi K3 |
IQ 127#21 | 1,048,576 | $2.11/1M | $0.3165/1M | $14.77/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.