{user_name}
Mistral AI hero banner for a WordPress guide on creating Mistral API keys

Create Mistral API Key: Guide for WordPress and API Integration

This guide explains how you create a Mistral API Key for the European AI alternative and insert it into your WordPress plugin.

Short & to the point

  1. Sign in to Mistral Studio or create an account.
  2. If needed, create a workspace and accept the terms of use.
  3. Open the API Keys section in the Studio.
  4. Create a new key, give it a name and set an expiration date.
  5. Insert the Mistral API Key into your WordPress software, for example in neo WP AI, and test the connection.

Mistral AI is a European provider of modern Large Language Models (LLMs). For your own applications, backends, automations or WordPress extensions access is via the Mistral API. For that you need a API Key from Mistral Studio.

This guide covers the typical topics around creating a Mistral API Key, creating a Mistral API secret, setting up Mistral API integration and Mistral API Key for WordPress.

1. Sign in to Mistral or create an account

The start is via the Mistral homepage or directly via Mistral Studio. Existing accounts just log in, new users create an account first.

Mistral Studio login screen mockup with email field and social sign-in buttons, for creating a Mistral API key guide
Mistral Studio login or start view as entry to API management.

2. Set up a workspace

With a new account you often first create a workspace. A recognizable name is useful, for example for a project, website or client. API Keys are tied to the workspace.

Mistral Studio workspace creation popup showing ”WordPress AI Usage” name field for creating an API key and workspace
Workspace setup in Mistral Studio: separate workspaces help with clients, staging and production.

3. Open API Keys in the Studio

After login the key management is in the API Keys area. There you can create new keys, manage existing keys and revoke keys if needed.

Screenshot of Mistral Studio sidebar highlighting the API Keys tab to guide creating and inserting a Mistral API key for WordPress integration
API Keys view in Mistral Studio where new keys are created and existing keys are managed.

4. Create a new Mistral API Key

Use the Create new key button to create a new API Key. An expiration date is useful for tests, client projects and temporary integrations but can be omitted.

Screenshot of Mistral Studio ”My API Keys” dialog showing creating a WordPress AI API key with name, scope, and expiration fields
Create-key dialog in Mistral Studio with name and expiration date for the new API Key.

5. Insert Mistral API Key into WordPress

After creation the Mistral API Key is shown in full. The complete key will not be visible again later. Copy it immediately and store it e.g. in a password manager.

If you use a WordPress plugin like neoAI you usually paste the key into a protected backend field there and then test the connection.

Screenshot of Mistral Studio ”My API Keys” page showing a newly created API key in a green success box with a highlighted Copy button for WordPress integration
In a WordPress plugin the Mistral API Key belongs in a protected backend field.

6. Mistral API integration in WordPress or your own app

For a Mistral API Key WordPress use the key belongs in a protected setting or in the server configuration. API requests should run through PHP or a backend module, not directly from JavaScript in the frontend.

7. Costs, Free Mode, billing and rate limits

API costs depend on the model, the number of tokens, the type of usage and possibly on batch or special features. Before using in production check the official Mistral pricing page and billing in the Admin Console.

According to Mistral documentation API keys work by default in Free Mode for evaluation and prototyping. Rate limits are controlled among other things by requests per second, tokens per minute and tokens per month.

8. Common errors with Mistral API Keys

  • 401 Unauthorized: The key is missing, copied incorrectly, expired, belongs to the wrong workspace or is not sent as a Bearer token.
  • 400 Bad Request: The request is formally wrong. Check JSON, endpoint, model name and roles in the messages payload.
  • 402 Payment Required: In some setups an active payment method or an appropriate billing status is missing.
  • 404 Not Found: Endpoint or resource does not exist, the model name is wrong or the URL is not correctly formatted.
  • 429 Too Many Requests: A rate limit has been reached.
★★★★★

Rate now!

[{user_coupon}]

{user_discount} Discount

Redeem now!