TrustedRouter

Find a model

Browse the full catalog →

OpenAI compatible API · Attested · Public status

DeepSeek API Privacy & Zero Data Retention

Run DeepSeek V4 Pro and V4 Flash through an attested OpenAI-compatible gateway. No prompt or output logging, with enforceable ZDR route filters.

Verify gateway
Onebase URL to migrate
100sof models and routes
0prompt or output logs. Always.
DeepSeek API privacy

DeepSeek V4 on attested infrastructure. With Confidential privacy, your prompts never reach the model vendor.

The worry behind "is the DeepSeek API safe" is specific. api.deepseek.com runs on the vendor's own infrastructure, several US states have restricted it on government devices, and a January 2025 incident exposed plaintext chat logs. The V4 weights themselves are MIT-licensed. The risk lives in where the endpoint runs.

TrustedRouter serves deepseek-v4-pro and deepseek-v4-flash through a hardware-attested confidential-compute gateway, and DeepSeek's own API is one of the routes. With Confidential privacy (provider.min_privacy "confidential"), prompts never reach the model vendor: a Confidential request routes only to third-party confidential-compute hosts, and fails rather than fall back to the vendor's own API. TrustedRouter never logs prompt or output content. Ordinary synchronous and streaming inference does not retain it. The opt-in Batch API temporarily retains enclave-encrypted artifacts for up to 30 days. Zero-Data-Retention routes are available, and each route's privacy tier is listed on the models page. Migration is one line: change base_url, keep your OpenAI SDK.

See DeepSeek pricing Check the attestation

Same SDK, new base_urlPython
from openai import OpenAI

client = OpenAI(
    base_url="https://api.trustedrouter.com/v1",
    api_key=TR_KEY,
)

r = client.chat.completions.create(
    model="deepseek-v4-pro",  # or deepseek-v4-flash
    messages=[{"role": "user", "content": "Summarize this contract."}],
)
Hosting

Confidential skips the vendor

Confidential requests run only on third-party confidential-compute hosts, never on DeepSeek's own API. Standard routing can include it. EU-focused routing is available through the EU gateway.

Proof

Attestation you can run

The gateway source is open and the image digest is published. One curl with a nonce returns a JWT signed by the CPU vendor's root key, bound to the live TLS session. Details at /security.

Retention

No prompt or output logs

TrustedRouter never logs prompt or output content. Ordinary synchronous and streaming inference does not retain it. The opt-in Batch API temporarily retains enclave-encrypted artifacts for up to 30 days. Zero-Data-Retention routes add contractual guarantees; TEE routes keep prompts sealed even from the hosting provider. See zero data retention.

DeepSeek zero data retention

Make downstream retention a hard routing rule.

TrustedRouter never logs prompt or output content. Ordinary synchronous and streaming inference does not retain it. The opt-in Batch API temporarily retains enclave-encrypted artifacts for up to 30 days. For ordinary real-time DeepSeek requests, set provider.min_privacy to zdr to consider only providers with a recorded zero-data-retention posture.

The filter fails closed. If no eligible DeepSeek endpoint is available, the router returns an error instead of silently sending the request to a weaker privacy tier.

Require ZDRJSON
{
  "model": "deepseek/deepseek-v4-flash",
  "provider": {"min_privacy": "zdr"},
  "messages": [
    {"role": "user", "content": "Summarize this contract."}
  ]
}
api.deepseek.comTrustedRouter
Model accessDeepSeek V4, first-partydeepseek-v4-pro and deepseek-v4-flash, plus 220+ routes across 30+ providers
PricingVendor list prices, hard to beatThin markup over provider list prices; see /pricing
Where prompts goThe vendor's own infrastructureAn attested gateway; Confidential requests never reach the vendor
Retention proofPrivacy policy and termsHardware attestation, checkable live, bound to the TLS session
Outage handlingSingle providerAutomatic fallback across providers
Verify, don't trust

Run the attestation check yourself.

Other US hosts also serve DeepSeek outside China with zero-retention policies, and that is a real improvement over first-party routing. They still ask you to take the policy on faith. TrustedRouter's gateway proves it: run curl "https://api.trustedrouter.com/attestation?nonce=$NONCE" and check the returned JWT against the published image digest. Your compliance team gets evidence, plus the DPA, subprocessor list, and SOC 2 readiness documentation to assess it with.

Hosting is the control point for Chinese open-weights generally. In our testing, the same GLM weights answered 60 of 60 sensitive questions through TrustedRouter's enclave versus 30 of 60 via the vendor-hosted API; the filtering is host-applied, not in the weights. One anonymized proof point: a document-processing company scaled from zero to over a billion tokens per week through the attested gateway within three weeks of onboarding. Use the live model catalog for current DeepSeek model IDs, try one in the playground, compare current latency on the live leaderboard, and inspect stable history in the monthly benchmark reports.

Live catalog evidence

Current routes, prices, privacy, and measured performance.

Catalog facts come from the routes currently configured in TrustedRouter. Performance uses the same cached metadata snapshot as the public leaderboard. Prompts and outputs are not part of these measurements.

583public models
108providers
1757configured routes
368ZDR routes
42provider E2EE routes
5839recent availability samples
Model Providers Context Input Output Privacy Measured route
DeepSeek: DeepSeek V4.1 Flashdeepseek/deepseek-v4.1-flash
+21
37 routes
1,048,576 $0.0422/1M to $2.11/1M $0.0844/1M to $10.55/1M Confidential + ZDR 2803 ms TTFT telnyx · 92.76% available · n=1541
DeepSeek: DeepSeek V4 Flash 0731deepseek/deepseek-v4-flash-0731
+24
37 routes
1,048,576 $0.0422/1M to $0.495431/1M $0.09495/1M to $1.3926/1M Confidential + ZDR 1677 ms TTFT confidential-ai · 234 tok/s · 100.00% available · n=105
DeepSeek: DeepSeek V4 Flash 0423deepseek/deepseek-v4-flash
+9
18 routes
1,048,576 $0.09495/1M to $0.320079/1M $0.1899/1M to $0.842312/1M ZDR 5 cited scores 1256 ms TTFT deepseek · 80 tok/s · 100.00% available · n=31
DeepSeek: DeepSeek V4 Pro 0423deepseek/deepseek-v4-pro
+13
27 routes
1,048,576 $0.15825/1M to $2.532/1M $0.633/1M to $5.064/1M ZDR 5 cited scores 1543 ms TTFT deepseek · 100.00% available · n=29
DeepSeek: DeepSeek V3.2deepseek/deepseek-v3.2
+5
14 routes
163,840 $0.2743/1M to $3.165/1M $0.4009/1M to $4.7475/1M Confidential + ZDR 3 cited scores 3539 ms TTFT sambanova · 100.00% available · n=19
DeepSeek-V4-Flash-0423deepseek/deepseek-v4-flash-0423
2 routes
1,048,576 $0.1477/1M $0.2954/1M ZDR 1602 ms TTFT wafer · 100.00% available · n=17
CrusoePolicy varies 13 models 1348 ms p50 · n=34
DeepInfraPolicy varies 90 models 2821 ms p50 · n=494
GMI CloudPolicy varies 73 models 2800 ms p50 · n=26
Novita AIPolicy varies 77 models 2168 ms p50 · n=25
SiliconFlowPolicy varies 27 models 1874 ms p50 · n=26
TogetherZDR 13 models 1170 ms p50 · n=274
WaferPolicy varies 8 models 1602 ms p50 · n=39
TinfoilConfidential + ZDR 6 models 3017 ms p50 · n=496

Browse every modelReview provider policiesOpen the full leaderboardSnapshot 2026-10-13T12:23:11.817Z

Questions

Is the DeepSeek API safe to use?

It depends on which endpoint you call. api.deepseek.com is the vendor's own service, and several US states have restricted it on government devices. TrustedRouter serves the same MIT-licensed V4 weights through a hardware-attested gateway, and DeepSeek's own API is one of its routes. With Confidential privacy (provider.min_privacy "confidential"), prompts never reach the model vendor: a Confidential request routes only to third-party confidential-compute hosts, and fails rather than fall back to the vendor's own API. TrustedRouter never logs prompt or output content. Ordinary synchronous and streaming inference does not retain it. The opt-in Batch API temporarily retains enclave-encrypted artifacts for up to 30 days. You can verify the attestation live at any time instead of relying on a policy.

Does using DeepSeek through TrustedRouter send data to China?

It can on Standard routing, where DeepSeek's own API is one of the V4 routes. With Confidential privacy (provider.min_privacy "confidential"), prompts never reach the model vendor: a Confidential request routes only to third-party confidential-compute hosts, and fails rather than fall back to the vendor's own API. Zero-Data-Retention routes add a contractual guarantee that providers keep nothing. Each route's privacy tier is listed on the models page, and the gateway's attestation is checkable live.

How do I require DeepSeek zero data retention?

Set provider.min_privacy to zdr on a DeepSeek request. The router then considers only endpoints with a recorded zero-data-retention posture and fails closed if none are eligible. TrustedRouter never logs prompt or output content. Ordinary synchronous and streaming inference does not retain it. The opt-in Batch API temporarily retains enclave-encrypted artifacts for up to 30 days. The ZDR filter adds the downstream provider requirement.

Which DeepSeek model ID should I use?

Read the live TrustedRouter model catalog and choose the current DeepSeek route for your workload. The API is OpenAI-compatible, so changing generations is a model-id change rather than an SDK migration. The live leaderboard shows current route behavior, while monthly benchmark reports preserve historical measurements.

Workspace access

Sign in

Choose a sign in method to access your TrustedRouter workspace.

New to TrustedRouter?

By continuing you agree to the terms of service and privacy policy.