Creator specimen
August 11, 2026
Mistral AI
primary source
Regional inference makes geography an API choice
For client or source-sensitive work, add a project policy that names where material may be processed and what leaves the workspace. The proof is a readable routing receipt, not a vague privacy claim.
Source and observed change
Mistral documented regional inference with an EU endpoint, regional data processing, and a transparent pricing multiplier.
- The documentation says prompts and outputs sent to the EU endpoint are processed within the region.
- The EU regional endpoint is available while a US option is described as forthcoming.
- Regional inference is priced at 1.1 times the corresponding standard endpoint.
Mechanism to test
Residency should be selectable in the routing layer and recorded per request. A serious design also covers logs, support access, storage, embeddings, fallback regions, and what happens when a regional model is unavailable.
Human decision to expose
For client or source-sensitive work, add a project policy that names where material may be processed and what leaves the workspace. The proof is a readable routing receipt, not a vague privacy claim.
Proof packet
Input receipt
Source material, prompt, constraints, and permissions.
Process receipt
Model or instrument settings, versions, and selected branches.
Decision receipt
What the creator edited, rejected, combined, or performed.
Output receipt
Final artifact, export details, and the claim it supports.
05 · Useful contribution
Make the next artifact valuable on its own.
Publish a regional-inference checklist spanning request routing, derived data, observability, fallbacks, retention, and client disclosure.
Next specimen
Daybreak separates capability from access