Skip to main content
Short answer: if OpenRouter isn’t working and returns a 403 with the text Access denied by security policy, that’s the protection at OpenRouter’s front door — the request never reaches the models or the key check. This is how OpenRouter currently answers requests from Russian IP addresses (our check, 21 Nov 2026). The protection checks the IP address the request comes from, so neither a new key nor a second account will help. To keep working without a VPN, move your code to RuAPI: the request format is the same OpenAI-compatible one. You change three things — the base URL, the key and the model names (table below).

What the error looks like

A request to the API (/api/v1/chat/completions, /api/v1/models and others) gets a 403:
In the OpenAI Python SDK the error looks like this: openai.PermissionDeniedError: Error code: 403 - {'success': False, 'error': 'Access denied by security policy.'}. The openrouter.ai website doesn’t open either: instead you get a Cloudflare page, “Sorry, you have been blocked”, with the line “You are unable to access openrouter.ai”.
Checked on 21 Nov 2026 with globalping.io: hosting-provider nodes in Moscow and Saint Petersburg got this response from /api/v1/models and /api/v1/chat/completions (requests without a key), while a node in Germany got the model list for the same /api/v1/models request. Home internet nodes — MTS, Rostelecom, Beeline and MGTS — got the same response from /api/v1/models, and the same Cloudflare page instead of the site.

Why OpenRouter returns 403

  • It’s an IP block, not a key error. OpenRouter’s regular errors, according to its documentation (checked on 21 Nov 2026), look different: {"error": {"code": …, "message": …}}. This response comes from the Cloudflare protection in front of the site — the same one that shows “Sorry, you have been blocked” in a browser. The request never reaches OpenRouter’s API or the key check.
  • First payments were cut off, then access. On 11 May 2026, owners of accounts with the region set to Russia received an email from OpenRouter: the service no longer supports usage and payments associated with their geography. After that, top-ups failed both by card and with crypto via Coinbase (Habr post of 12 May 2026). Now the service itself doesn’t open either — see the check above. We found no official announcement from OpenRouter. For the top-up options that articles suggest and their risks, see How to top up OpenRouter from Russia.
  • A VPN breaches the terms. Section 5.7 of the OpenRouter terms (version of 31 Aug 2026) prohibits using a VPN or proxy to reach models whose providers don’t allow use in certain countries, or circumventing OpenRouter’s safeguards that restrict such access. A breach counts as material: access to the service can be suspended or terminated right away. Under section 9, unused credits are not refunded if you violate the terms.

What to do if OpenRouter isn’t working

How to move your code from OpenRouter to RuAPI

1

Account

Sign up at www.ruapi.ai — with email, Google or Yandex.
2

Balance

Console → Wallet: USDT or USDC (TRC20 / BEP20 / Polygon; USDT also on TON), from 5 USDT, no foreign card needed. No USDT yet? Buy it with rubles via SBP. You can also pay with a card from a foreign bank (Visa / Mastercard).
3

Key

Console → API Keys → Create API key. A RuAPI key starts with sk-; use it in place of your OpenRouter key (sk-or-…).
4

Code

Change base_url, the key and the model name. Messages, streaming, function calling and image input work as before.

Model names: OpenRouter → RuAPI

The general rule: drop the prefix before “/” (anthropic/, openai/, google/ …). For Claude models, replace the dot in the version number with a hyphen: 5.5 → 5-5. The exceptions are deepseek-flash and MiniMax-M3.1-Flash (letter case matters) — see the table. The full list is on the pricing page, or call GET https://www.ruapi.ai/v1/models with your key. Table current as of 21 Nov 2026.

What else to remove from the request

Claude Code instead of OpenRouter

OpenRouter’s guide (checked on 21 Nov 2026) sets up Claude Code like this: ANTHROPIC_BASE_URL=https://openrouter.ai/api, the key in ANTHROPIC_AUTH_TOKEN, an empty ANTHROPIC_API_KEY. RuAPI uses the same scheme; only the values change. RuAPI accepts the Anthropic Messages format that Claude Code speaks natively, so no router is needed. In ~/.claude/settings.json:
If you followed OpenRouter’s guide and set the variables in ~/.zshrc / ~/.bashrc or in the project’s .claude/settings.local.json, delete the lines with openrouter.ai and OPENROUTER_API_KEY there: project settings override ~/.claude/settings.json. Replace names like anthropic/claude-opus-5.5[1m] or ~anthropic/claude-opus-latest with names from the table above — including in ANTHROPIC_DEFAULT_FABLE_MODEL and CLAUDE_CODE_SUBAGENT_MODEL if you set them (for example claude-fable-5-2, claude-opus-5-5). ANTHROPIC_BASE_URL must not end with /v1. Then open a new terminal and run /status: the Anthropic base URL line should say https://www.ruapi.ai. Full setup: Claude Code: setup.

FAQ

No. The request is refused based on the IP address it came from, before the key is checked. From the same IP address a new key or a new account gets the same 403.
Because their requests come from an IP address in another country. In our check, a node in Germany got the usual model list from /api/v1/models, while nodes in Moscow and Saint Petersburg got a 403.
The main ones, yes: Claude, GPT, Gemini, DeepSeek, Kimi, Qwen, GLM, Grok and MiniMax (see the table above). These are the original models at their native precision, with no extra quantization. Only the names differ.
In the tool’s settings, remove the “OpenRouter” provider and connect RuAPI. Connect Claude over the Anthropic protocol so prompt caching works; connect other models as “OpenAI Compatible”. In both cases the key is your RuAPI key, and the model name comes from the table above. Depending on the tool, the base URL is https://www.ruapi.ai or https://www.ruapi.ai/v1 (tools build the request path differently), and menu names vary too, so follow the guide for your tool: Cline, Kilo Code, Roo Code, Continue.

Next steps

OpenRouter alternative

RuAPI vs OpenRouter: payment, access, refunds of unused balance.

OpenRouter: how to top up

Payment options from Russia, fees and risks — before you pay.

How to buy USDT with rubles

No USDT yet? Buy it with rubles via SBP to top up RuAPI.

RuAPI error codes

400, 401, 403, 429 — what they mean and how to fix them.