Discover the Mistral Console

Updated November 2, 2026 — Models. Mistral Large 3 (mistral-large-2512) and Mistral Medium 3.5 were deprecated on October 31, 2026, and will be retired on April 30, 2027. Their designated successor, Mistral Large 4 (mistral-large-4), has been in public preview since October 6. The examples in this course use the alias mistral-large-latest, which currently points to Mistral Large 3 according to its official specification (verified November 3, 2026). Similarly, mistral-medium-latest points to Mistral Medium 3.5. These aliases will remain valid until April 30, 2027. For new projects, test mistral-large-4, their designated successor.

Your entry point: console.mistral.ai

Before you write a single line of code, you need to open the door. That door is the Mistral Console. You can find it at console.mistral.ai. It centralizes everything your code cannot do on its own: generating API keys, monitoring usage, and organizing workspaces. Creating an account requires a professional email address and a strong password. If you prefer to avoid managing another credential, the sign-up screen offers authentication via Google or GitHub. Within seconds, you are logged in and looking at the dashboard.

What the dashboard tells you

The dashboard provides a high-level view of your activity. It displays your real-time usage—token count and estimated costs—along with a list of your active API keys and their status. You will also see available models with quick links to their documentation, plus any alerts, such as a reached quota or an expired key. Make it a habit to check this view at the start of every session. If you haven’t launched anything since Friday but the token counter moved over the weekend, that anomaly almost always signals a test script left running or a leaked key. The dashboard is your first incident detector, long before the bill arrives.

Workspaces: The art of isolation

Workspaces are isolated environments. Each one has its own API keys, quotas, and members. This separation is critical for business use. By dedicating a workspace to each project, you cleanly separate development, staging, and production environments. This ensures that an enthusiastic load test in development never drains the quota serving your real users. By dedicating a workspace to each team, you allow data, product, and research teams to manage their own usage independently, without fighting over a shared budget.

Access controls complete this setup. Invite collaborators with distinct roles—Administrator, Developer, or Viewer—based on what they need to do. An intern analyzing costs has no reason to revoke a production key; the Viewer role gives them exactly what they need, nothing more.

Above the workspaces sits the Administration Portal, accessible at admin.mistral.ai. This is where you configure global organization settings: member and role management, billing configuration, spending limits set per workspace, and audit logs tracking every action. These logs come in handy the day you need to answer, “Who created this key, and when?”

Create your first workspace

The process is simple. Click the “New Workspace” button in the sidebar, give it a clear name like “Support Chatbot Project,” and add a description if you wish. The workspace is ready immediately, with no approval wait time.

Every workspace receives a unique UUID identifier. This ID appears on your invoices and in audit logs, making internal chargebacks much less painful when multiple projects run in parallel. Instead of guessing how to split a global total, you get one line item per workspace.

Adopt a consistent naming convention from day one, such as {team}-{project}-{env}. data-chatbot-prod is unambiguous, unlike “test2,” which no one will dare delete six months later. Also, limit the number of administrators; one or two per workspace is enough to maintain control without blocking daily work. Finally, use the description field to note the intended use. The next person to join the team will read this, and it will save them from creating a duplicate.

Before you move on

The next lesson covers creating your API key. It assumes three things: your account is active (you confirmed your email), you have at least one workspace, and you can access the Administration Portal. Verify these three points now to avoid hunting for a missing option in ten minutes.

One last tip if you are joining an organization that already uses Mistral: do not create your own workspace in a corner. Ask the administrator to invite you to the one that matches your project. A rogue workspace means billing that escapes tracking and keys that no one thinks to rotate.

Key takeaways

• The Mistral Console lives at console.mistral.ai—it is your command center
• Workspaces isolate projects, quotas, and API keys
• The Administration Portal (admin.mistral.ai) manages members, billing, and audits
• Organizing your workspaces well from the start prevents confusion as your projects multiply