Darkbloom
Explore Darkbloom models on TrustedRouter with current routes, token pricing, policy sources, privacy posture, regional availability, and API support.
Darkbloomdarkbloom
No provider claim
These privacy labels describe Darkbloom, the upstream model provider. ZDR is a retention policy; verified confidential inference additionally requires attested provider compute and end-to-end encryption.
| Provider | Darkbloom |
|---|---|
| Routing status | Not routable |
| Provider website | https://darkbloom.dev/ |
| Models | 0 public models |
| Credits routes | 0 |
| Zero data retention | not claimed |
| Verified confidential inference | Not verified |
| Policy note | Credentials are staged for provider discovery, but no canaried route with exact first-party pricing is published yet. No contractual ZDR, confidential-compute, or E2EE claim is tracked. Policy source |
Models served by Darkbloom.
Each row links to pricing, provider, benchmark, and API pages for the model.
| Model | AI IQ | Context | Input | Cached input | Output |
|---|
Questions
Does Darkbloom have zero data retention?
TrustedRouter does not currently mark Darkbloom 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 Darkbloom end-to-end encrypted?
TrustedRouter does not currently mark Darkbloom 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 Darkbloom models are available through TrustedRouter?
This page currently lists 0 public Darkbloom models, with live pricing, route count, context length, measured performance when available, and links to each model's provider and benchmark pages.