TheRouter Deprecates /v1/anthropic/* Paths: Migrate to /v1/messages Before September 3, 2026
TheRouter's legacy /v1/anthropic/messages paths are deprecated and will be removed on September 3, 2026. The canonical path is /v1/messages — the same path official Anthropic SDKs use. Migration is a one-line base-URL change.
Archive item produced with AI assistance from the cited source and published without individual review. Editor of record: Joe Werner.

If you call TheRouter's Anthropic-format ingress at /v1/anthropic/messages or
/v1/anthropic/messages/count_tokens, you have a deadline: September 3,
2026. On that date the legacy paths are removed. The canonical paths —
/v1/messages and /v1/messages/count_tokens — are already live, behave
identically, and are not affected.
This is a path rename, not a behavior change. Same request format, same response format, same streaming, same billing, same API keys.
What changes, and when
| Date | What happens |
|---|---|
| Now | Every response on /v1/anthropic/* carries Deprecation: true and Sunset: Wed, 03 Sep 2026 00:00:00 GMT headers |
| August 19, 2026 | D-15 checkpoint — we contact tenants still sending successful traffic to the legacy paths |
| September 3, 2026 | Legacy paths removed; requests to /v1/anthropic/* return 404 |
The path mapping:
| Deprecated | Canonical |
|---|---|
POST /v1/anthropic/messages | POST /v1/messages |
POST /v1/anthropic/messages/count_tokens | POST /v1/messages/count_tokens |
Why /v1/messages
/v1/messages is the official Anthropic API path — it is what every official
Anthropic SDK appends to its base URL. The /v1/anthropic/ prefix was an early
TheRouter convention that official SDKs do not recognize, forcing manual URL
construction. Standardizing on the official path means pointing any Anthropic
SDK at TheRouter is a one-line change with zero path configuration.
How to migrate
If you use an Anthropic SDK, set the base URL to the TheRouter root — no path suffix at all:
from anthropic import Anthropic
client = Anthropic(
base_url="https://api.therouter.ai", # SDK appends /v1/messages itself
api_key="sk-tr-YOUR_KEY",
)
message = client.messages.create(
model="anthropic/claude-sonnet-4.5",
max_tokens=1024,
messages=[{"role": "user", "content": "Hello"}],
)
If you make raw HTTP calls, replace the path:
- POST https://api.therouter.ai/v1/anthropic/messages
+ POST https://api.therouter.ai/v1/messages
Both Authorization: Bearer and x-api-key authentication headers work on the
canonical path, exactly as before.
How to check whether you are affected
Inspect any response from your current integration. If it includes a
Deprecation: true header, you are calling a legacy path. If there is no such
header, you are already on the canonical path and nothing changes for you.
A quick check from the command line:
curl -si https://api.therouter.ai/v1/anthropic/messages \
-H "x-api-key: $THEROUTER_API_KEY" \
-H "Content-Type: application/json" \
-d '{"model":"anthropic/claude-sonnet-4.5","max_tokens":1,"messages":[{"role":"user","content":"ping"}]}' \
| grep -i -E "^(deprecation|sunset):"
What TheRouter users should do
- Search your code and configs for
/v1/anthropic. Any match — SDK base URLs, raw HTTP calls, environment variables, infrastructure-as-code — needs the one-line update before September 3. - Prefer the SDK base-URL form.
base_url="https://api.therouter.ai"is forward-compatible; hand-built paths are where migrations rot. - Don't wait for the D-15 contact. August 19 is when we start reaching out to tenants still on the legacy paths — being migrated before then means one less operational interruption on your side.

Claude Sonnet 5.5 Ships Five Breaking API Changes for Operators Running Sonnet 5
Claude Sonnet 5.5 (Sep 28) ships 5 breaking changes: forced tool use returns 400, `thinking:disabled` is rejected, thinking blocks are model-bound, `computer_20251124` is gone on the Claude API, and advisor pairings are now 5.x-only.

Claude Opus 5.5: Four Breaking API Changes and What They Mean for Your Routing Setup
Four breaking changes in Claude Opus 5.5: thinking can't be disabled, forced tool_choice returns 400, thinking blocks don't cross non-Fable/Mythos models, and computer_20251124 is gone. Each has a specific fix — three carry fallback routing implications the announcement skips.

OpenAI Retires Nine Audio and Realtime Model IDs by January 2027: The Migration Operators Must Complete
OpenAI deprecated nine legacy audio and realtime model IDs on July 20, shutdown January 20, 2027. The migration is a model-string swap — but operators routing gpt-4o-audio, gpt-4o-realtime, or gpt-audio families need a full routing audit before the deadline.