Three reports in Mistral AI’s official Python client issue tracker describe problems that can be easy to miss: transcription requests that reportedly ignore context_bias for URL-based audio, cached-token details that appear in a raw response but are awkward to access through the SDK model, and a missing API key that reportedly is not detected until the first API call. These are reports tied to specific package versions—not confirmation that the same behavior persists in current releases.
What these reports do—and do not—establish
The examples below come from individual reports in the official Mistral Python client issue tracker. They are not an official list of exactly three bugs, nor do they establish present-day behavior across the SDK. The reports identify different package versions and different failure modes; each should be checked against the version and response shape in your own application.
As an Amazon Associate I earn from qualifying purchases.
Mistral’s migration guide maps v1 to mistralai<2 and v2 to mistralai>=2. It also changes the v2 import from from mistralai import Mistral to from mistralai.client import Mistral. That distinction matters when reproducing an issue: a v1 example is not automatically a valid v2 test. See the official migration guide.
Why might URL-based transcription ignore context_bias?
What the report says
In issue #338, the reporter described a transcription request using file_url rather than an uploaded audio file. The request reportedly succeeded, but the supplied context_bias was not applied. The report identifies mistralai==1.12.0 and Python 3.12.3.
#1 Best Overall
The reporter attributed the difference to request encoding: their account says that when the files list was empty, the SDK sent application/x-www-form-urlencoded rather than multipart/form-data. The issue includes a direct curl request using -F flags as a workaround. This is the reporter’s explanation and proposed workaround, not an independently verified cause or a confirmed fix.
What to check
- Confirm whether your request supplies audio through
file_urlor an uploaded file. The report concerns URL input; it does not establish that uploaded-file transcription has the same behavior. - Check the installed SDK version and the request actually sent, including its content type and whether the bias value is present.
- If you try the issue’s multipart
curlworkaround, treat it as a diagnostic comparison, not proof that the current SDK has a defect or that the workaround is supported for every endpoint version.
The issue report does not establish whether #338 has since been fixed. See issue #338 for its report and discussion.
Why can prompt_tokens_details look empty in Python?
Raw JSON and typed SDK fields are different views
Issue #572 describes a chat-completion response whose raw HTTP payload included prompt_tokens_details and a cached_tokens value, while the SDK’s UsageInfo model did not declare that field. The reporter says the extra data therefore remained an untyped dictionary; code using attribute access could see None and mistakenly infer that no prompt tokens were cached. The report identifies mistralai==2.4.9 and Python 3.12.
Recommended Free Tools
This distinction is important: a field visible in raw JSON is not necessarily a declared model attribute. If you are diagnosing an apparent zero or missing cached-token count, inspect the actual serialized response as well as the typed object, and verify how the installed SDK represents extra fields. Do not infer that the server returned no cache details solely from an attribute access result.
Issue #572 is a report, not independent confirmation of current server responses or current SDK model behavior. The available issue record does not establish whether the issue has been fixed. Follow issue #572 for the report and any subsequent discussion.
Why can Mistral() accept a missing API key?
Construction may not be the first point credentials are checked
In issue #519, a reporter said that constructing Mistral() without an explicit key and without MISTRAL_API_KEY succeeded, with the missing credential only becoming apparent on the first API call. The report concerns mistralai 2.4.5. In practical terms, a successful client constructor was not a reliable check that the application had usable credentials.
For applications that need an early configuration failure, validate the key in your own startup path before making the first network request. Mistral’s repository documents the Python client, API-key setup, and debug logging in its official client repository. Avoid logging the key itself when diagnosing configuration.
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →The issue is marked closed, but its text does not identify the fix or a release containing it. Closure alone does not prove which behavior a particular installed version has. See issue #519.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.How the three reports differ
| Report | Version and conditions described | Reported mismatch | Fix status established by the cited report |
|---|---|---|---|
| #338 | mistralai==1.12.0, Python 3.12.3; transcription with file_url |
Request reportedly succeeds but ignores context_bias; reporter attributes this to encoding when no files are attached |
No verified fix established |
| #572 | mistralai==2.4.9, Python 3.12; chat completion usage details |
Raw response reportedly contains cached-token details absent from declared UsageInfo attributes |
No verified fix established |
| #519 | mistralai 2.4.5; client constructed without an explicit key or environment key |
Construction reportedly succeeds; missing credential surfaces on first API call | Marked closed; fix and release not identified in the report |
Check package safety before installing or upgrading
The version details in these reports are for identifying their reported environments, not recommendations to install those releases. Separately, the official repository security advisory identifies PyPI mistralai==2.4.6 as malicious, says versions 2.4.5 and earlier are not known to be affected, and recommends pinning to 2.4.5 or earlier while the PyPI project is quarantined. Advisory status can change, so check the official security advisories before selecting an install or upgrade version. This package-security issue is separate from the three behavior reports discussed above.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
