Claude Code setup guide
Model IDs per plan, two-variable setup, and how to handle 429 caps.
Your terminal stops mid-session with API Error: 400 Identity verification is required, or your browser redirects to portal.anthropic.com for a physical ID and live selfie. With the updated Supported Regions Policy taking effect on November 12, this Persona-backed check is driving a much stricter enforcement wave.
You are halfway through a refactor when Claude Code stops and prints a red error in your terminal:
API Error: 400 Identity verification is required to continueOr you open claude.ai to upgrade to Claude Pro or Max and your browser redirects to portal.anthropic.com, asking you to complete an identity check within minutes.
The short version: Verification Portal is not a routine CAPTCHA. It is a mandatory compliance check handled by Persona Identities. In the first half of 2026, Anthropic banned 11.4 million accounts and overturned only about 10.5% of appeals. If your daily work depends on Claude Code, the real fix is decoupling your workflow from personal account risk controls rather than trying to game the check.
Anthropic's enforcement focus has shifted sharply from basic bot filtering to regional compliance, anti-reselling, and anti-distillation. Data from the Anthropic Transparency Hub shows how steep the jump is:
| Reporting period | Banned accounts | Appeals received | Appeals overturned |
|---|---|---|---|
| H2 2025 | 1.45M | — | ~3.3% |
| H1 2026 (Jan–Jun) | 11.4M | 398,000 | 42,000 (~10.5%) |
Ban volume multiplied nearly eightfold in six months. Then, announced on October 8 and taking full effect on November 12, Anthropic raised the bar again with an updated Usage Policy and Supported Regions Policy:
The Permissions-Policy header on portal.anthropic.com explicitly grants camera access to withpersona.com (inquiry.withpersona.com, verify.withpersona.com). Anthropic outsources the entire verification flow to Persona Identities, a San Francisco-based KYC provider.
Based on Anthropic's support documentation and developer reports, five signals commonly trigger the prompt:
Once you enter Verification Portal, the requirements are much stricter than phone verification:
Anthropic's documentation states that verification data is used strictly for identity confirmation, fraud prevention, and compliance, not model training. However, Persona collects and processes the raw images and biometric data, and Anthropic retains access to records for appeals and compliance reviews.
Across r/ClaudeAI, r/ClaudeCode, and tech press reports, the loudest complaint is not the check itself, but getting banned right after completing it.
Three failure modes come up repeatedly:
API Error: 400 Identity verification is required—even after running claude logout, deleting ~/.claude/credentials.json, and logging back in.From Anthropic's perspective, cracking down on account farms, regional arbitrage, and unauthorized distillation makes sense. For working developers, though, an automated pipeline with a ~10.5% appeal overturn rate turns a personal subscription into a fragile single point of failure.
Once API Error: 400 Identity verification is required shows up, you have three practical options:
claude logout, clear ~/.claude/credentials.json, and claude login again. If the account is already suspended, expect roughly a one-in-ten chance on appeal.ANTHROPIC_BASE_URL and ANTHROPIC_AUTH_TOKEN. Pointing it at a provider that does not tie your CLI to a consumer subscription removes Persona KYC and personal account ban waves from your daily workflow.| Comparison | Personal Claude Pro / Max | CodingPass (Go / Plus / Pro) |
|---|---|---|
| Personal Anthropic account | Required | Not required |
| Verification Portal / Persona KYC | Enforced when risk flags trigger | Never triggered |
| Pricing and caps | Dynamic black-box limits; third-party apps use extra usage | Metered at official API rates; public monthly, weekly, and 5-hour caps |
| Over-limit handling | Can trigger abuse flags or extra charges | Blocked before upstream with HTTP 429; no surprise bills |
| Tool compatibility | Official Claude Code / claude.ai | Native support for Claude Code, OpenCode, and Codex |
With CodingPass, all traffic runs through compliant enterprise API channels—no personal Anthropic account, no passport upload, and no live selfie. CodingPass Go costs $10 a month with a $60 monthly allowance that works directly with Claude Sonnet 5.5 (Plus and Pro add Opus 5.5 and Fable 5.2). Input, output, and cache reads are metered at official API rates, every 5-hour window and weekly cap is listed on Usage Limits, and hitting a cap returns HTTP 429 with the exact reset time instead of charging extra.
Switching takes two minutes and keeps your existing workflow intact:
Create a key: Pick a plan in CodingPass, open Dashboard → Keys → New key, and copy your cp-live- key.
Set two environment variables in ~/.zshrc or ~/.bashrc and open a new terminal:
export ANTHROPIC_BASE_URL="https://codingpass.ai"export ANTHROPIC_AUTH_TOKEN="cp-live-…"Run Claude Code as usual:
claude --model claude-sonnet-5-5Even if your personal account still works today, keeping CodingPass configured as a fallback lets you swap one line and keep shipping if Verification Portal ever pops up mid-sprint.
Point Claude Code at CodingPass. No personal Anthropic account, no Verification Portal. Two env vars, transparent metering, cancel anytime.