A developer in Russia who tries Claude API and Anthropic's models (Sonnet 4.6, Opus 4.8, Haiku 4.5) hits a wall fast. The API console rejects your IP. Your card gets declined. A VPN works for a day, then stops. Below: where the blocks come from, and a working way to connect in under 10 minutes.
Claude in Russia: chat, Claude Code and the API
A search for "Claude in Russia" really covers three different jobs, and each has its own answer.
- claude.ai (the browser chat). Sign-up and payment from Russia fail for the same reasons described below: IP, phone, card. How to use Claude in Russian without an Anthropic account is covered in our guide to using Claude in Russian from Russia without a VPN.
- Claude Code (the CLI agent). The tool itself is free, but it needs access: an Anthropic subscription or an API key. Installing and configuring Claude Code through codexkey is described in our Claude Code setup guide for Russia.
- Claude API (for your own code and agents). This is the main part of the article: below, step by step, is how to connect through codexkey.
If you need only one of the three, go straight to the matching article. If you are not sure which fits, keep reading: the blocking logic is the same for chat, CLI and API.
Why Claude API is restricted in Russia
Anthropic, the company behind Claude, enforces geographic restrictions on several levels at once. That is why simple workarounds rarely last.
IP-based geo-blocking
The first layer is simple: Anthropic's servers check the source IP address of every request. Russian IP ranges are blocked at the edge. A request from a Russian IP gets a 403 Forbidden or just times out. This applies to the web console at console.anthropic.com and to the API endpoint at api.anthropic.com alike.
Payment verification
Even if you get past the IP check, Anthropic requires a valid payment method. It accepts cards issued by banks in supported countries. Russian cards (Mir, the national card network, and Visa/Mastercard from Russian banks, which have been largely cut off from international payment networks since 2022) are declined during billing setup. Without a verified payment method your API key never activates.
Phone number verification
Creating an account requires phone verification. Anthropic keeps a list of accepted country codes, and Russian numbers (+7) are not on it. Virtual numbers from services like SMS-activate sometimes pass the first sign-up but get flagged and banned within days.
Sanctions compliance
As a US company, Anthropic has to follow OFAC sanctions and export controls. Its trust-and-safety team monitors traffic and closes accounts that try to get around geographic restrictions. This is active enforcement, not a passive block.
Anthropic's supported regions policy and 12 November 2026
All of these restrictions rest on a published policy. Anthropic's Supported Regions Policy page shows an effective date of 12 November 2026. We opened the page and the policy PDF on 2 November 2026 and summarise them close to the text, without our own interpretation:
- Anthropic's products and services are available only in the listed countries and regions. That covers its apps (Claude.ai, Claude Code, Cowork), the API and developer platform, and Claude models offered through cloud platforms and authorized resellers.
- Any country or region that is not listed is unsupported. Territories and dependencies of a listed country are supported along with it.
- Use by people physically located in an unsupported region counts as unsupported, including users and personnel of otherwise supported entities.
- Use by entities incorporated or headquartered in an unsupported region, and by their users or personnel, counts as unsupported even if those people sit in a supported country.
- The same goes for entities that are majority-owned or controlled, directly or indirectly, by persons or entities in unsupported regions.
- The list has 185 countries and regions. We did not find Russia, Belarus, China, Hong Kong, Iran, Syria, Cuba or North Korea on it. Ukraine is listed with exceptions: Crimea, Donetsk, Kherson, Luhansk and Zaporizhzhia.
What the text does not say: how enforcement changes on 12 November, how the new version differs from the previous one, or how the policy treats independent API gateways.
We are not lawyers, we draw no legal conclusions and we promise no safety. Whether the policy applies to you depends on where you are physically located, where your organization is registered and who owns it. If this matters for your business, talk to a lawyer or to Anthropic. codexkey is a separate service, not part of Anthropic, and we cannot promise that access will stay the same if the vendor's rules change. A sensible minimum: do not run a single integration through one channel, and keep an eye on the policy text.
Common workarounds and why they fail
Let's be honest about what developers in Russia typically try, and why each approach has serious problems.
VPN and proxy
What people try: connect through a VPN with a US or European exit node, then use the Anthropic API as usual.
Why it fails:
- Anthropic detects many commercial VPN IP ranges and blocks them
- Even if the first connection works, billing still requires a non-Russian card
- Phone verification still requires a non-Russian number
- Anthropic's fraud detection flags accounts with inconsistent geographic signals (a US IP but no card, because you have nothing to add)
- A VPN adds 50-200ms to every API call, and that compounds with streaming responses
Foreign virtual cards
What people try: get a virtual card from Wise, Payoneer or other fintech apps that issue cards in supported countries.
Why it fails:
- Most of these services also require identity verification that excludes Russian residents
- Wise suspended Russian accounts in 2022
- Payoneer has restricted functionality for Russian users
- A service that works today can shut off access tomorrow and leave your production pipeline broken
Buying API keys from third parties
What people try: buy ready-made Anthropic API keys in Telegram channels or on forums.
Why it fails:
- Keys get revoked within days or weeks when Anthropic spots unusual patterns
- You have no control over rate limits, billing or key rotation
- The seller can use the same key at the same time, which causes rate limit errors
- No refund when the key dies
- There are legal and security risks: your data goes through the account of an unknown party
Using someone else's account
What people try: a friend or colleague abroad creates an account and shares access.
Why it fails long-term:
- Single point of failure: if they close the account, you are down
- Shared rate limits cause production issues
- Anthropic's terms of service prohibit account sharing
- No proper billing separation for business use
What works: third-party API gateways
One approach holds up reliably: a third-party API gateway. It is a service that keeps its own relationship with Anthropic (or runs equivalent infrastructure) and exposes the same API interface to you. You connect to the gateway instead of to Anthropic directly.
codexkey is built for exactly this. How it differs from the workarounds above:
- No VPN required. codexkey's servers are reachable from Russian IPs
- No foreign card required. Pay with SBP (the Russian Faster Payments System), cryptocurrency (USDT, BTC, ETH) or Russian bank cards
- No Anthropic account required. You register on codexkey and get an API key right away
- Same API protocol. The Anthropic Messages API format, so any SDK or tool that supports Claude works after a simple
base_urlchange - All models available. Claude Opus 4.8, Sonnet 4.6 and gpt-5.6-luna as the cheapest tier, with new releases as they come out
We carry Haiku too: the catalog has claude-haiku-5.5 and claude-haiku-4.5, with prices on the models page. They run in the Premium channel and are not available in the Cheap Haiku channel.
Step by step: getting Claude API access through codexkey
Step 1: register on codexkey
Open the registration page and create an account. You can sign up with email or Telegram, with no phone verification and no ID checks.
Step 2: top up your balance
In the dashboard, click "Top Up" and choose your payment method:
| Method | Via |
|---|---|
| SBP (QR code) | YooKassa, Platega |
| Russian bank card | YooKassa, Platega |
| Cryptocurrency | CryptoCloud, CryptoBot, 2328 |
Top-ups start from $1, and the balance is credited once the payment is confirmed.
SBP is the easiest: scan the QR code in your banking app and confirm the transfer.
Step 3: create an API key
Open the API Keys section in your dashboard and click "Create Key": you will get a key that looks like sk_cdx_.... Copy it and store it securely. You can create several keys for different projects.
Step 4: connect your application
Replace the Anthropic base URL with https://api.codexkey.online and use your codexkey key. That's it. Every SDK, framework and tool that supports the Anthropic Messages API works without any other code changes.
Code examples
Python with the official Anthropic SDK
import anthropic
# Just two changes: base_url and api_key
client = anthropic.Anthropic(
base_url="https://api.codexkey.online",
api_key="sk_cdx_your_key_here",
)
message = client.messages.create(
model="claude-sonnet-5",
max_tokens=1024,
messages=[
{"role": "user", "content": "Explain quantum computing in simple terms"}
],
)
print(message.content[0].text)
Python with streaming
import anthropic
client = anthropic.Anthropic(
base_url="https://api.codexkey.online",
api_key="sk_cdx_your_key_here",
)
with client.messages.stream(
model="claude-sonnet-5",
max_tokens=1024,
messages=[
{"role": "user", "content": "Write a short story about a robot learning to paint"}
],
) as stream:
for text in stream.text_stream:
print(text, end="", flush=True)
TypeScript with the official Anthropic SDK
import Anthropic from "@anthropic-ai/sdk";
const client = new Anthropic({
baseURL: "https://api.codexkey.online",
apiKey: "sk_cdx_your_key_here",
});
async function main() {
const message = await client.messages.create({
model: "claude-sonnet-5",
max_tokens: 1024,
messages: [
{ role: "user", content: "Explain quantum computing in simple terms" },
],
});
console.log(message.content[0].text);
}
main();
TypeScript with streaming
import Anthropic from "@anthropic-ai/sdk";
const client = new Anthropic({
baseURL: "https://api.codexkey.online",
apiKey: "sk_cdx_your_key_here",
});
async function main() {
const stream = await client.messages.stream({
model: "claude-sonnet-5",
max_tokens: 1024,
messages: [
{ role: "user", content: "Write a haiku about programming" },
],
});
for await (const event of stream) {
if (
event.type === "content_block_delta" &&
event.delta.type === "text_delta"
) {
process.stdout.write(event.delta.text);
}
}
}
main();
Environment variables (recommended for production)
Instead of hardcoding keys, use environment variables:
export ANTHROPIC_BASE_URL=https://api.codexkey.online
export ANTHROPIC_API_KEY=sk_cdx_your_key_here
Then your code gets cleaner:
import anthropic
# SDK picks up env vars automatically
client = anthropic.Anthropic()
message = client.messages.create(
model="claude-sonnet-5",
max_tokens=1024,
messages=[{"role": "user", "content": "Hello, Claude!"}],
)
Latency and reliability from Russia
The biggest worry with a proxy or gateway is latency. Here is what to expect from codexkey compared with the alternatives:
Response time comparison
| Setup | First token latency | Full response (500 tokens) |
|---|---|---|
| codexkey from Moscow | 200-400ms | 2-4s |
| codexkey from Saint Petersburg | 200-400ms | 2-4s |
| VPN + Anthropic direct (if it works) | 400-800ms | 4-8s |
| OpenAI API from Russia (with workaround) | 300-600ms | 3-5s |
codexkey routes traffic through optimized paths, so in practice latency is often better than a VPN connection to Anthropic directly: a VPN adds an extra network hop and often exits through congested nodes.
Uptime
A VPN-based setup has two points of failure: it depends on the VPN provider's uptime and on Anthropic's. If either goes down, you are offline.
Comparison: all your options side by side
An honest comparison of every way to access Claude API from Russia in 2026:
| Factor | VPN + Anthropic direct | codexkey | OpenAI API (with workaround) | Together.ai |
|---|---|---|---|---|
| Works from Russian IP | No (need VPN) | Yes | No (need VPN) | No (need VPN) |
| Russian card payment | No | Yes (SBP, cards, crypto) | No | No |
| Account creation | Requires foreign phone | Email or Telegram | Requires foreign phone | Email only |
| Claude models available | All (if account works) | All | None (GPT only) | Older Claude models, limited |
| Latency from Russia | 400-800ms (VPN overhead) | 200-400ms | 300-600ms (VPN overhead) | 300-500ms (VPN overhead) |
| Reliability | Low (VPN + key revocation risk) | High (no VPN) | Medium | Medium |
| Streaming support | Yes | Yes | Yes (different protocol) | Yes |
| Tool use / function calling | Yes | Yes | Yes (different format) | Partial |
| Price markup | 0% (direct) | Small markup | 0% (direct) | Varies |
| Setup time | Hours to days (if possible) | <10 minutes | Hours to days | Hours |
| Risk of account ban | High | None | High | Medium |
Why not just use OpenAI instead?
A fair question. OpenAI's GPT-4o and o1 are strong models. But developers have specific reasons to choose Claude:
- Longer context window. Claude supports up to 200K tokens, which matters for large codebases
- Code generation. Claude Sonnet 4.6 consistently outperforms GPT-4o on coding benchmarks (SWE-bench, HumanEval)
- Instruction following. Claude handles complex, multi-step prompts more reliably
- Claude Code. Anthropic's CLI agent (similar to Cursor but in the terminal) only works with Claude models
- Artifacts and extended thinking. Features unique to the Claude ecosystem
If you need OpenAI too, many developers use both: codexkey for Claude and a similar gateway for GPT.
Why not Together.ai?
Together.ai is a legitimate inference provider, but:
- It hosts open-source models and a limited selection of Claude models
- Access from Russia still requires a VPN and foreign payment
- Its Claude model versions often lag behind Anthropic's latest releases
- Rate limits are lower on its Claude models than on its open-source offerings
Advanced: using codexkey with developer tools
Claude Code
Claude Code is Anthropic's CLI agent. To connect it to codexkey:
export ANTHROPIC_BASE_URL=https://api.codexkey.online
export ANTHROPIC_AUTH_TOKEN=sk_cdx_your_key_here
export ANTHROPIC_DEFAULT_OPUS_MODEL="claude-opus-5-5[1m]"
export ANTHROPIC_DEFAULT_SONNET_MODEL="claude-sonnet-5[1m]"
export ANTHROPIC_DEFAULT_HAIKU_MODEL="claude-sonnet-5"
claude
The ANTHROPIC_DEFAULT_* lines are required: without them Claude Code asks for its own default models and answers "There's an issue with the selected model".
That's it. Claude Code reads these environment variables and connects through codexkey on its own.
Cursor IDE
In Cursor settings, go to Models → Add Custom Model:
- API Base URL:
https://api.codexkey.online - API Key: your
sk_cdx_...key - Model:
claude-sonnet-5
LangChain / LlamaIndex
Both frameworks let you set a custom base URL for the Anthropic provider:
from langchain_anthropic import ChatAnthropic
llm = ChatAnthropic(
model="claude-sonnet-5",
anthropic_api_url="https://api.codexkey.online",
anthropic_api_key="sk_cdx_your_key_here",
)
Security and privacy
A reasonable concern: if your API calls go through a third party, what happens to your data?
- codexkey does not store your prompts or completions
- API traffic is encrypted with TLS 1.3
- API keys are stored as hashes in the database, so even a database breach would not expose your key
- You can rotate keys right from the dashboard
- Request and response content is not logged: only metadata (model, token count, timestamp) is kept for billing
FAQ
Is it legal to use Claude API from Russia through a gateway?
We do not give legal conclusions. Third-party API gateways are common in many countries: your agreement is with codexkey and you have no Anthropic account. At the same time, Anthropic's supported regions policy describes use by people and organizations in unsupported regions, and Russia is not on the list. The policy does not say how it applies to intermediaries and their customers. If this matters for your business, consult a lawyer.
What do we know about Anthropic's regions policy from 12 November 2026?
The Supported Regions Policy page shows an effective date of 12 November 2026. Anthropic's products are available only in the listed countries and regions, and Russia is not on the list. Use by people physically located in an unsupported region, and by organizations registered or controlled from one, counts as unsupported. The page does not explain how enforcement will change after that date.
Can Anthropic's policy affect access through codexkey?
We do not know and will not guess. The policy text does not mention API gateways separately, and vendor rules can change. Do not run a single integration through one channel: set up your code so that switching provider means changing an address and a key.
Do I need a VPN to use codexkey?
No, that is the whole point. codexkey's servers are reachable from Russian IP addresses directly: no VPN, no proxy, no Tor, just a regular internet connection.
Which Claude models are available?
All current Claude models: Claude Opus 4.8 and Claude Sonnet 4.6, plus gpt-5.6-luna as the cheapest tier. New models typically show up in codexkey within 24-48 hours of Anthropic's public launch.
How does pricing compare to Anthropic direct?
codexkey adds a small markup over Anthropic's base prices to cover infrastructure and payment processing. The exact rates are on the codexkey pricing page. For most developers the markup is much smaller than the cost of keeping a VPN, foreign virtual cards and dealing with account bans.
Do extended thinking and tool use work?
Yes. codexkey proxies the full Anthropic Messages API, including extended thinking (beta), tool use / function calling, vision (image inputs) and streaming. If Anthropic supports it, it works here too.
What happens if my balance runs out mid-request?
The current request completes (you will not get a truncated response), but later requests return a 402 Payment Required error until you top up. Set up balance alerts in the dashboard to avoid surprises.
Is there a free tier or trial?
Check current offers on the codexkey site: promotional credits may be available for new accounts. The minimum top-up via SBP is about 100 ₽ (from one dollar), which is enough for testing with gpt-5.6-luna or a few hundred requests with Sonnet.
Can I use codexkey for production workloads?
Check model and channel availability before going to production and handle provider errors in your client. A codexkey key has a name, a Premium or Cheap channel, an optional Premium fallback for Cheap, an expiry and usage statistics. The dashboard key API does not let you set per-key request limits and does not guarantee extra request capacity.
Getting Claude API access from Russia should not be a constant fight with VPNs, virtual cards and account bans. codexkey gives you a stable, fast and straightforward path: register, top up with SBP or crypto, and build. Your code changes by exactly two lines, base_url and api_key, and everything else stays the same.