What does your app need to use Mistral models?

This profile covers Mistral Studio’s developer API. Use a workspace and a developer key held on your server. Mistral’s current Free mode can let you try Studio and Vibe, while developer API access requires billing activation.

Choose a supported model for one task. A maintenance app can ask for a short title and one category from a list. Use an output format your app can read, then check whether the category actually fits before showing or saving it.

What counts toward the price and usage limits?

Check the model’s input and output rates per million tokens. The pricing table also lists separate rates for some cached inputs and other features. Audio and document features can use different units.

Check request and token limits for the organization. Workspaces can share those organization limits. Mistral describes monthly spending limits and a prepaid balance for additional pay-as-you-go use. Decide what your app shows if it cannot get a result.

How can you plan a maintenance label without sending a note?

Draw a fictional note about a loose door handle. Plan the API request, expected output and fallback on paper. Leave credentials, accounts and live notes untouched.

Choose the fields
Write a short title and one allowed category. Cross out the pretend tenant’s name, unit number and contact details.
Count input and output separately
Estimate 300 input tokens and 60 output tokens for the paper example. Multiply each estimate by the number of expected requests, then use the model’s separate rates for the two totals.
Plan what happens when the result is wrong
Write an invalid category and a missing response. Leave the ticket for manual labeling in both cases and keep the same example for checking another model later.

What can Mistral keep, and what should you record before switching?

Check the terms and settings for the exact model and feature. Mistral’s commercial terms allow training use in specified cases, including Labs or Preview models. Its zero data retention control is limited to eligible paid requests that do not need to keep state after the response.

File storage and other features can have different rules. Keep your app’s field definitions, test examples and exact model ID separately. Check model retirement and the terms for what you send or reuse before changing models.