NextBit (EU)
Try NextBit (EU) on us. Starter credit covers your first requests, then one key reaches all 4 NextBit (EU) models, with the privacy posture shown on every route.
NextBit (EU)nextbit-eu
These privacy labels describe NextBit (EU), 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 | NextBit (EU) |
|---|---|
| API operator country | ES Legal home of the API operator, not an inference-location guarantee. |
| Headquarters | Not verified |
| Routing status | Active |
| Provider website | https://nextbit256.com/ |
| Models | 4 public models |
| Credits routes | 4 |
| Zero data retention | yes All routes |
| Verified confidential inference | Not verified |
| Policy note | NextBit's EU API processes inference exclusively in Spain. Its public DPA sections 4 and 11 prohibit retaining prompts, outputs, or content logs and using them for training; operational metadata is retained. This route uses eu.api.nextbit256.com, never the global API. Special-category personal data requires a separate agreement under section 13. No confidential-compute or E2EE claim is made. 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
- Spain (EU)
The EU API's DPA commits to inference exclusively on NextBit infrastructure in Spain. - Can locations change?
- Model availability can change; the EU endpoint must not route inference outside Spain.
- Provider region pinning
- Use https://eu.api.nextbit256.com/v1, not the separate global endpoint.
- Pinning through TrustedRouter
- Select provider.only=[nextbit-eu] with allow_fallbacks=false and min_privacy=zdr.
- Infrastructure declaration
- Spain-only inference; gateway in the EU. Operational metadata retained; no content retention.
- Evidence
- Public DPA sections 4 and 11; EU catalog declares ES for every model; authenticated inference smoke. 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
5 samplesContinuously sampled across NextBit (EU)'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 | 1843 ms |
|---|---|
| Effective throughput | 58 tok/s n=1 |
| Uptime | 100.00% |
| Model | p50 TTFT | Effective throughput | Uptime | Config excluded | Availability samples |
|---|---|---|---|---|---|
| google/gemma-4-26b-a4b-it | 1379 ms | — | 100.00% | — | 2 |
| qwen/qwen3-14b | 1843 ms | — | 100.00% | — | 2 |
| google/gemma-3-27b-it | 2774 ms | — | 100.00% | — | 1 |
| google/gemma-3-12b-it | — | 58 tok/s n=1 | — | — | 0 |
NextBit (EU) performance history · Full provider & model leaderboard.
Models served by NextBit (EU).
Each row links to pricing, provider, benchmark, and API pages for the model.
| Model | AI IQ | Context | Input | Cached input | Output |
|---|---|---|---|---|---|
google/gemma-3-12b-itGoogle: Gemma 3 12B |
— | 131,072 | $0.1055/1M | $0.05275/1M | $0.184625/1M |
google/gemma-3-27b-itGoogle: Gemma 3 27B |
— | 131,072 | $0.0844/1M | $0.0422/1M | $0.36925/1M |
google/gemma-4-26b-a4b-itGoogle: Gemma 4 26B A4B |
IQ 99#127 | 262,144 | $0.09495/1M | $0.05275/1M | $0.3165/1M |
qwen/qwen3-14bQwen: Qwen3 14B |
— | 40,960 | $0.1055/1M | Not published | $0.2321/1M |
Questions
Does NextBit (EU) have zero data retention?
TrustedRouter records NextBit (EU) as supporting provider-level zero data retention based on the policy source linked on this page. This is a provider policy claim, separate from TrustedRouter's content-stateless real-time gateway and from end-to-end confidential compute.
Is NextBit (EU) end-to-end encrypted?
TrustedRouter does not currently mark NextBit (EU) 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 NextBit (EU) models are available through TrustedRouter?
This page currently lists 4 public NextBit (EU) models, with live pricing, route count, context length, measured performance when available, and links to each model's provider and benchmark pages.