By default, Logic automatically routes your document execution to the optimal model based on your document’s requirements. However, you can bypass this routing and explicitly specify which model and reasoning level to use by adding the model query parameter.
Model overrides are an advanced feature. In most cases, Logic’s automatic model routing will select the best model for your use case. Only use model overrides when you have specific requirements around model selection.
When using a model override, Logic validates that your chosen model supports your document’s requirements. If your document requires capabilities the model doesn’t support, you’ll receive a 400 InvalidModelOverride error.
Capability
OpenAI
Gemini
Groq
PDF Processing
Supported
Supported
Llama only
Image Processing
Supported
Supported
Llama only
Audio Processing
Not supported
Supported
Not supported
HIPAA Compliance
Not supported
Supported
Not supported
Tool Usage
Supported
Not supported
Supported
For example, if your document processes audio input and you specify ?model=gpt-5.1:low, the request will fail because OpenAI models don’t support audio processing.
If you specify an invalid model or a model that doesn’t support your document’s requirements, you’ll receive a 400 InvalidModelOverride error:
Copy
{ "error": { "code": "InvalidModelOverride", "message": "The specified model 'gpt-5.1:low' does not support audio processing required by this document" }}