Claude Code and Codex
used from Germany and the DACH region
Anthropic's supported-regions page lists Germany, Austria and Switzerland. The friction for DACH teams is rarely availability — it is the card and knowing which switch redirects which CLI. Both switches are documented: ANTHROPIC_BASE_URL for Claude Code, a profile in config.toml for Codex.
Updated 2026-10-07
Point this tool at the QCode endpoint — one key for Claude, GPT and Chinese models.
- Billed per token — live rates on /models
- Pay by card (Visa / Mastercard / AMEX), Apple Pay, Google Pay or crypto
- Self-service: top up and activate instantly
Four things to confirm before you configure
DACH countries listed
Germany, Austria and Switzerland all appear on the published list of regions where Anthropic offers commercial API access.
Claude Code switch
Claude Code's own environment-variable reference describes ANTHROPIC_BASE_URL as overriding the API endpoint to route requests through a proxy or gateway.
Documented as supported
QCode's tooling page states it currently supports Claude Code and Codex CLI, and that Cursor is not supported because it does not allow configuring third-party API endpoints.
How DACH accounts top up
An international card (Visa / Mastercard / AMEX), Apple Pay, Google Pay, WeChat Pay, crypto across 18+ networks, or — for a company — a corporate bank transfer.
What this page is about
Two tools, two switches, one account behind them. Claude Code is a terminal CLI whose endpoint is redirected with an environment variable; Codex is a terminal CLI configured through a file. For a team in Germany the deciding question is not which CLI feels nicer, but what has to be true for the money and the endpoint to still work in six months.
What DACH teams actually ask
Two questions come up most often: whether the vendor serves the country at all, and how a German account pays. The first is answered by a published list; the second depends on the card and the acquirer — so the two paths are kept apart here.
Order of operations
Confirm the country is on the vendor's published list, then confirm which channel your bank actually clears.
Claude Code is one environment variable; Codex is one profile in config.toml. Do not describe both as one change in a ticket.
Test with a small top-up and keep the balance in one currency before a larger purchase.
Confirmed vs. not documented
Backed by published sources
Anthropic publishes the countries, regions and territories where it currently offers commercial API access, and Germany, Austria and Switzerland are on that list. Claude Code's reference documents ANTHROPIC_BASE_URL as routing requests through a proxy or gateway. Codex documents AGENTS.md as extra project instructions. On the QCode side: international Visa / Mastercard / AMEX cards plus Apple Pay, Google Pay, WeChat Pay and Alipay, crypto across 18+ networks, and the explicit statement that Claude Code and Codex CLI are supported while Cursor is not, because Cursor does not allow configuring third-party API endpoints.
Not documented — verify yourself
QCode publishes an access node in Los Angeles, US — us.qcode.cc — serving North America and Europe. Nothing we could find documents a node located in Europe, SEPA direct debit, prices in euro, German-language vendor documentation, or any latency figure for Germany. Unverified as well: whether your specific card clears today. Treat each of those as an open question and re-check the source pages before relying on them.
Two setup shapes, one account
Claude Code: one environment variable
Claude Code reads its endpoint from ANTHROPIC_BASE_URL, described in its own reference as overriding the API endpoint to route requests through a proxy or gateway. One variable and one key; the CLI then behaves as it did against the first-party host.
Codex: one config.toml profile
Codex is configured through a profile in ~/.codex/config.toml, so endpoint and key live in a file rather than in the shell. QCode publishes a Codex quick-start for that profile, and a ChatGPT sign-in is untouched if you keep both paths.
What to change, in order
Step 1 — create the account and note the key. Step 2 — Claude Code: export ANTHROPIC_BASE_URL and the key variable, start the CLI, confirm it addresses the host you set. Step 3 — Codex: add the provider and profile to ~/.codex/config.toml and switch with /model. Step 4 — top up through whichever channel your bank clears, starting with a small amount.
On QCode
QCode's endpoint documentation states: Claude uses the Anthropic endpoint https://api.qcode.cc/api (the value for Claude Code's ANTHROPIC_BASE_URL), GPT, GLM, Kimi, DeepSeek and Qwen use the OpenAI-compatible endpoint https://api.qcode.cc/openai/v1, and Codex CLI's base_url is https://api.qcode.cc/openai; Claude models cannot use the OpenAI-compatible endpoint. Which ids are callable is the live /models list. Billing is per token, with each model's unit price on /models; CNY and USD balances are tracked separately and do not mix.
FAQ
Are Claude and Codex available from Germany at all?
Anthropic's supported-regions page lists the countries where it offers commercial API access, and Germany, Austria and Switzerland are on it. That answers availability, not billing: whether a specific card clears is decided by the issuer and the acquirer at the moment of the charge.
What exactly do I change to redirect each CLI?
Claude Code: set ANTHROPIC_BASE_URL plus your key, and the CLI talks to that host instead. Codex: add a provider and profile in ~/.codex/config.toml. Both are documented switches, and neither requires code changes.
Is any of this documented in German?
The official Claude Code documentation is in English. On the QCode side, the site is configured for five languages — zh, en, ja, ru and de — and this guide is written in all five.
How do I pay with a German card, or as a German company?
For a personal account: an international card (Visa / Mastercard / AMEX), Apple Pay, Google Pay, WeChat Pay or crypto. For a company the documented path is a corporate bank transfer.
Is there an EU endpoint, and what about latency from Germany?
QCode documents proxies in Asia-Pacific (Hong Kong / Japan) for access from China, and an access node in Los Angeles, US — us.qcode.cc — serving North America and Europe. No latency figure for Germany is published, so this page makes no latency claim — measure it against your own traffic.
Does Cursor work with the same key?
No. QCode's tooling page states Cursor is not supported because it does not allow configuring third-party API endpoints. Editors that do expose an OpenAI-compatible base URL are a different case; for that shape the site documents Zed, Warp and JetBrains AI Assistant.
Sources
Anthropic's supported-regions page plus the Claude Code environment-variable and project-memory references (fetched 2026-10-01); OpenAI's Codex CLI and AGENTS.md documentation (fetched the same day). QCode-side statements come from QCode's own pages: the tooling-comparison note, the payment page and the pricing page. Where a source is silent, this page says so.
Run Claude Code and Codex from Germany
One account, one key, both CLIs — with the endpoint values written down so your ops team can review them.
Related reading
Anthropic base URL setup guide
The exact variable and the scopes of the settings files.
Codex CLI complete guide
Codex from installation through config.toml.
QCode pricing guide
How balance, service rate and plan tiers fit together.
Vendor availability, prices and payment channels change. Every claim on this page names its source; where they disagree, the vendor pages and QCode's checkout govern.