I have searched for all existing open AND closed issues and discussions for similar requests. I have found none that is comparable to my request.
Verify Feature Scope
I have read through and understood the scope definition for feature requests in the Issues section. I believe my feature request meets the definition and belongs in the Issues section instead of the Discussions.
Problem Description
Following #14200, the custom Mistral API endpoint had been introduced in version 0.6.35. This addition is a step in the right direction, however, its usage is heavily limited by the use of the /files endpoint interrogation method.
Desired Solution you'd like
Following the solution proposed by @paddy313 in PR #18905, a new set of parameters should be introduced (through the env variable MISTRAL_OCR_PARAMS), to manage the file transfer method, force the use of the /ocr endpoint, and provide options for the annotations and bbox features.
Alternatives Considered
No response
Additional Context
No response
Originally created by @theobgbd on GitHub (Dec 3, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/19707
### Check Existing Issues
- [x] I have searched for all existing **open AND closed** issues and discussions for similar requests. I have found none that is comparable to my request.
### Verify Feature Scope
- [x] I have read through and understood the scope definition for feature requests in the Issues section. I believe my feature request meets the definition and belongs in the Issues section instead of the Discussions.
### Problem Description
Following #14200, the custom Mistral API endpoint had been introduced in version 0.6.35. This addition is a step in the right direction, however, its usage is heavily limited by the use of the /files endpoint interrogation method.
### Desired Solution you'd like
Following the solution proposed by @paddy313 in PR #18905, a new set of parameters should be introduced (through the env variable MISTRAL_OCR_PARAMS), to manage the file transfer method, force the use of the /ocr endpoint, and provide options for the annotations and bbox features.
### Alternatives Considered
_No response_
### Additional Context
_No response_
@owui-terminator[bot] commented on GitHub (Dec 3, 2025):
🔍Similar Issues Found
I found some existing issues that might be related to this one. Please check if any of these are duplicates or contain helpful solutions:
#17677feat: custom endpoint for mistral ocr by ion-elgreco • Sep 23, 2025
#14134feat: Customized endpoint for Mistral OCR by tiangao88 • May 21, 2025
#12035feat: Support Mistral OCR by space192 • Mar 25, 2025
#19649feat: support dots.ocr for image analysis by Busboy3129 • Dec 01, 2025
💡Tips:
If this is a duplicate, please consider closing this issue and adding any additional details to the existing one
If you found a solution in any of these issues, please share it here to help others
This comment was generated automatically by a bot. Please react with a 👍 if this comment was helpful, or a 👎 if it was not.
<!-- gh-comment-id:3605757357 -->
@owui-terminator[bot] commented on GitHub (Dec 3, 2025):
🔍 **Similar Issues Found**
I found some existing issues that might be related to this one. Please check if any of these are duplicates or contain helpful solutions:
1. [#17677](https://github.com/open-webui/open-webui/issues/17677) **feat: custom endpoint for `mistral ocr`**
*by ion-elgreco • Sep 23, 2025*
2. [#14134](https://github.com/open-webui/open-webui/issues/14134) **feat: Customized endpoint for Mistral OCR**
*by tiangao88 • May 21, 2025*
3. [#12035](https://github.com/open-webui/open-webui/issues/12035) **feat: Support Mistral OCR**
*by space192 • Mar 25, 2025*
4. [#19649](https://github.com/open-webui/open-webui/issues/19649) **feat: support dots.ocr for image analysis**
*by Busboy3129 • Dec 01, 2025*
---
💡 **Tips:**
- If this is a duplicate, please consider closing this issue and adding any additional details to the existing one
- If you found a solution in any of these issues, please share it here to help others
*This comment was generated automatically by a bot.* Please react with a 👍 if this comment was helpful, or a 👎 if it was not.
Would be very much appreciated especially to allow for Azure Mistral OCR endpoints
<!-- gh-comment-id:3606907830 -->
@JARZcorp commented on GitHub (Dec 3, 2025):
Would be very much appreciated especially to allow for Azure Mistral OCR endpoints
I confirm that being able to use /ocr endpoint for Azure AI Foundry (which is supported by LiteLLM) is a real need and would push further the usage of OpenWebUI with organizations who want tight control on their data. #14200
@paddy313 can you help us out please?
<!-- gh-comment-id:3650314022 -->
@tiangao88 commented on GitHub (Dec 14, 2025):
I confirm that being able to use /ocr endpoint for Azure AI Foundry (which is supported by LiteLLM) is a real need and would push further the usage of OpenWebUI with organizations who want tight control on their data. [#14200](https://github.com/open-webui/open-webui/discussions/14200#discussioncomment-14960935)
@paddy313 can you help us out please?
<!-- gh-comment-id:3691283650 -->
@tiangao88 commented on GitHub (Dec 25, 2025):
> I opened a PR for this - see [#20126](https://github.com/open-webui/open-webui/pull/20126)
That is a nice Xmas gift. Thank you @KevinRohn
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @theobgbd on GitHub (Dec 3, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/19707
Check Existing Issues
Verify Feature Scope
Problem Description
Following #14200, the custom Mistral API endpoint had been introduced in version 0.6.35. This addition is a step in the right direction, however, its usage is heavily limited by the use of the /files endpoint interrogation method.
Desired Solution you'd like
Following the solution proposed by @paddy313 in PR #18905, a new set of parameters should be introduced (through the env variable MISTRAL_OCR_PARAMS), to manage the file transfer method, force the use of the /ocr endpoint, and provide options for the annotations and bbox features.
Alternatives Considered
No response
Additional Context
No response
@owui-terminator[bot] commented on GitHub (Dec 3, 2025):
🔍 Similar Issues Found
I found some existing issues that might be related to this one. Please check if any of these are duplicates or contain helpful solutions:
#17677 feat: custom endpoint for
mistral ocrby ion-elgreco • Sep 23, 2025
#14134 feat: Customized endpoint for Mistral OCR
by tiangao88 • May 21, 2025
#12035 feat: Support Mistral OCR
by space192 • Mar 25, 2025
#19649 feat: support dots.ocr for image analysis
by Busboy3129 • Dec 01, 2025
💡 Tips:
This comment was generated automatically by a bot. Please react with a 👍 if this comment was helpful, or a 👎 if it was not.
@JARZcorp commented on GitHub (Dec 3, 2025):
Would be very much appreciated especially to allow for Azure Mistral OCR endpoints
@tiangao88 commented on GitHub (Dec 14, 2025):
I confirm that being able to use /ocr endpoint for Azure AI Foundry (which is supported by LiteLLM) is a real need and would push further the usage of OpenWebUI with organizations who want tight control on their data. #14200
@paddy313 can you help us out please?
@KevinRohn commented on GitHub (Dec 24, 2025):
I opened a PR for this - see #20126
@tiangao88 commented on GitHub (Dec 25, 2025):
That is a nice Xmas gift. Thank you @KevinRohn