Models and tools
Mistral
A Mistral integration connects a Mistral workspace API key to Mobius so loops can inspect available models, files, and fine-tuning jobs.
Use Mistral when a run needs to check the models or training assets available inside a customer's Mistral workspace before choosing a downstream action.
Capability map
| Capability | Value |
|---|---|
| Provider ID | mistral |
| Auth kind | api_key |
| Connect flow | Inline API key or platform credential |
| Actions | Yes |
| Events | No |
| Webhook delivery | No |
| Event samples | No |
| Live status | No |
Connect Mistral
| Surface | Support |
|---|---|
| App | Open Govern > Integrations, choose Mistral, and paste a Mistral API key when the project should use its own workspace. |
| CLI | The mobius CLI does not connect Mistral integrations yet. Use the app or API. |
| API | Call POST /v1/projects/{project}/integrations/providers/mistral/connect with api_key. |
Mobius validates the key with Mistral model discovery before saving it. If the catalog marks Mistral ready through a platform credential, the read-only actions can run without a project-local key. Connect your own key when the run must see models, files, and fine-tuning jobs from a specific Mistral workspace.
Actions
mistral.files.list
mistral.fine_tuning.jobs.get
mistral.fine_tuning.jobs.list
mistral.models.get
mistral.models.listUse mistral.models.list to discover base and fine-tuned models, then use
mistral.models.get for the exact model a later step should inspect. Use the
file and fine-tuning job actions for visibility. They do not upload files,
start jobs, cancel jobs, or archive models yet.
Events
Mistral does not register source events. Mistral does not publish webhooks for model, file, or fine-tuning job changes through this integration, so loops that need freshness should run on a schedule or call the list actions on demand.
Next
- Pass model IDs into agent steps.
- Store reports from Mistral visibility checks as artifacts.
- Keep provider keys in integrations.