← Back to blog

Claude 4 Deprecation: 5 Things to Do This Weekend

Claude 4 Opus and Claude Sonnet 4 retire on June 15, 2026 — that's 10 days away. If you haven't started migrating yet, this weekend is your window. The good news: it takes about 2 hours total, and you'll save 67% on API costs.

--
Days Left
June 15
Deadline
~2hr
Total Time
67%
Cost Savings

The bottom line: This is a model name change, not a platform migration. Your API key, SDK, and endpoint stay the same. You're just updating a string in your code.

Why This Weekend Matters

After June 15, every API call to claude-4-opus and claude-sonnet-4 will return errors. If your app uses these models, it will break. But the fix is trivial — and the replacement models are actually better:

You're not downgrading. You're upgrading — and saving money doing it.

The 5 Things to Do This Weekend

1
Find Every Claude 4 Reference in Your Code
~10 min

Search your entire codebase for these model IDs:

# Search for Claude 4 model references
grep -r "claude-4-opus" . --include="*.py" --include="*.js" --include="*.ts" --include="*.json"
grep -r "claude-sonnet-4" . --include="*.py" --include="*.js" --include="*.ts" --include="*.json"

Check everywhere: source code, config files, environment variables, documentation, tests, and CI/CD pipelines. Don't forget .env files and deployment configs.

Pro tip: Also search for claude-4 as a substring — it catches any other Claude 4 variants you might have missed.

2
Update the Model Name Strings
~5 min

Replace each model reference. This is a find-and-replace operation:

Old Model IDNew Model IDPrice Change
claude-4-opus claude-opus-4-8 $15/$75 → $5/$25 (save 67%)
claude-sonnet-4 claude-sonnet-4-6 $3/$15 → $3/$15 (same price, 5x context)

That's it. No new SDK. No new API key. No new endpoint. Just a string change.

3
Test Your Integration
~30 min

Run your test suite with the new model names. Focus on:

  • API calls succeed (no 404 or 400 errors)
  • Response format is compatible (it should be — same Anthropic API)
  • Token limits work correctly (new models have larger context windows)
  • Streaming responses work if you use streaming

Good news: Claude Opus 4.8 and Claude Sonnet 4.6 use the same API format as Claude 4. If your code worked before, it will work now — just with a different model name.

4
Calculate Your New Costs
~10 min

Use the APIpulse calculator to see exactly how much you'll save with the new models:

For most users, the savings are significant:

Monthly UsageClaude 4 Opus CostClaude Opus 4.8 CostSavings
1M input + 500K output tokens $52.50 $17.50 $35.00/mo (67%)
10M input + 5M output tokens $525.00 $175.00 $350.00/mo (67%)
100M input + 50M output tokens $5,250.00 $1,750.00 $3,500.00/mo (67%)
5
Deploy and Monitor
~30 min

Push your changes to production. Then monitor for 24 hours:

  • Check error rates — should be zero new errors
  • Check response times — should be similar or better
  • Check your API dashboard — confirm the new model names appear
  • Check costs — confirm the lower pricing kicks in

Rollback plan: If something goes wrong, you can switch back instantly — just change the model name back. But do this before June 15, because after that the old model IDs stop working entirely.

What If You Want to Switch Providers Entirely?

The steps above keep you on Anthropic. But if you want to explore cheaper alternatives, here are the best options:

AlternativePrice (In/Out per M)Savings vs Claude 4 OpusBest For
DeepSeek V4 Pro $0.435 / $0.87 97% cheaper Cost-sensitive, code, analysis
Gemini 2.5 Pro $1.25 / $10.00 92% cheaper Long context, multimodal
GPT-5 $1.25 / $10.00 87% cheaper General purpose, function calling
Claude Opus 4.8 $5.00 / $25.00 67% cheaper Drop-in replacement, best quality

Use the Migration Tool to compare all 34 alternatives side by side with your exact usage.

Quick FAQ

Will my API key stop working?

No. Your Anthropic API key works with all Anthropic models, including the new ones. You don't need a new key.

Do I need to update my SDK?

No. The Anthropic SDK works with all Claude models. Just change the model name string.

What if I'm using a third-party proxy (OpenRouter, LiteLLM, etc.)?

Check your proxy's documentation — they may handle the model mapping automatically. If not, update the model name in your proxy config.

Can I keep using Claude 4 after June 15?

No. The model IDs will be retired and return errors. There's no extended support or grace period.

What about Claude 4 Opus on claude.ai (the web interface)?

This deprecation only affects the API. The claude.ai web interface manages its own model availability separately.

Ready to migrate?

Calculate your exact savings and get the code changes you need.

Deprecation Calculator → Migration Tool →

Related Resources