Inception Labs
Try Inception Labs on us. Starter credit covers your first requests, then one key reaches all 3 Inception Labs models, with the privacy posture shown on every route.
Inception Labsinception
These privacy labels describe Inception Labs, 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 | Inception Labs |
|---|---|
| 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://www.inceptionlabs.ai/ |
| Models | 3 public models |
| Credits routes | 3 |
| Zero data retention | not claimed |
| Verified confidential inference | Not verified |
| Policy note | No contractual zero-retention, confidential-compute, or E2EE claim is tracked for TrustedRouter's Inception account. 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.
Measured performance
28 samplesContinuously sampled across Inception Labs'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 | 1289 ms |
|---|---|
| Effective throughput | — |
| Uptime | 100.00% |
| Model | p50 TTFT | Effective throughput | Uptime | Config excluded | Availability samples |
|---|---|---|---|---|---|
| inception/mercury-2.5 | 1289 ms | — | 100.00% | — | 12 |
| inception/mercury-2 | 1070 ms | — | 100.00% | — | 8 |
| inception/mercury-3 | 1317 ms | — | 100.00% | — | 8 |
Inception Labs performance history · Full provider & model leaderboard.
Models served by Inception Labs.
Each row links to pricing, provider, benchmark, and API pages for the model.
| Model | AI IQ | Context | Input | Cached input | Output |
|---|---|---|---|---|---|
inception/mercury-2Inception: Mercury 2 |
IQ 93#156 | 128,000 | $0.26375/1M | $0.026375/1M | $0.79125/1M |
inception/mercury-2.5Inception: Mercury 2.5 |
IQ 100#126 | 260,000 | $0.0422/1M | $0.01/1M | $0.15825/1M |
inception/mercury-3Inception: Mercury 3 |
IQ 98#138 | 1,000,000 | $0.1055/1M | $0.01055/1M | $0.36925/1M |
Questions
Does Inception Labs have zero data retention?
TrustedRouter does not currently mark Inception Labs 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 Inception Labs end-to-end encrypted?
TrustedRouter does not currently mark Inception Labs 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 Inception Labs models are available through TrustedRouter?
This page currently lists 3 public Inception Labs models, with live pricing, route count, context length, measured performance when available, and links to each model's provider and benchmark pages.