What is your goal?Why is it no longer supporting custom supplier models? It used to be possible!
What is the problem & what have you tried?Why is it no longer supporting custom supplier models? It used to be possible!
Screenshots (scenario flow, module settings, errors)Welcome to the Make community!
This is a validation enforced at the module-level, which we cannot change. Therefore, if you think this is a bug, please contact Make support directly.
As this is a community (peer-led) forum, we can only help with using the Make platform as intended (scenario building, troubleshooting scenario/module error messages, etc.). We cannot assist with bugs with the user interface/software. Make support has access to internal tools and workflows to investigate the issue further.
Before creating a support ticket, do try to look around if others are facing the same problem, and if there are further steps you can take. Here are some things you can do —
Check the Make Status page to see if it is an ongoing network-wide issue/outage and view any updates (example).
Search this Make forum to see if there are any discussions, updates, and workarounds. Here are some possible search terms you can use:
tags:error bug "not working"
If you are unable to log-in, you should use this form to report and resolve your account’s login issue first.
When you are logged in to your account, head to the new ticket page to submit a ticket.
Above: Screenshot of the Contact Support page
After submitting your support ticket, you should receive a confirmation email with the subject “Ticket Created” together with a summary of what you submitted. If you do not receive this automated reply within minutes, try creating a ticket again. Example of email subject: [#1234567] Ticket created | Technical challenge
If you do not receive a response from Make support, simply be patient. Make support receives thousands of tickets, hence tickets have to be prioritised based on the severity of the incidents and organisation’s plan. For more information about the different levels of customer support for each plan, refer to the “Support” section on the Pricing page, or on your organisation’s Subscription page. If you are a free customer, you can create a temporary free Pro account to get quicker support via the ticketing system.
When your ticket has an update and/or issue is resolved, we’d love to hear details about it, and how support and you worked to resolve it (including use of any workarounds). By posting your findings and solutions in this thread, we are contributing to this knowledgebase to enable others with similar problems to search for answers.
— @samliew
Hello @Rico,
It is still possible, but the model you are trying to use is not available in Anthropic.
You can use the List Models API endpoint from Anthropic to verify it.
curl https://api.anthropic.com/v1/models \
-H 'anthropic-version: 2023-06-01' \
-H "X-Api-Key: $ANTHROPIC_API_KEY"
You can do it by using Make’s Make an API Call module
List of models available for 14th of April 2026
[
{
"id": "claude-sonnet-4-6",
"display_name": "Claude Sonnet 4.6",
...
},
{
"id": "claude-opus-4-6",
"display_name": "Claude Opus 4.6"
},
{
"id": "claude-opus-4-5-20251101",
"display_name": "Claude Opus 4.5"
},
{
"id": "claude-haiku-4-5-20251001",
"display_name": "Claude Haiku 4.5"
},
{
"id": "claude-sonnet-4-5-20250929",
"display_name": "Claude Sonnet 4.5"
},
{
"id": "claude-opus-4-1-20250805",
"display_name": "Claude Opus 4.1"
},
{
"id": "claude-opus-4-20250514",
"display_name": "Claude Opus 4"
},
{
"id": "claude-sonnet-4-20250514",
"display_name": "Claude Sonnet 4"
},
{
"id": "claude-3-haiku-20240307",
"display_name": "Claude Haiku 3"
}
]
You can also toggle off Map switch, select model and change it back to map- it will show you parameter- for example claude-opus-4-6
For Anthropic models thinking is enabled via body:
{
"model": "claude-sonnet-4-6",
"max_tokens": 16000,
"thinking": {
"type": "enabled",
"budget_tokens": 10000
},
"messages": [
{
"role": "user",
"content": "..."
}
],
...
}
Thinking uses the same model - it simply changes how the model behaves and allocates tokens for reasoning.
Source:
claude-sonnet-4-6-thinking is not working for you- it simply does not exist.Hope it helps!
Have a nice day,
Michal
If you have a free Make plan, you are restricted in model selection, I believe.
Excause me! I thought you are referring to Anthropic model mainly because your error which clearly states that module is fetching models using RPC. Sorry!
In that case- please report it to Support Team.
What is your goal?Change the model in the Make AI Agents module to a different OpenRouter model (e.g. anthropic/claude-haiku-4.5 or deepseek/deepseek-v3.2).
What is the problem & what have you tried?I have multiple working AI Agent scenarios that were set up previously using OpenRouter with anthropic/claude-sonnet-4.6, these still run perfectly fine.
I have multiple working AI Agent scenarios that were set up previously using OpenRouter with anthropic/claude-sonnet-4.6 — these still run perfectly fine.
However, when I try to create a new AI Agent module or change the model on an existing one, I get the error:
“Value not found in options in parameter ‘Model’.”
This happens with every model string I try, including ones that are confirmed correct on OpenRouter’s API page:
anthropic/claude-haiku-4.5
anthropic/claude-sonnet-4.6
deepseek/deepseek-v3.2
openai/gpt-4.1
I have the Map toggle ON (which is how my previous working agents were configured — same method, same connection).
What I’ve tried:
Multiple OpenRouter accounts
Multiple Make.com accounts
Different model strings (with and without provider prefix)
Turning Map off (no dropdown appears, nothing to select)
Creating a brand new connection with the correct base URL (OpenRouter)
Nothing works. Old agents with the model already saved continue to function, but I cannot create new agents or modify the model on any agent.
Error messages or input/output bundlesValue not found in options in parameter ‘Model’.
Environment:
Connection type: Other Providers (Compatible with OpenAI)
Base URL: OpenRouter
AI Agents module version: Beta (latest)
This appears to be a validation issue introduced in a recent update — the module seems to be checking model strings against an internal whitelist that doesn’t include current OpenRouter models, even though the API connection itself is valid and previously saved agents still work.
Is anyone else experiencing this? Any workaround or ETA on a fix?
I’ve encountered the same problem, it’s really frustrating, and I hope the official team can provide an explanation.
Hey @here 
Thanks for reporting this issue, and we apologize for the frustrations caused by this.
We have informed our devs about the issue, and they have already jumped onto this and deployed a fix, and you should be able to choose a different model as it was possible in the past.
Let me know if you run into this issue again!
Thank you for your patience and understanding 
