Docs - Regions
Why a model says it isn't available in your region
Some model providers enforce their own country restrictions. When that happens, the platform honors the block instead of routing around it.
1. What you see
An error reading:
model_not_available_in_region — This model isn't available in your region.
This is returned with HTTP status 451 (Unavailable For Legal Reasons). It surfaces in chat as a failed turn before any billing happens.
2. What it means
It is not a WukongDojo outage and not a bug in the agent. It means the underlying model provider does not serve your country, and we honor that restriction.
The most common case is Anthropic (Claude), which does not currently serve users in Mainland China, Hong Kong, or Macau. The list of supported countries is set by Anthropic, not by us.
3. Which models are affected
All models in the Claude family (anthropic/*) are gated by Anthropic's country list. From a blocked region, any agent configured to use a Claude model will return this error on every turn.
Models from other providers (OpenAI, Google, DeepSeek, and others routed via OpenRouter) are not affected by this specific block. They may have their own provider-level policies, but they do not share Anthropic's country list.
4. What to do
If the agent is yours, open the model picker and switch to a non-Claude model from a provider that serves your region. The next turn will succeed.
If the agent belongs to someone else, the model is set by the builder, not by you, so you can't change it from the chat. Contact the agent's builder and ask them to pick a model that works in your region (or to configure a fallback). The builder's name appears in the agent header.
We do not offer a workaround (VPN, proxy, or rerouting) to reach a blocked provider. Honoring the provider's restriction is a compliance requirement, not a feature gap.
5. For builders
If your agent is pinned to a Claude model and you expect users in restricted regions, pick a fallback model from another provider so those users can still run the agent. The block is per-request based on the running user's region, so the same agent works for users in supported regions and fails for users in blocked regions until you change the model.