Ethical Stack.

Mistral API (Studio)

Developer API for Mistral-hosted language and multimodal models.

Score calculation

(3 + 6 + 4 + 2 + 3) ÷ 5 = 3.6

5 of six dimensions rated. Unrated dimensions are excluded from the average.

Full scoring method ↗
Setup details

Mistral API endpoints for developer accounts; consumer Vibe and self-hosted open weights are separate.

What fits your needs

Mistral API endpoints for developer accounts; consumer Vibe and self-hosted open weights are separate.

Where it fits

Use Studio API keys and model IDs to integrate Mistral models into an application.

See the evidence
Tradeoffs to expect

Route and limits

Default API retention is 30 rolling days for abuse monitoring; ZDR is limited to supported endpoints and has to be enabled.

See the evidence
How to switch

Try it

Create a Studio account and API key, then test the model ID and endpoint you plan to use.

See the evidence
Practical questions

Before relying on it

Confirm API vs Agents route, ZDR eligibility and status, model, endpoint region and account plan.

See the evidence

Energy practices

3/10↑

Public docs establish the Mistral API endpoint and selected model route; they don’t confirm its request-level physical footprint. The API supports model selection, max_tokens and other request controls; these limit or configure workload but do not measure physical savings.

See the evidence

This practices and disclosure grade covers Mistral API endpoint and selected model. Public product/API documentation establishes how this route operates and the listed user controls, but gives no measured per-request energy, emissions or water. A corporate electricity claim is not allocated to this route.

1 + 1 reporting + 0 electricity + 1 controls = 3/10. This grades documented practices and transparency.

Request-level electricity, emissions, water use, serving utilization and any route-specific clean-power matching are not reported for Mistral API endpoint and selected model.

Reporting1/3
Official documentation describes the Mistral API endpoint and selected model operating boundary, but does not publish a dated quantitative energy, emissions or water result for this route.
Electricity sourcing0/3
The reviewed sources do not map Mistral API endpoint and selected model to a site-specific electricity mix or time-matched clean-power supply.
Resource controls1/3
The API supports model selection, max_tokens and other request controls; these limit or configure workload but do not measure physical savings.

Water disclosure

Water reporting has not been assessed for this choice.

Training data

—Depends on the model↑

The API offers multiple Mistral models and may add new versions; assess the training data and rights for the selected model release.

See the evidence

Mistral’s API documentation defines a model-selected inference route; its privacy policy describes user-input use and retention separately. Neither source is a complete provenance and permission record for each model training data.

Selected model, training data inventory, third-party datasets, permissions, filtering, and creator remedies vary by model.

Your data & privacy

6/10↑

Mistral’s privacy policy says API inputs and outputs are retained for generation and then 30 rolling days for abuse monitoring unless zero data retention is enabled for a supported endpoint; Agents and fine-tuning have different retention.

See the evidence

The current Mistral privacy policy sets a default API input/output retention period of 30 rolling days for abuse monitoring, with zero data retention available for supported stateless endpoints. It excludes the Agents API and fine-tuning from that general window, so the endpoint type and ZDR eligibility change the result.

Retention and a ZDR route are documented, but default API calls retain prompts for abuse monitoring and endpoint coverage differs.

Account plan, endpoint type, ZDR activation, region and organization settings determine the exact route and retention.

Openness

4/10↑

A documented hosted API for Mistral models with self-hostable weights available for some models under separate licenses.

See the evidence

Mistral provides API documentation and model selection for managed inference. Some model releases have downloadable weights, but those licenses do not expose the hosted API runtime or make all API models self-hostable.

API interface is documented, with some separately available weights but provider-managed inference.

Model weights and licenses vary across model families and do not apply to every API endpoint.

Worker protections

2/10↑

Mistral publicly says its supplier code applies to goods and services and its Trust Center shows contractors acknowledge a code, but labor-specific provisions and outcomes were not publicly inspectable.

See the evidence

Mistral’s August 2026 help page states that its Code of Conduct sets standards suppliers are expected to follow for Mistral business and all supplier goods/services; the Trust Center lists contractor acknowledgment of the Code of Conduct. The public interface did not expose the code’s labor clauses or worker procedures, and no worker survey, audit, pay/conditions disclosure or remediation results were located. This supports limited credit for a supplier-code commitment only. These findings concern the developer or operator. This product’s use in a particular deployment needs separate evidence.

1 + 1 pay & conditions + 0 worker voice & remedy + 0 evidence & follow-through = 2/10. This grades documented worker safeguards, not a measured rate of mistreatment.

The supplier code’s detailed labor language and coverage of AI data workers, grievance route, monitoring and outcomes were not accessible from the public Trust Center.

Pay & conditions1/3
A supplier code is a stated business requirement, but its labor content and implementation were not publicly inspectable in this review.
Worker voice & remedy0/3
No public worker-specific voice or grievance mechanism was established in the accessible sources.
Evidence & follow-through0/3
The Trust Center shows contractor code acknowledgment but no labor-specific audits, remediation or outcomes.
Workers rubric ↗

Military ties

3/10Broad defense ties↑

Mistral AI publicly partners with defense AI company Helsing on joint development of vision-language-action models, and its current company page says it serves defense customers. A separate Airbus agreement includes military aerospace applications; specific Mistral model deployments in weapons systems are not established.

See the evidence

Mistral's announcement with Helsing describes joint development of next-generation AI systems for European defense, while Helsing's announcement links its military AI portfolio to Ukraine-deployed strike drones and fighter electronic-warfare capabilities. Mistral also identifies defense as a customer sector and Airbus says the partnership includes military aerospace applications. This is broad defense enablement, capped at 3/10; no binding weapons/surveillance prohibitions or military-use oversight outcomes are public in these sources. These findings concern the developer or operator. This product’s use in a particular deployment needs separate evidence.

1 + 0 use restrictions + 0 enforcement & oversight + 2 relationship disclosure = 3/10. Known defense ties lower this rating; safeguards can improve it within the relationship’s cap.

The sources don’t confirm which Mistral models, if any, are deployed in specific military systems, the operational purpose or safeguards, contract restrictions, or independent oversight. Helsing's existing strike systems are not evidence that Mistral models themselves control or target weapons.

Use restrictions0/4
The reviewed public partnership and company materials do not disclose binding restrictions on weapons, harmful surveillance, or military-intelligence use.
Enforcement & oversight0/3
No public military-specific review, enforcement mechanism, or independent outcome assessment was identified in the reviewed partnership materials.
Relationship disclosure2/2
Mistral and its partners identify the defense relationships and intended applications, including VLA model development and military aerospace, though no model-level deployment details or outcomes are disclosed.

Mistral publicly confirms joint defense-AI development and military-aerospace partnerships, but no source establishes its model in actual targeting or combat intelligence use. The relationship limits this grade to 3/10.

Military rubric ↗

BDS targets

Not listed↑

We did not find Mistral AI among the named targets in the two official BNC campaign lists. This is a limited list check, not BDS approval.

See the evidence

Mistral AI is not a named target in the checked lists, but BDS uses selective campaigns, so absence cannot establish a clean record. Running downloaded weights locally is a different decision from paying the developer or a cloud host; check the host as well. These findings concern the developer or operator. This product’s use in a particular deployment needs separate evidence.

This review covers the named targets in the BNC consumer/pressure guide and No Tech campaign, not every BDS campaign, local group, investment or supplier. Lists and ownership can change. A company’s absence from these lists is not an endorsement or proof that it has no relevant relationships.

More from Mistral AI

All sources

Side by side