Skip to main content
Mistral’s full lineup — Large, Medium, Small, Ministral (edge sizes), Codestral (code), Devstral (dev tools), Magistral (reasoning), Pixtral (multimodal) — is routable through Verlon in whichever SDK you already use. No Mistral-specific SDK required.

Chat models

This table is auto-generated from the Verlon model registry on every sync — see the live registry for pricing, benchmarks, and deprecation dates.

Other modalities

  • audio — 4 models
  • embeddings — 4 models
  • moderation — 1 models
  • OCR / document processing — 7 models
  • speech-to-text — 3 models
  • text-to-speech — 2 models
Non-chat Mistral models are called through the Verlon SDK using the same model IDs — Mistral’s OCR line is particularly strong for document processing (see SDK reference → OCR).

Quickstart

First time? Create a gate and grab an API key — the examples below need a GATE_ID and VERLON_API_KEY.
The fastest path — Verlon SDK, one call:
Any chat model from the table above works — swap mistral-large-latest for codestral-latest, magistral-medium-latest, pixtral-large-latest, or any other ID.

SDK compatibility

The Verlon SDK is the native path to every model on this page — the quickstart above is all it takes. Already on another SDK? Any SDK with a Verlon drop-in endpoint can reach these models too — today that’s the OpenAI SDK and the Anthropic SDK: point it at Verlon, reference a gate that routes here, and your code stays unchanged.

Streaming

What’s supported

Full support for stream: true in every supported SDK — identical semantics to the source SDK.
Fully supported. Verlon translates the tool-call shape between OpenAI / Anthropic / Mistral native formats.
Image inputs work with Pixtral models — Mistral’s vision-capable line.
Codestral, Devstral, and Magistral models are available with the same call shape — swap the model ID.
temperature, max_tokens, top_p, stop, and the rest are passed through.
Every response includes token usage plus Verlon’s cost field with per-call dollar amount.

How it works

  1. You send a request in your chosen SDK’s format
  2. Verlon receives — validates the gate, applies routing rules
  3. Verlon translates to Mistral’s native format and dispatches to Mistral’s API
  4. Mistral responds with its raw response
  5. Verlon normalizes back to your SDK’s expected shape
  6. You receive a response in the format your code already handles, with an added cost field
Your existing code doesn’t know it’s talking to Mistral.

Errors

The error shape always matches the SDK you’re calling with. Through the Verlon SDK it surfaces as a thrown Error:

Full non-chat model list

Every non-chat Mistral model Verlon routes to, grouped by modality. Chat models are in the table near the top of this page.

Audio

Embeddings

Moderation

OCR / document processing

Speech-to-text

Text-to-speech