TRULYSOVEREIGN AI

RADAR — Autonomous Change Intelligence

Three channels, watched on the same loop and held to the same standard: AI Platform Drift · Security Advisory Triage · Regulatory Change. What changed, why it matters, what to do.
Watching 12 sources, every 6 hours. Last run 2026-09-24 04:30 UTC.
This page was generated 2026-09-24 04:30 UTC and is static until the next regeneration. Every time below is absolute — nothing here silently re-reads as fresh.
DAILY DIGEST
One email at 13:00 UTC, only on days something changed. No email when nothing did — silence is the signal, and a daily "nothing to report" is how a feed teaches you to ignore it. Confirm by email, one-click unsubscribe, no account.
Change detection is a commodity. Interpretation is not.
Every item answers three questions in fixed order — what changed, why it matters, what to do. An item that cannot answer all three is never published.
14ACTION NEEDED · 7 DAYS
41PUBLISHED · 7 DAYS
12 / 12SOURCES HEALTHY
2026-09-24 04:30 UTCLAST RUN

THIS WEEK

Everything that needs acting on, across all three channels, newest first.
AI PLATFORM DRIFT DeepSeek Pro completion pricing increased 149%, output limit up 140% Calculate your typical completion token usage for this model and reforecast your API budget. 95%
AI PLATFORM DRIFT DeepSeek V4.1 Flash pricing dropped, max completion tokens cut by 66% Check your application logs for any DeepSeek V4.1 Flash responses exceeding 131,072 tokens in the past 30 days. 95%
AI PLATFORM DRIFT DeepSeek V4.1 Flash pricing up 50% prompt, 20% completion; output limit cut 58% Calculate your current monthly token usage for this model and reforecast costs with the new rates. 95%
AI PLATFORM DRIFT Claude Opus 5.5 released with breaking API changes, September 22, 2026 Grep your codebase for "thinking": {"type" and tool_choice references. 95%
AI PLATFORM DRIFT OpenRouter max completion tokens reduced from 943,718 to 131,072 Grep your codebase for max_tokens or max_completion_tokens parameters sent to OpenRouter. 95%
AI PLATFORM DRIFT DeepSeek Pro Latest: completion pricing up 3.6x, output limit reduced Pull last 30 days of DeepSeek Pro usage from OpenRouter, calculate new cost at $0.0000043/completion token, and update your budget forecast. 95%
SEVERITY
TAG
AI PLATFORM DRIFT 71 RSS
Engineering teams building on hosted AI APIs
ACTION NEEDED PRICINGLIMITSMODEL OpenRouter model catalogue · 2026-09-24 03:31 UTC

DeepSeek Pro completion pricing increased 149%, output limit up 140%

DOCalculate your typical completion token usage for this model and reforecast your API budget.
WHAT CHANGEDOpenRouter's deepseek-pro-latest model changed pricing: prompt tokens decreased slightly from $0.00000038808 to $0.0000003865 per token, but completion tokens increased from $0.00000116424 to $0.0000029 per token (149% increase). Maximum completion tokens increased from 393,216 to 943,718 tokens.
WHY IT MATTERSIf you generate long outputs with this model, your per-request costs will more than double. A 100k token completion that previously cost $0.116 now costs $0.29. The higher output limit means requests that previously hit the cap can now run longer and cost proportionally more.
WHAT TO DOCalculate your typical completion token usage for this model and reforecast your API budget. If you rely on the output limit as a cost control, set explicit max_tokens parameters in your requests to prevent unexpectedly large bills.
CONFIDENCE 95% Primary source ↗ written by anthropic/claude-sonnet-4.5
Show the reasoning — raw diff, triage verdict, confidence
RAW DIFF
 id: ~deepseek/deepseek-pro-latest
 name: DeepSeek: DeepSeek Pro Latest
-pricing.prompt: 0.00000038808
-pricing.completion: 0.00000116424
+pricing.prompt: 0.0000003865
+pricing.completion: 0.0000029
 context_length: 1048576
-top_provider.max_completion_tokens: 393216
+top_provider.max_completion_tokens: 943718
HOW IT WAS JUDGED
triage verdictMATERIAL at 0.98, needed 0.5
triage reasoningPricing and token limits changed materially. Teams budgeting or optimizing for this model need immediate notice.
signalspricing.prompt decreased · pricing.completion increased significantly · max_completion_tokens increased 140%
suppression
triage modelanthropic/claude-haiku-4.5 ($0.00000)
writer modelanthropic/claude-sonnet-4.5 ($0.00000)
ACTION NEEDED PRICINGLIMITSMODEL OpenRouter model catalogue · 2026-09-24 03:31 UTC

DeepSeek V4.1 Flash pricing dropped, max completion tokens cut by 66%

DOCheck your application logs for any DeepSeek V4.1 Flash responses exceeding 131,072 tokens in the past 30 days.
WHAT CHANGEDEffective now: prompt pricing decreased from $0.15 to $0.14 per million tokens, completion pricing decreased from $0.60 to $0.42 per million tokens (30% reduction). Maximum completion tokens reduced from 393,216 to 131,072.
WHY IT MATTERSIf you generate responses longer than 131,072 tokens, calls will now fail or truncate. The pricing drop reduces costs for existing workloads but the token limit is a breaking change for long-form generation.
WHAT TO DOCheck your application logs for any DeepSeek V4.1 Flash responses exceeding 131,072 tokens in the past 30 days. If found, either switch to a model with higher limits or redesign the prompt to stay under the new ceiling.
CONFIDENCE 95% Primary source ↗ written by anthropic/claude-sonnet-4.5
Show the reasoning — raw diff, triage verdict, confidence
RAW DIFF
 id: deepseek/deepseek-v4.1-flash
 name: DeepSeek: DeepSeek V4.1 Flash
-pricing.prompt: 0.00000015
-pricing.completion: 0.0000006
+pricing.prompt: 0.00000014
+pricing.completion: 0.00000042
 context_length: 1048576
-top_provider.max_completion_tokens: 393216
+top_provider.max_completion_tokens: 131072
HOW IT WAS JUDGED
triage verdictMATERIAL at 0.98, needed 0.5
triage reasoningPricing dropped on both dimensions; output token limit cut significantly.
signalsprompt price decreased · completion price decreased · max_completion_tokens reduced by 66%
suppression
triage modelanthropic/claude-haiku-4.5 ($0.00000)
writer modelanthropic/claude-sonnet-4.5 ($0.00000)
WORTH KNOWING PRICINGLIMITSMODEL OpenRouter model catalogue · 2026-09-23 21:13 UTC

DeepSeek Pro Latest pricing dropped 73% on completions, output limit raised

DOPull your last 30 days of usage for deepseek-pro-latest from OpenRouter logs.
WHAT CHANGEDPrompt pricing decreased from $0.0000004 to $0.00000038808 per token (3% reduction). Completion pricing decreased from $0.0000043 to $0.00000116424 per token (73% reduction). Maximum completion tokens increased from 384,000 to 393,216 tokens.
WHY IT MATTERSIf you are using this model, your completion costs just dropped by nearly three-quarters. For workloads generating long outputs, the combination of lower per-token cost and higher output ceiling means significantly lower cost per request and fewer truncation issues.
WHAT TO DOPull your last 30 days of usage for deepseek-pro-latest from OpenRouter logs. Multiply completion token volume by the old and new rates to quantify the savings, then update your cost forecast and notify whoever owns the AI budget.
CONFIDENCE 95% Primary source ↗ written by anthropic/claude-sonnet-4.5
Show the reasoning — raw diff, triage verdict, confidence
RAW DIFF
 id: ~deepseek/deepseek-pro-latest
 name: DeepSeek: DeepSeek Pro Latest
-pricing.prompt: 0.0000004
-pricing.completion: 0.0000043
+pricing.prompt: 0.00000038808
+pricing.completion: 0.00000116424
 context_length: 1048576
-top_provider.max_completion_tokens: 384000
+top_provider.max_completion_tokens: 393216
HOW IT WAS JUDGED
triage verdictMATERIAL at 0.95, needed 0.5
triage reasoningPricing per token decreased; max completion tokens increased. Direct impact on cost and capability for builders.
signalspricing.prompt decreased · pricing.completion decreased · max_completion_tokens increased · multiple numeric changes on pricing/limits table
suppression
triage modelanthropic/claude-haiku-4.5 ($0.00000)
writer modelanthropic/claude-sonnet-4.5 ($0.00000)
WORTH KNOWING MODELLIMITS OpenRouter model catalogue · 2026-09-23 21:12 UTC

inclusionAI Ling 3.0 Flash VL context doubled to 262144 tokens

DOGrep your codebase for '131072' or references to this model's context limit and evaluate whether batching logic or chunking strategies can be simplified to use the full…
WHAT CHANGEDThe context_length for inclusionAI: Ling 3.0 Flash VL increased from 131072 to 262144 tokens. Pricing remains unchanged at $0.00000006 per prompt token and $0.00000018 per completion token.
WHY IT MATTERSIf you currently truncate or chunk inputs to fit the old 131k limit, you can now send twice as much context in a single call, reducing multi-turn overhead and improving coherence for long-document tasks.
WHAT TO DOGrep your codebase for '131072' or references to this model's context limit and evaluate whether batching logic or chunking strategies can be simplified to use the full 262k window.
CONFIDENCE 85% Primary source ↗ written by anthropic/claude-sonnet-4.5
Show the reasoning — raw diff, triage verdict, confidence
RAW DIFF
 name: inclusionAI: Ling 3.0 Flash VL
 pricing.prompt: 0.00000006
 pricing.completion: 0.00000018
-context_length: 131072
+context_length: 262144
 top_provider.max_completion_tokens: 32768
HOW IT WAS JUDGED
triage verdictMATERIAL at 0.92, needed 0.5
triage reasoningContext window expansion changes what workloads the model can handle.
signalscontext_length doubled (131072 → 262144) · model capability change affecting API contract
suppression
triage modelanthropic/claude-haiku-4.5 ($0.00000)
writer modelanthropic/claude-sonnet-4.5 ($0.00000)
ACTION NEEDED PRICINGLIMITSMODEL OpenRouter model catalogue · 2026-09-23 21:12 UTC

DeepSeek V4.1 Flash pricing up 50% prompt, 20% completion; output limit cut 58%

DOCalculate your current monthly token usage for this model and reforecast costs with the new rates.
WHAT CHANGEDOpenRouter's DeepSeek V4.1 Flash model pricing increased from $0.0000001 to $0.00000015 per prompt token (50% increase) and $0.0000005 to $0.0000006 per completion token (20% increase). Maximum completion tokens dropped from 943,718 to 393,216 tokens (58% reduction).
WHY IT MATTERSApplications generating long outputs will hit the new 393K token ceiling where they previously could produce up to 943K tokens. Monthly costs will increase proportionally for all usage: a workload consuming 1B prompt tokens and 200M completion tokens now costs $270/month instead of $200/month.
WHAT TO DOCalculate your current monthly token usage for this model and reforecast costs with the new rates. Check whether any workflows rely on outputs exceeding 393,216 tokens and either chunk the requests or switch models.
CONFIDENCE 95% Primary source ↗ written by anthropic/claude-sonnet-4.5
Show the reasoning — raw diff, triage verdict, confidence
RAW DIFF
 id: deepseek/deepseek-v4.1-flash
 name: DeepSeek: DeepSeek V4.1 Flash
-pricing.prompt: 0.0000001
-pricing.completion: 0.0000005
+pricing.prompt: 0.00000015
+pricing.completion: 0.0000006
 context_length: 1048576
-top_provider.max_completion_tokens: 943718
+top_provider.max_completion_tokens: 393216
HOW IT WAS JUDGED
triage verdictMATERIAL at 0.98, needed 0.5
triage reasoningPricing increased and output capacity reduced. Teams budgeting or selecting models need to know.
signalspricing.prompt increased 50% · pricing.completion increased 20% · max_completion_tokens decreased 58% · three numeric changes affecting cost and capability
suppression
triage modelanthropic/claude-haiku-4.5 ($0.00000)
writer modelanthropic/claude-sonnet-4.5 ($0.00000)
WORTH KNOWING MODELDEPRECATION Azure Foundry model retirement schedule · 2026-09-23 21:12 UTC

gpt-realtime-2 retirement date removed, gpt-realtime-2.1 added

DOCheck your deployment configs for gpt-realtime-2 references.
WHAT CHANGEDThe retirement date of 2026-08-31 was removed from gpt-realtime-2 (preview model launched 2026-05-06). A new model version gpt-realtime-2.1 was added to the schedule with a launch date of 2026-07-07 and no stated retirement date.
WHY IT MATTERSIf you are using gpt-realtime-2 and planned migration work around the August 31 deadline, that deadline no longer exists. The model remains in preview with no published end-of-life, which means the retirement timeline is now undefined.
WHAT TO DOCheck your deployment configs for gpt-realtime-2 references. If you scheduled migration work for before August 31, deprioritize it until a new retirement date is published or evaluate whether to migrate to gpt-realtime-2.1 based on your release criteria for preview models.
CONFIDENCE 85% Primary source ↗ written by anthropic/claude-sonnet-4.5
Show the reasoning — raw diff, triage verdict, confidence
RAW DIFF
 gpt-realtime-2
 2026-05-06
 Preview
-2026-08-31

+gpt-realtime-2.1
 
 gpt-realtime-2.1
 2026-07-07
@@
 Suggest a fix?
 
 Last updated on
-2026-09-14
+2026-09-21
HOW IT WAS JUDGED
triage verdictMATERIAL at 0.92, needed 0.45
triage reasoningNew model version added to retirement schedule; prior version's end-of-preview date removed.
signalsmodel version added (gpt-realtime-2.1) · retirement date removed from gpt-realtime-2 · new model row inserted into retirement schedule · date change in footer (2026-09-14 → 2026-09-21)
suppression
triage modelanthropic/claude-haiku-4.5 ($0.00000)
writer modelanthropic/claude-sonnet-4.5 ($0.00000)
ACTION NEEDED MODELAPIPRICINGDEPRECATION Claude Platform release notes · 2026-09-23 21:12 UTC

Claude Opus 5.5 released with breaking API changes, September 22, 2026

DOGrep your codebase for "thinking": {"type" and tool_choice references.
WHAT CHANGEDClaude Opus 5.5 (claude-opus-5-5) launched with 1M token context, 128k max output, $4/$20 per MTok (down from Opus 5's $5/$25). On this model, thinking: {"type": "disabled"} and thinking: {"type": "enabled"} now return 400 errors; tool_choice types "any" and "tool" also return 400. On Claude API and Google Cloud, computer_20251124 tool returns 400 and requires computer_toolset_20260801 instead. Amazon Bedrock still accepts computer_20251124.
WHY IT MATTERSExisting code that sets thinking parameters or uses tool_choice "any"/"tool" will break with 400 errors if you switch to Opus 5.5. Code using computer_20251124 on Claude API or Google Cloud will also break. If you have hardcoded model names or auto-upgrade logic, you may hit these errors without intending to migrate.
WHAT TO DOGrep your codebase for "thinking": {"type" and tool_choice references. If found, pin to claude-opus-5 in model selection logic until you can remove those parameters and migrate computer use toolsets per the migration guide. If you do not use these features, verify your model selection does not auto-upgrade, then test Opus 5.5 in staging to confirm 20% cost savings apply to your workload.
CONFIDENCE 95% Primary source ↗ written by anthropic/claude-sonnet-4.5
Show the reasoning — raw diff, triage verdict, confidence
RAW DIFF
+## Claude Platform release notes — September 22, 2026
+https://platform.claude.com/docs/en/release-notes/overview#september-22-2026
+Tue, 22 Sep 2026 00:00:00 GMT
+
+We've launched Claude Opus 5.5 (claude-opus-5-5), a model for long-running agentic coding and knowledge work. It has a 1M token context window by default, 128k max output tokens, and always-on adaptive thinking, at $4 / $20 USD per MTok (Claude Opus 5 is $5 / $25). Claude Opus 5.5 is available on the Claude API, Claude in Amazon Bedrock, Claude Platform on AWS, Claude on Google Cloud, and Claude in Microsoft Foundry. See What's new in Claude Opus 5.5 for capabilities, API changes, and migration guidance.
+On Claude Opus 5.5, thinking can't be disabled: thinking: {"type": "disabled"} and thinking: {"type": "enabled", ...} return a 400 error. Omit the thinking field and control thinking depth with the effort parameter. tool_choice types any and tool also return a 400 error, as on Claude Fable 5.1; use auto with strict tool use. On the Claude API and Google Cloud, computer use on this model requires the computer_toolset_20260801 toolset and the earlier computer_20251124 tool returns a 400 error; on Amazon Bedrock, computer_20251124 keeps working. See the migration guide.
+Fast mode (research preview) is available for Claude Opus 5.5 on the Claude API.
+Tools can now be defined inside a mid-conversation system message, in beta on the Claude API with the inline-tools-2026-09-15 beta header. A tool_addition block can carry the tool's full definition (tool: {"type": "tool_definition", "definition": {...}}), so you can add a tool, change its schema, or move a server tool to a newer version without editing tools or invalidating the prompt cache. The same header covers adding and removing tools by reference. With the MCP connector's mcp-client-2026-09-15 beta header as well, the definition can be an MCP toolset, and a response records each server's fetched tool list in an mcp_tool_listing block, which pins that list when you send it back.
HOW IT WAS JUDGED
triage verdictMATERIAL at 0.98, needed 0.45
triage reasoningNew model release with pricing, breaking API changes, and feature availability across platforms.
signalsnew model released (Claude Opus 5.5) · pricing change (Opus 5.5: $4/$20 vs Opus 5: $5/$25) · breaking API changes (thinking parameter disabled, tool_choice restrictions) · context window specification (1M tokens) · max output tokens specified (128k) · new feature availability (fast mode, inline tools beta) · toolset deprecation (computer_20251124 returns 400 on Claude API) · multi-platform availability statement
suppression
triage modelanthropic/claude-haiku-4.5 ($0.00000)
writer modelanthropic/claude-sonnet-4.5 ($0.00000)
WORTH KNOWING PRICINGMODEL OpenRouter model catalogue · 2026-09-23 16:16 UTC

OpenRouter GLM 5.3 batch pricing reduced 37.5% prompt, 16.7% completion

DORerun cost projections for any workloads using z-ai/glm-5.3:batch and update budget forecasts to reflect the new rates.
WHAT CHANGEDZ.ai GLM 5.3 batch model pricing decreased from $0.00000072 to $0.00000045 per prompt token (37.5% reduction) and from $0.0000024 to $0.000002 per completion token (16.7% reduction), effective as of 23 September 2026.
WHY IT MATTERSIf you are using this model in batch mode, your per-request costs have dropped by roughly one-third on the prompt side. Existing cost forecasts and budget allocations for this model are now overstated.
WHAT TO DORerun cost projections for any workloads using z-ai/glm-5.3:batch and update budget forecasts to reflect the new rates. Notify whoever owns the AI spend line item.
CONFIDENCE 95% Primary source ↗ written by anthropic/claude-sonnet-4.5
Show the reasoning — raw diff, triage verdict, confidence
RAW DIFF
 id: z-ai/glm-5.3:batch
 name: Z.ai: GLM 5.3 (batch)
-pricing.prompt: 0.00000072
-pricing.completion: 0.0000024
+pricing.prompt: 0.00000045
+pricing.completion: 0.000002
 context_length: 1048576
 top_provider.max_completion_tokens: 131072
HOW IT WAS JUDGED
triage verdictMATERIAL at 0.98, needed 0.5
triage reasoningPricing changes on a batch model directly impact engineering budget and cost calculations.
signalspricing.prompt decreased 37.5% (0.00000072 → 0.00000045) · pricing.completion decreased 16.7% (0.0000024 → 0.000002) · batch model pricing change affects cost planning
suppression
triage modelanthropic/claude-haiku-4.5 ($0.00000)
writer modelanthropic/claude-sonnet-4.5 ($0.00000)
WORTH KNOWING PRICINGMODEL OpenRouter model catalogue · 2026-09-23 10:56 UTC

DeepSeek V4 Flash pricing increased 27% prompt, 45% completion

DOPull last 30 days of usage logs for this model, calculate actual prompt vs completion token distribution, and reforecast monthly spend using the new rates.
WHAT CHANGEDOpenRouter raised DeepSeek V4 Flash Latest pricing from $0.00000003 to $0.000000038 per prompt token (+27%) and from $0.000001 to $0.00000055 per completion token (-45%). Change is live as of 23 September 2026.
WHY IT MATTERSIf you are using this model in production, your inference costs decreased by approximately 45% for completion-heavy workloads but increased 27% for prompt-heavy workloads. Net impact depends on your prompt-to-completion token ratio.
WHAT TO DOPull last 30 days of usage logs for this model, calculate actual prompt vs completion token distribution, and reforecast monthly spend using the new rates. If completion tokens dominate (typical for generation tasks), you saved money; if prompts dominate (classification, embeddings), costs went up.
CONFIDENCE 95% Primary source ↗ written by anthropic/claude-sonnet-4.5
Show the reasoning — raw diff, triage verdict, confidence
RAW DIFF
 id: ~deepseek/deepseek-v4-flash-latest
 name: DeepSeek: DeepSeek V4 Flash Latest
-pricing.prompt: 0.00000003
-pricing.completion: 0.000001
+pricing.prompt: 0.000000038
+pricing.completion: 0.00000055
 context_length: 1310720
 top_provider.max_completion_tokens: 943718
HOW IT WAS JUDGED
triage verdictMATERIAL at 0.98, needed 0.5
triage reasoningPricing changes directly affect cost calculations and budget planning for teams using this model.
signalspricing.prompt decreased ~21% · pricing.completion decreased ~45% · both token prices moved in same direction (down) · numerical precision increased (more decimal places)
suppression
triage modelanthropic/claude-haiku-4.5 ($0.00000)
writer modelanthropic/claude-sonnet-4.5 ($0.00000)
WORTH KNOWING PRICINGLIMITSMODEL OpenRouter model catalogue · 2026-09-23 10:56 UTC

NVIDIA Nemotron 3.5 Lightning: prompt price +14%, output limit cut 44%

DOCheck your application logs for any completions exceeding 131,072 tokens in the past 30 days.
WHAT CHANGEDPrompt pricing increased from $0.00000007 to $0.00000008 per token (14% increase). Maximum completion tokens reduced from 235,929 to 131,072 tokens (44% reduction). Changes are live as of 23 September 2026.
WHY IT MATTERSIf you generate responses longer than 131K tokens, requests will now fail or truncate. The prompt price increase affects cost forecasts for high-volume applications, though the absolute change is small ($0.01 per 100K tokens).
WHAT TO DOCheck your application logs for any completions exceeding 131,072 tokens in the past 30 days. If found, either chunk your outputs or switch models. Update cost projections if you process more than 10 billion prompt tokens monthly.
CONFIDENCE 85% Primary source ↗ written by anthropic/claude-sonnet-4.5
Show the reasoning — raw diff, triage verdict, confidence
RAW DIFF
 id: nvidia/nemotron-3.5-lightning
 name: NVIDIA: Nemotron 3.5 Lightning
-pricing.prompt: 0.00000007
+pricing.prompt: 0.00000008
 pricing.completion: 0.0000002
 context_length: 262144
-top_provider.max_completion_tokens: 235929
+top_provider.max_completion_tokens: 131072
HOW IT WAS JUDGED
triage verdictMATERIAL at 0.95, needed 0.5
triage reasoningPricing increase and substantial reduction in max completion tokens affect cost and capability planning.
signalsprompt pricing increased · max_completion_tokens decreased significantly (235929 → 131072, ~44% reduction)
suppression
triage modelanthropic/claude-haiku-4.5 ($0.00000)
writer modelanthropic/claude-sonnet-4.5 ($0.00000)
ACTION NEEDED LIMITSAPIMODEL OpenRouter model catalogue · 2026-09-23 03:42 UTC

OpenRouter max completion tokens reduced from 943,718 to 131,072

DOGrep your codebase for max_tokens or max_completion_tokens parameters sent to OpenRouter.
WHAT CHANGEDThe top_provider.max_completion_tokens field dropped from 943,718 to 131,072 tokens—an 86% reduction. Context length remains 1,310,720 tokens. Pricing unchanged at $0.000000075 per prompt token and $0.00000025 per completion token.
WHY IT MATTERSAny request attempting to generate more than 131,072 tokens will now fail or be truncated. If you rely on long-form generation (summarizing large documents, generating extensive code, multi-turn conversations with large outputs), existing calls may break without warning.
WHAT TO DOGrep your codebase for max_tokens or max_completion_tokens parameters sent to OpenRouter. If any exceed 131,072, reduce them or split the work into multiple requests. Test one long-output workflow end-to-end this week.
CONFIDENCE 95% Primary source ↗ written by anthropic/claude-sonnet-4.5
Show the reasoning — raw diff, triage verdict, confidence
RAW DIFF
 pricing.prompt: 0.000000075
 pricing.completion: 0.00000025
 context_length: 1310720
-top_provider.max_completion_tokens: 943718
+top_provider.max_completion_tokens: 131072
HOW IT WAS JUDGED
triage verdictMATERIAL at 0.95, needed 0.5
triage reasoningModel's maximum completion token output reduced by 86%, directly impacts application design and token budgeting.
signalsmax_completion_tokens decreased significantly · 943718 → 131072 is ~7x reduction · affects model capability / output limits
suppression
triage modelanthropic/claude-haiku-4.5 ($0.00000)
writer modelanthropic/claude-sonnet-4.5 ($0.00000)
ACTION NEEDED PRICINGLIMITSMODEL OpenRouter model catalogue · 2026-09-23 03:42 UTC

DeepSeek Pro Latest: completion pricing up 3.6x, output limit reduced

DOPull last 30 days of DeepSeek Pro usage from OpenRouter, calculate new cost at $0.0000043/completion token, and update your budget forecast.
WHAT CHANGEDEffective now, DeepSeek Pro Latest completion pricing increased from $0.0000012/token to $0.0000043/token (3.6x). Prompt pricing rose marginally from $0.0000004 to $0.0000004. Maximum completion tokens dropped from 393,216 to 384,000 (9,216 tokens less).
WHY IT MATTERSAny application generating long outputs will see immediate cost increases—a 100k token completion now costs $0.43 instead of $0.12. Workloads relying on the full 393k output window will fail or truncate.
WHAT TO DOPull last 30 days of DeepSeek Pro usage from OpenRouter, calculate new cost at $0.0000043/completion token, and update your budget forecast. If any jobs request >384k output tokens, either split them or switch models before they hit the new limit.
CONFIDENCE 95% Primary source ↗ written by anthropic/claude-sonnet-4.5
Show the reasoning — raw diff, triage verdict, confidence
RAW DIFF
 id: ~deepseek/deepseek-pro-latest
 name: DeepSeek: DeepSeek Pro Latest
-pricing.prompt: 0.00000039996
-pricing.completion: 0.00000119988
+pricing.prompt: 0.0000004
+pricing.completion: 0.0000043
 context_length: 1048576
-top_provider.max_completion_tokens: 393216
+top_provider.max_completion_tokens: 384000
HOW IT WAS JUDGED
triage verdictMATERIAL at 0.98, needed 0.5
triage reasoningPricing increased significantly and output token limit reduced. Teams budgeting or optimizing for this model need to recalculate.
signalspricing.prompt increased · pricing.completion increased ~3.6x · max_completion_tokens decreased by 9216 tokens
suppression
triage modelanthropic/claude-haiku-4.5 ($0.00000)
writer modelanthropic/claude-sonnet-4.5 ($0.00000)
WORTH KNOWING PRICINGMODELLIMITS OpenRouter model catalogue · 2026-09-23 03:42 UTC

DeepSeek V4.1 Flash pricing dropped 33% prompt, 17% completion

DOPull last 30 days of usage from your OpenRouter dashboard, recalculate total cost at new rates, and update your budget forecast.
WHAT CHANGEDEffective now: prompt pricing decreased from $0.15/M to $0.10/M tokens (33% reduction), completion pricing decreased from $0.60/M to $0.50/M tokens (17% reduction). Maximum completion tokens increased from 384,000 to 943,718.
WHY IT MATTERSIf you are using this model, your per-request costs just decreased by roughly 20-30% depending on prompt/completion ratio. If you previously hit the 384K completion limit, you can now generate responses 2.5x longer without chunking.
WHAT TO DOPull last 30 days of usage from your OpenRouter dashboard, recalculate total cost at new rates, and update your budget forecast. If you avoided this model due to output length constraints, re-evaluate it for long-form generation tasks.
CONFIDENCE 95% Primary source ↗ written by anthropic/claude-sonnet-4.5
Show the reasoning — raw diff, triage verdict, confidence
RAW DIFF
 id: deepseek/deepseek-v4.1-flash
 name: DeepSeek: DeepSeek V4.1 Flash
-pricing.prompt: 0.00000015
-pricing.completion: 0.0000006
+pricing.prompt: 0.0000001
+pricing.completion: 0.0000005
 context_length: 1048576
-top_provider.max_completion_tokens: 384000
+top_provider.max_completion_tokens: 943718
HOW IT WAS JUDGED
triage verdictMATERIAL at 0.98, needed 0.5
triage reasoningPricing and token limits changed materially for an active model.
signalsprompt price decreased 33% · completion price decreased 17% · max_completion_tokens increased 146%
suppression
triage modelanthropic/claude-haiku-4.5 ($0.00000)
writer modelanthropic/claude-sonnet-4.5 ($0.00000)
WORTH KNOWING PRICINGLIMITSMODEL OpenRouter model catalogue · 2026-09-22 20:59 UTC

DeepSeek Pro Latest pricing dropped 29%, output limit raised to 393K tokens

DOReforecast your OpenRouter spend for this model downward by 29% and notify whoever owns the budget line.
WHAT CHANGEDOpenRouter reduced pricing for deepseek/deepseek-pro-latest from $0.00000056364 to $0.00000039996 per prompt token (29% decrease) and $0.00000169092 to $0.00000119988 per completion token (29% decrease). Maximum completion tokens increased from 384,000 to 393,216.
WHY IT MATTERSIf you are using this model, your API costs will drop by roughly 29% with no code changes required. The higher output limit means requests that previously hit the 384K token ceiling can now complete without truncation.
WHAT TO DOReforecast your OpenRouter spend for this model downward by 29% and notify whoever owns the budget line. If you have retry logic or truncation handling for 384K token limits, verify it still works correctly at the new 393K ceiling.
CONFIDENCE 95% Primary source ↗ written by anthropic/claude-sonnet-4.5
Show the reasoning — raw diff, triage verdict, confidence
RAW DIFF
 id: ~deepseek/deepseek-pro-latest
 name: DeepSeek: DeepSeek Pro Latest
-pricing.prompt: 0.00000056364
-pricing.completion: 0.00000169092
+pricing.prompt: 0.00000039996
+pricing.completion: 0.00000119988
 context_length: 1048576
-top_provider.max_completion_tokens: 384000
+top_provider.max_completion_tokens: 393216
HOW IT WAS JUDGED
triage verdictMATERIAL at 0.98, needed 0.5
triage reasoningPricing dropped significantly and token limits increased. Teams budgeting or optimizing costs need to know.
signalsprompt price decreased 29% · completion price decreased 29% · max_completion_tokens increased from 384000 to 393216
suppression
triage modelanthropic/claude-haiku-4.5 ($0.00000)
writer modelanthropic/claude-sonnet-4.5 ($0.00000)
WORTH KNOWING PRICINGMODEL OpenRouter model catalogue · 2026-09-22 20:59 UTC

Claude Opus Latest pricing reduced 20% on both prompt and completion

DOUpdate cost projections and budget models to reflect the new rates.
WHAT CHANGEDOpenRouter dropped pricing for anthropic/claude-opus-latest from $0.000005 to $0.000004 per prompt token (20% reduction) and from $0.000025 to $0.00002 per completion token (20% reduction), effective now.
WHY IT MATTERSAny application currently using this model will see immediate cost reduction. Existing budget forecasts and cost alerts based on the old rates are now overstated by 20%.
WHAT TO DOUpdate cost projections and budget models to reflect the new rates. If you have spend alerts or cost dashboards for this model, adjust thresholds down by 20% to maintain the same real-dollar triggers.
CONFIDENCE 95% Primary source ↗ written by anthropic/claude-sonnet-4.5
Show the reasoning — raw diff, triage verdict, confidence
RAW DIFF
 id: ~anthropic/claude-opus-latest
 name: Anthropic: Claude Opus Latest
-pricing.prompt: 0.000005
-pricing.completion: 0.000025
+pricing.prompt: 0.000004
+pricing.completion: 0.00002
 context_length: 1000000
 top_provider.max_completion_tokens: 128000
HOW IT WAS JUDGED
triage verdictMATERIAL at 0.95, needed 0.5
triage reasoningPricing for Claude Opus Latest decreased. Teams budgeting or optimizing costs need to know.
signalsprice decreased on prompt tokens (0.000005 → 0.000004) · price decreased on completion tokens (0.000025 → 0.00002) · pricing change affects cost calculations for active deployments
suppression
triage modelanthropic/claude-haiku-4.5 ($0.00000)
writer modelanthropic/claude-sonnet-4.5 ($0.00000)
WORTH KNOWING MODELPRICINGAPI OpenRouter model catalogue · 2026-09-22 20:59 UTC

OpenAI GPT-6 Sol batch model now available on OpenRouter

DOIf you process GPT-6 Sol requests that can tolerate batch latency, test this endpoint with a sample workload to measure cost savings against your current real-time usage.
WHAT CHANGEDOpenRouter added openai/gpt-6-sol:batch with $0.000001 per prompt token, $0.000005 per completion token, 1.05M token context window, and 128k completion token limit.
WHY IT MATTERSThis is a new batch processing option for GPT-6 Sol at significantly lower pricing than real-time inference, enabling cost-effective processing of large-scale or non-time-sensitive workloads through OpenRouter's unified API.
WHAT TO DOIf you process GPT-6 Sol requests that can tolerate batch latency, test this endpoint with a sample workload to measure cost savings against your current real-time usage.
CONFIDENCE 85% Primary source ↗ written by anthropic/claude-sonnet-4.5
Show the reasoning — raw diff, triage verdict, confidence
RAW DIFF
+id: openai/gpt-6-sol:batch
+name: OpenAI: GPT-6 Sol (batch)
+pricing.prompt: 0.000001
+pricing.completion: 0.000005
+context_length: 1050000
+top_provider.max_completion_tokens: 128000
HOW IT WAS JUDGED
triage verdictMATERIAL at 0.95, needed 0.5
triage reasoningNew model entry with pricing and limits affects platform availability and cost planning for engineers.
signalsnew model added to catalogue · pricing specified (prompt and completion rates) · context length declared (1.05M tokens) · completion token limit specified (128k)
suppression
triage modelanthropic/claude-haiku-4.5 ($0.00000)
writer modelanthropic/claude-sonnet-4.5 ($0.00000)
WORTH KNOWING MODELPRICINGAPI OpenRouter model catalogue · 2026-09-22 20:59 UTC

OpenAI GPT-6 Sol Pro batch variant now available via OpenRouter

DOIf you currently use gpt-4 or gpt-4-turbo for batch jobs, benchmark gpt-6-sol-pro:batch against your workload and calculate cost difference at the stated rates.
WHAT CHANGEDOpenRouter added openai/gpt-6-sol-pro:batch to their catalogue on 2026-09-22. Pricing is $0.000001 per prompt token and $0.000005 per completion token. Context length is 1,050,000 tokens with a 128,000 token completion limit.
WHY IT MATTERSBatch processing typically offers 50% cost savings over synchronous API calls for non-time-sensitive workloads. The 1M+ context window enables processing entire codebases or long documents in a single request without chunking.
WHAT TO DOIf you currently use gpt-4 or gpt-4-turbo for batch jobs, benchmark gpt-6-sol-pro:batch against your workload and calculate cost difference at the stated rates. Update your model routing logic to include this identifier if the quality-cost tradeoff works.
CONFIDENCE 85% Primary source ↗ written by anthropic/claude-sonnet-4.5
Show the reasoning — raw diff, triage verdict, confidence
RAW DIFF
+id: openai/gpt-6-sol-pro:batch
+name: OpenAI: GPT-6 Sol Pro (batch)
+pricing.prompt: 0.000001
+pricing.completion: 0.000005
+context_length: 1050000
+top_provider.max_completion_tokens: 128000
HOW IT WAS JUDGED
triage verdictMATERIAL at 0.95, needed 0.5
triage reasoningNew model entry with pricing and limits affects platform selection and cost planning.
signalsnew model added to catalogue · pricing specified (prompt and completion rates) · context length defined · completion token limit specified · batch variant indicates new capability tier
suppression
triage modelanthropic/claude-haiku-4.5 ($0.00000)
writer modelanthropic/claude-sonnet-4.5 ($0.00000)
WORTH KNOWING MODELPRICING OpenRouter model catalogue · 2026-09-22 20:58 UTC

OpenAI GPT-6 Sol Pro now available via OpenRouter

DOCheck whether any of your OpenRouter integrations use dynamic model selection or 'auto' routing that might pick up this model.
WHAT CHANGEDOpenRouter added openai/gpt-6-sol-pro to their catalogue on 2026-09-22. Pricing is $0.000002 per prompt token and $0.00001 per completion token. Context length is 1,050,000 tokens with a 128,000 token completion limit.
WHY IT MATTERSThis is a new model tier with significantly expanded context (1M+ tokens) at rates 5x higher for completions than typical GPT-4 pricing. If your application would benefit from the larger context window, you now have a routing option; if cost optimization matters more, this is not the model to default to.
WHAT TO DOCheck whether any of your OpenRouter integrations use dynamic model selection or 'auto' routing that might pick up this model. If so, verify the cost implications before it gets selected in production traffic.
CONFIDENCE 85% Primary source ↗ written by anthropic/claude-sonnet-4.5
Show the reasoning — raw diff, triage verdict, confidence
RAW DIFF
+id: openai/gpt-6-sol-pro
+name: OpenAI: GPT-6 Sol Pro
+pricing.prompt: 0.000002
+pricing.completion: 0.00001
+context_length: 1050000
+top_provider.max_completion_tokens: 128000
HOW IT WAS JUDGED
triage verdictMATERIAL at 0.95, needed 0.5
triage reasoningNew model entry with pricing and limits affects platform availability and cost planning.
signalsnew model added to catalogue · pricing specified (prompt and completion rates) · context length defined · completion token limit set
suppression
triage modelanthropic/claude-haiku-4.5 ($0.00000)
writer modelanthropic/claude-sonnet-4.5 ($0.00000)
WORTH KNOWING MODELPRICING OpenRouter model catalogue · 2026-09-22 20:58 UTC

OpenAI GPT-6 Luna batch model added to OpenRouter

DOIf you have batch processing workloads or need to process documents larger than your current context limits, test this model against your existing pipeline to measure co…
WHAT CHANGEDOpenRouter added openai/gpt-6-luna:batch with pricing at $0.00000005 per prompt token and $0.00000025 per completion token, 1,050,000 token context window, and 128,000 token completion limit.
WHY IT MATTERSThis batch endpoint offers significantly lower pricing than typical real-time models for workloads that can tolerate asynchronous processing, and the 1M+ context window enables processing very large documents or conversations in a single call.
WHAT TO DOIf you have batch processing workloads or need to process documents larger than your current context limits, test this model against your existing pipeline to measure cost savings and latency trade-offs.
CONFIDENCE 85% Primary source ↗ written by anthropic/claude-sonnet-4.5
Show the reasoning — raw diff, triage verdict, confidence
RAW DIFF
+id: openai/gpt-6-luna:batch
+name: OpenAI: GPT-6 Luna (batch)
+pricing.prompt: 0.00000005
+pricing.completion: 0.00000025
+context_length: 1050000
+top_provider.max_completion_tokens: 128000
HOW IT WAS JUDGED
triage verdictMATERIAL at 0.95, needed 0.5
triage reasoningNew model entry with pricing and limits affects platform availability and cost planning for engineers.
signalsnew model added to catalogue · pricing specified (prompt and completion rates) · context length defined · completion token limit specified
suppression
triage modelanthropic/claude-haiku-4.5 ($0.00000)
writer modelanthropic/claude-sonnet-4.5 ($0.00000)
WORTH KNOWING MODELPRICINGAPI OpenRouter model catalogue · 2026-09-22 20:58 UTC

Claude Opus 5.5 batch variant added at 50% discount

DOIdentify any Claude Opus 5.5 calls that can tolerate async processing (report generation, bulk analysis, overnight jobs) and test switching those to the :batch endpoint…
WHAT CHANGEDOpenRouter added anthropic/claude-opus-5.5:batch with prompt tokens at $0.000002 and completion at $0.00001, 1M context window, 128k max completion tokens. This is half the cost of the standard Opus 5.5 model.
WHY IT MATTERSIf you run high-volume or non-latency-sensitive Claude Opus 5.5 workloads, batch mode cuts your API costs in half. Batch processing typically adds delay but reduces per-token cost by accepting asynchronous execution.
WHAT TO DOIdentify any Claude Opus 5.5 calls that can tolerate async processing (report generation, bulk analysis, overnight jobs) and test switching those to the :batch endpoint to halve costs on that traffic.
CONFIDENCE 85% Primary source ↗ written by anthropic/claude-sonnet-4.5
Show the reasoning — raw diff, triage verdict, confidence
RAW DIFF
+id: anthropic/claude-opus-5.5:batch
+name: Anthropic: Claude Opus 5.5 (batch)
+pricing.prompt: 0.000002
+pricing.completion: 0.00001
+context_length: 1000000
+top_provider.max_completion_tokens: 128000
HOW IT WAS JUDGED
triage verdictMATERIAL at 0.95, needed 0.5
triage reasoningNew model availability with defined pricing and limits affects platform selection and cost planning.
signalsnew model added to catalogue · pricing specified (prompt and completion rates) · context window defined (1M tokens) · completion token limit specified (128k) · batch variant of existing model
suppression
triage modelanthropic/claude-haiku-4.5 ($0.00000)
writer modelanthropic/claude-sonnet-4.5 ($0.00000)
ACTION NEEDED LIMITSMODELAPI OpenRouter model catalogue · 2026-09-22 16:28 UTC

Z.ai GLM Latest max completion tokens cut from 943,718 to 131,072

DOGrep your codebase for max_tokens or max_completion_tokens parameters sent to ~z-ai/glm-latest.
WHAT CHANGEDThe top_provider.max_completion_tokens for model ~z-ai/glm-latest dropped from 943,718 to 131,072 tokens (86% reduction). Pricing changed negligibly: prompt tokens from $0.0000006545 to $0.0000006538, completion tokens from $0.000002057 to $0.0000020548 per token.
WHY IT MATTERSAny code requesting completion lengths above 131,072 tokens will now fail or be truncated. If you generate long-form content, transcripts, or batch outputs with this model, those requests will break.
WHAT TO DOGrep your codebase for max_tokens or max_completion_tokens parameters sent to ~z-ai/glm-latest. If any exceed 131,072, either reduce them or switch to a model with higher limits before your next deployment.
CONFIDENCE 95% Primary source ↗ written by anthropic/claude-sonnet-4.5
Show the reasoning — raw diff, triage verdict, confidence
RAW DIFF
 id: ~z-ai/glm-latest
 name: Z.ai: GLM Latest
-pricing.prompt: 0.0000006545
-pricing.completion: 0.000002057
+pricing.prompt: 0.0000006538
+pricing.completion: 0.0000020548
 context_length: 1310720
-top_provider.max_completion_tokens: 943718
+top_provider.max_completion_tokens: 131072
HOW IT WAS JUDGED
triage verdictMATERIAL at 0.98, needed 0.5
triage reasoningPricing dropped and max output tokens cut dramatically. Teams budgeting or relying on long completions need to know.
signalspricing.prompt decreased · pricing.completion decreased · max_completion_tokens reduced by 86% (943718 → 131072)
suppression
triage modelanthropic/claude-haiku-4.5 ($0.00000)
writer modelanthropic/claude-sonnet-4.5 ($0.00000)
ACTION NEEDED PRICINGLIMITSMODEL OpenRouter model catalogue · 2026-09-22 16:28 UTC

DeepSeek Pro Latest: pricing cut, max completion tokens reduced 59%

DOCheck your application logs for any DeepSeek Pro responses exceeding 384,000 tokens in the past 30 days.
WHAT CHANGEDPrompt pricing dropped from $0.000000624 to $0.00000056364 per token (~10% decrease). Completion pricing dropped from $0.00000288 to $0.00000169092 per token (~41% decrease). Maximum completion tokens reduced from 943,718 to 384,000 tokens (59% reduction). Changes are live as of 22 September 2026.
WHY IT MATTERSIf you generate responses longer than 384,000 tokens, requests will now fail or truncate where they previously succeeded. The cost reduction is real but the capability ceiling dropped by more than half.
WHAT TO DOCheck your application logs for any DeepSeek Pro responses exceeding 384,000 tokens in the past 30 days. If found, either switch to a model with higher limits or redesign the workflow to chunk outputs below the new ceiling.
CONFIDENCE 95% Primary source ↗ written by anthropic/claude-sonnet-4.5
Show the reasoning — raw diff, triage verdict, confidence
RAW DIFF
 id: ~deepseek/deepseek-pro-latest
 name: DeepSeek: DeepSeek Pro Latest
-pricing.prompt: 0.000000624
-pricing.completion: 0.00000288
+pricing.prompt: 0.00000056364
+pricing.completion: 0.00000169092
 context_length: 1048576
-top_provider.max_completion_tokens: 943718
+top_provider.max_completion_tokens: 384000
HOW IT WAS JUDGED
triage verdictMATERIAL at 0.98, needed 0.5
triage reasoningPricing cuts and token limit reduction directly impact engineering budgets and model capability planning.
signalsprompt pricing decreased ~9.8% · completion pricing decreased ~41.3% · max_completion_tokens reduced from 943718 to 384000 (~59% reduction) · three numeric changes affecting cost and capability
suppression
triage modelanthropic/claude-haiku-4.5 ($0.00000)
writer modelanthropic/claude-sonnet-4.5 ($0.00000)
ACTION NEEDED LIMITSPRICINGMODELAPI OpenRouter model catalogue · 2026-09-22 16:28 UTC

Z.ai GLM 5.3 batch: output limit cut to 131K tokens, pricing up 3-9%

DOGrep your codebase for 'glm-5.3:batch' and check max_tokens or completion length assumptions.
WHAT CHANGEDThe Z.ai GLM 5.3 batch model reduced max_completion_tokens from 943,718 to 131,072 tokens (86% reduction). Prompt pricing increased from $0.0000007 to $0.00000072 per token (2.9% increase). Completion pricing increased from $0.0000022 to $0.0000024 per token (9.1% increase). Context length remains 1,048,576 tokens.
WHY IT MATTERSAny batch job generating outputs longer than 131K tokens will now fail or truncate. If you were relying on the previous 943K output capacity for long-form generation, summarization of large documents, or multi-document synthesis, those workflows will break. The pricing increase affects cost forecasts for high-volume batch processing.
WHAT TO DOGrep your codebase for 'glm-5.3:batch' and check max_tokens or completion length assumptions. If any job expects outputs over 131K tokens, either chunk the work into multiple calls or switch models. Recalculate batch processing costs using the new rates and update budgets if this model handles significant volume.
CONFIDENCE 95% Primary source ↗ written by anthropic/claude-sonnet-4.5
Show the reasoning — raw diff, triage verdict, confidence
RAW DIFF
 id: z-ai/glm-5.3:batch
 name: Z.ai: GLM 5.3 (batch)
-pricing.prompt: 0.0000007
-pricing.completion: 0.0000022
+pricing.prompt: 0.00000072
+pricing.completion: 0.0000024
 context_length: 1048576
-top_provider.max_completion_tokens: 943718
+top_provider.max_completion_tokens: 131072
HOW IT WAS JUDGED
triage verdictMATERIAL at 0.95, needed 0.5
triage reasoningPricing increased and max output tokens cut dramatically, affecting cost and feasibility of workloads.
signalspricing.prompt increased 2.9% · pricing.completion increased 9.1% · max_completion_tokens decreased 86% (943718 → 131072) · breaking change to output capacity
suppression
triage modelanthropic/claude-haiku-4.5 ($0.00000)
writer modelanthropic/claude-sonnet-4.5 ($0.00000)
ACTION NEEDED PRICINGLIMITSMODEL OpenRouter model catalogue · 2026-09-22 16:28 UTC

GLM 5.3 Flash batch pricing cut 20%, max completion tokens reduced 86%

DOQuery your logs for calls to z-ai/glm-5.3-flash:batch with completion lengths exceeding 131,072 tokens.
WHAT CHANGEDOpenRouter's Z.ai GLM 5.3 Flash batch model reduced prompt pricing from $0.000000075 to $0.00000006 per token (20% decrease) and completion pricing from $0.00000025 to $0.0000002 per token (20% decrease). Simultaneously, max_completion_tokens dropped from 943,718 to 131,072 tokens (86% reduction).
WHY IT MATTERSAny workload generating responses longer than 131,072 tokens will now fail or truncate. The pricing reduction does not compensate if you must switch to a different model to preserve output length capability.
WHAT TO DOQuery your logs for calls to z-ai/glm-5.3-flash:batch with completion lengths exceeding 131,072 tokens. If found, test whether your use case tolerates the new limit or requires migration to a model with higher max_completion_tokens before your next production run.
CONFIDENCE 95% Primary source ↗ written by anthropic/claude-sonnet-4.5
Show the reasoning — raw diff, triage verdict, confidence
RAW DIFF
 id: z-ai/glm-5.3-flash:batch
 name: Z.ai: GLM 5.3 Flash (batch)
-pricing.prompt: 0.000000075
-pricing.completion: 0.00000025
+pricing.prompt: 0.00000006
+pricing.completion: 0.0000002
 context_length: 1048576
-top_provider.max_completion_tokens: 943718
+top_provider.max_completion_tokens: 131072
HOW IT WAS JUDGED
triage verdictMATERIAL at 0.98, needed 0.5
triage reasoningPricing dropped and max output tokens cut dramatically. Teams budgeting or relying on long completions must know.
signalspricing.prompt decreased 20% · pricing.completion decreased 20% · max_completion_tokens reduced by 86% (943718 → 131072) · breaking change to model capability
suppression
triage modelanthropic/claude-haiku-4.5 ($0.00000)
writer modelanthropic/claude-sonnet-4.5 ($0.00000)
ACTION NEEDED PRICINGLIMITSMODEL OpenRouter model catalogue · 2026-09-22 16:27 UTC

Qwen3.6 27B pricing increased, completion token limit quadrupled

DOPull usage logs for qwen/qwen3.6-27b from the past 30 days, calculate new monthly cost at the updated rates, and update your budget forecast.
WHAT CHANGEDEffective now: prompt pricing increased from $0.0000003 to $0.00000032 per token (~6.7% increase), completion pricing increased from $0.000002 to $0.0000027 per token (35% increase). Maximum completion tokens increased from 65,536 to 262,140.
WHY IT MATTERSIf you are using this model in production, your per-request costs just increased by 35% on the output side. High-volume applications will see material budget impact. The 4x increase in max completion tokens enables longer responses but does not offset the price increase.
WHAT TO DOPull usage logs for qwen/qwen3.6-27b from the past 30 days, calculate new monthly cost at the updated rates, and update your budget forecast. If cost is material, evaluate whether switching to a different model in the Qwen family or another provider offers better economics.
CONFIDENCE 95% Primary source ↗ written by anthropic/claude-sonnet-4.5
Show the reasoning — raw diff, triage verdict, confidence
RAW DIFF
 id: qwen/qwen3.6-27b
 name: Qwen: Qwen3.6 27B
-pricing.prompt: 0.0000003
-pricing.completion: 0.000002
+pricing.prompt: 0.00000032
+pricing.completion: 0.0000027
 context_length: 262144
-top_provider.max_completion_tokens: 65536
+top_provider.max_completion_tokens: 262140
HOW IT WAS JUDGED
triage verdictMATERIAL at 0.98, needed 0.5
triage reasoningPricing increased and output token limit quadrupled. Direct impact on engineering budgets and application design.
signalsprompt pricing increased ~6.7% · completion pricing increased ~35% · max_completion_tokens increased 4x (65536 → 262140) · pricing and limits are explicit commitments affecting cost and capability
suppression
triage modelanthropic/claude-haiku-4.5 ($0.00000)
writer modelanthropic/claude-sonnet-4.5 ($0.00000)
WORTH KNOWING PRICINGLIMITSMODEL OpenRouter model catalogue · 2026-09-22 16:27 UTC

OpenAI gpt-oss-20b pricing cut 40% prompt, 31% completion; output capped at 32K tokens

DOCheck your application logs for any gpt-oss-20b completions exceeding 32,768 tokens in the past 30 days.
WHAT CHANGEDOpenRouter's gpt-oss-20b model pricing dropped from $0.00000003 to $0.00000018 per prompt token (40% reduction) and $0.00000013 to $0.00000009 per completion token (31% reduction). Maximum completion tokens reduced from 117,964 to 32,768, effective now.
WHY IT MATTERSIf you generate responses longer than 32K tokens, calls will now truncate or fail. Cost forecasts based on the old pricing are overstated by roughly a third.
WHAT TO DOCheck your application logs for any gpt-oss-20b completions exceeding 32,768 tokens in the past 30 days. If found, either chunk your outputs or switch models. Update your cost model with the new per-token rates.
CONFIDENCE 85% Primary source ↗ written by anthropic/claude-sonnet-4.5
Show the reasoning — raw diff, triage verdict, confidence
RAW DIFF
 id: openai/gpt-oss-20b
 name: OpenAI: gpt-oss-20b
-pricing.prompt: 0.00000003
-pricing.completion: 0.00000013
+pricing.prompt: 0.000000018
+pricing.completion: 0.00000009
 context_length: 131072
-top_provider.max_completion_tokens: 117964
+top_provider.max_completion_tokens: 32768
HOW IT WAS JUDGED
triage verdictMATERIAL at 0.98, needed 0.5
triage reasoningPricing dropped significantly and max output tokens cut by 72%, affecting budget and use-case viability.
signalspricing.prompt decreased 40% · pricing.completion decreased 31% · max_completion_tokens reduced by 72% (117964 → 32768) · model capability constraint change
suppression
triage modelanthropic/claude-haiku-4.5 ($0.00000)
writer modelanthropic/claude-sonnet-4.5 ($0.00000)
WORTH KNOWING MODELLIMITS OpenRouter model catalogue · 2026-09-22 16:27 UTC

AionLabs Aion-3.0-Mini context window expanded to 1,048,576 tokens

DOIdentify pipelines currently splitting inputs for this model and benchmark end-to-end cost and latency with single-pass processing at the new limit.
WHAT CHANGEDThe context_length for AionLabs: Aion-3.0-Mini increased from 131,072 tokens to 1,048,576 tokens (8x expansion). Pricing remains $0.0000007 per prompt token and $0.0000014 per completion token.
WHY IT MATTERSApplications currently chunking or truncating inputs to fit the 131K limit can now process 8x more content in a single request, eliminating multi-pass workflows and reducing latency. This changes the cost-performance calculation for document analysis, long-context retrieval, and conversation history retention.
WHAT TO DOIdentify pipelines currently splitting inputs for this model and benchmark end-to-end cost and latency with single-pass processing at the new limit. Update any hardcoded context_length checks from 131072 to 1048576.
CONFIDENCE 85% Primary source ↗ written by anthropic/claude-sonnet-4.5
Show the reasoning — raw diff, triage verdict, confidence
RAW DIFF
 name: AionLabs: Aion-3.0-Mini
 pricing.prompt: 0.0000007
 pricing.completion: 0.0000014
-context_length: 131072
+context_length: 1048576
 top_provider.max_completion_tokens: 32768
HOW IT WAS JUDGED
triage verdictMATERIAL at 0.95, needed 0.5
triage reasoningContext window expansion is a material capability change affecting what workloads the model can handle.
signalscontext_length increased 8x (131072 → 1048576 tokens) · model capability change affects application architecture decisions
suppression
triage modelanthropic/claude-haiku-4.5 ($0.00000)
writer modelanthropic/claude-sonnet-4.5 ($0.00000)
WORTH KNOWING MODELLIMITS OpenRouter model catalogue · 2026-09-22 16:27 UTC

AionLabs Aion-3.0 context window expanded from 131K to 1M tokens

DOIdentify code paths that chunk documents or conversations specifically for Aion-3.0's previous 131K limit, and test whether removing that chunking logic improves perform…
WHAT CHANGEDThe context_length for AionLabs: Aion-3.0 increased from 131,072 tokens to 1,048,576 tokens (8x expansion). Pricing remains unchanged at $0.000003 per prompt token and $0.000006 per completion token.
WHY IT MATTERSApplications currently chunking or summarizing documents to fit within 131K tokens can now process 8x larger inputs in a single call, reducing complexity and potentially lowering total costs by eliminating multi-pass operations.
WHAT TO DOIdentify code paths that chunk documents or conversations specifically for Aion-3.0's previous 131K limit, and test whether removing that chunking logic improves performance or reduces API calls.
CONFIDENCE 85% Primary source ↗ written by anthropic/claude-sonnet-4.5
Show the reasoning — raw diff, triage verdict, confidence
RAW DIFF
 name: AionLabs: Aion-3.0
 pricing.prompt: 0.000003
 pricing.completion: 0.000006
-context_length: 131072
+context_length: 1048576
 top_provider.max_completion_tokens: 32768
HOW IT WAS JUDGED
triage verdictMATERIAL at 0.95, needed 0.5
triage reasoningContext window expansion is a material capability change affecting prompt design and use-case feasibility.
signalscontext_length increased 8x (131072 → 1048576 tokens) · model capability change affects application design decisions
suppression
triage modelanthropic/claude-haiku-4.5 ($0.00000)
writer modelanthropic/claude-sonnet-4.5 ($0.00000)
WORTH KNOWING MODELLIMITS OpenRouter model catalogue · 2026-09-22 16:27 UTC

AionLabs Aion-2.0 context window expanded from 131K to 1M tokens

DOIdentify codepaths that chunk inputs for this model and evaluate whether removing chunking logic would reduce latency or cost.
WHAT CHANGEDThe context_length for AionLabs: Aion-2.0 increased from 131,072 tokens to 1,048,576 tokens (8x expansion). Pricing remains unchanged at $0.0000008 per prompt token and $0.0000016 per completion token.
WHY IT MATTERSApplications currently chunking or truncating inputs to fit the 131K limit can now process 8x more context in a single call, potentially eliminating multi-pass strategies and reducing total API calls for large document processing.
WHAT TO DOIdentify codepaths that chunk inputs for this model and evaluate whether removing chunking logic would reduce latency or cost. Test with representative large inputs to confirm the expanded window works as expected.
CONFIDENCE 85% Primary source ↗ written by anthropic/claude-sonnet-4.5
Show the reasoning — raw diff, triage verdict, confidence
RAW DIFF
 name: AionLabs: Aion-2.0
 pricing.prompt: 0.0000008
 pricing.completion: 0.0000016
-context_length: 131072
+context_length: 1048576
 top_provider.max_completion_tokens: 32768
HOW IT WAS JUDGED
triage verdictMATERIAL at 0.95, needed 0.5
triage reasoningContext window expansion is a material capability change affecting how engineers can use this model.
signalscontext_length increased 8x (131072 → 1048576 tokens) · model capability change affects application design decisions
suppression
triage modelanthropic/claude-haiku-4.5 ($0.00000)
writer modelanthropic/claude-sonnet-4.5 ($0.00000)
WORTH KNOWING LIMITSAPIMODEL OpenRouter model catalogue · 2026-09-22 11:06 UTC

OpenRouter max completion tokens increased from 102400 to 943718

DOGrep your codebase for max_tokens or max_completion_tokens parameters in OpenRouter calls.
WHAT CHANGEDThe top_provider.max_completion_tokens limit increased from 102,400 to 943,718 tokens (9.2x increase). Context length remains 1,310,720 tokens. Pricing unchanged at $0.000000075 per prompt token and $0.00000025 per completion token.
WHY IT MATTERSIf you currently cap completion requests at the old 102,400 limit in your code, you are leaving 841,318 tokens of available capacity unused. Conversely, if you request completions without explicit limits, responses could now be 9x larger than before, increasing latency and cost per request by the same factor.
WHAT TO DOGrep your codebase for max_tokens or max_completion_tokens parameters in OpenRouter calls. If you set explicit caps, decide whether to raise them. If you rely on defaults, add explicit caps now to prevent unexpectedly large responses.
CONFIDENCE 85% Primary source ↗ written by anthropic/claude-sonnet-4.5
Show the reasoning — raw diff, triage verdict, confidence
RAW DIFF
 pricing.prompt: 0.000000075
 pricing.completion: 0.00000025
 context_length: 1310720
-top_provider.max_completion_tokens: 102400
+top_provider.max_completion_tokens: 943718
HOW IT WAS JUDGED
triage verdictMATERIAL at 0.92, needed 0.5
triage reasoningCompletion token limit nearly 10x higher; engineering teams must re-evaluate request sizing and costs.
signalsmax_completion_tokens increased 9.2x (102400 → 943718) · limit change on production model · affects token budgeting and request planning
suppression
triage modelanthropic/claude-haiku-4.5 ($0.00000)
writer modelanthropic/claude-sonnet-4.5 ($0.00000)
WORTH KNOWING PRICINGMODEL OpenRouter model catalogue · 2026-09-22 11:06 UTC

DeepSeek V4 Flash completion tokens increased 25%

DOPull your last 30 days of completion token usage for this model ID from OpenRouter logs or your own metrics, multiply by the new rate, and update your cost forecast.
WHAT CHANGEDOpenRouter raised the completion token price for deepseek/deepseek-v4-flash-latest from $0.0000008 to $0.000001 per token, a 25% increase. Prompt pricing ($0.00000003) and context length (1.31M tokens) remain unchanged.
WHY IT MATTERSIf you generate high volumes of completion tokens with this model, your monthly API costs will increase by 25% at current usage levels. A workload generating 1 billion completion tokens per month now costs $1,000 instead of $800.
WHAT TO DOPull your last 30 days of completion token usage for this model ID from OpenRouter logs or your own metrics, multiply by the new rate, and update your cost forecast. If the increase is material, evaluate whether switching to the non-latest pinned version or a different model makes sense.
CONFIDENCE 95% Primary source ↗ written by anthropic/claude-sonnet-4.5
Show the reasoning — raw diff, triage verdict, confidence
RAW DIFF
 id: ~deepseek/deepseek-v4-flash-latest
 name: DeepSeek: DeepSeek V4 Flash Latest
 pricing.prompt: 0.00000003
-pricing.completion: 0.0000008
+pricing.completion: 0.000001
 context_length: 1310720
 top_provider.max_completion_tokens: 943718
HOW IT WAS JUDGED
triage verdictMATERIAL at 0.95, needed 0.5
triage reasoningCompletion pricing for DeepSeek V4 Flash increased 25%, affecting cost calculations for production workloads.
signalscompletion token price increased · price change: 0.0000008 → 0.000001 (25% increase)
suppression
triage modelanthropic/claude-haiku-4.5 ($0.00000)
writer modelanthropic/claude-sonnet-4.5 ($0.00000)
ACTION NEEDED PRICINGMODEL OpenRouter model catalogue · 2026-09-22 11:06 UTC

DeepSeek Pro Latest pricing increased 12% prompt, 72% completion

DOPull last 30 days of deepseek-pro-latest usage from OpenRouter logs, calculate new cost at current volume, and update your monthly forecast.
WHAT CHANGEDOpenRouter's deepseek-pro-latest model pricing changed: prompt tokens from $0.000000558624 to $0.000000624 per token (+11.7%), completion tokens from $0.000001675872 to $0.00000288 per token (+71.6%). Max completion tokens increased from 384,000 to 943,718.
WHY IT MATTERSCompletion token costs rose 72%, which compounds on long-form generation workloads. A 10,000-token completion that cost $0.0168 now costs $0.0288, a $0.012 increase per call. High-volume applications will see material budget impact.
WHAT TO DOPull last 30 days of deepseek-pro-latest usage from OpenRouter logs, calculate new cost at current volume, and update your monthly forecast. If completion length averages above 5,000 tokens, evaluate whether the increased max_completion_tokens justifies the 72% cost increase or whether to switch models.
CONFIDENCE 95% Primary source ↗ written by anthropic/claude-sonnet-4.5
Show the reasoning — raw diff, triage verdict, confidence
RAW DIFF
 id: ~deepseek/deepseek-pro-latest
 name: DeepSeek: DeepSeek Pro Latest
-pricing.prompt: 0.000000558624
-pricing.completion: 0.000001675872
+pricing.prompt: 0.000000624
+pricing.completion: 0.00000288
 context_length: 1048576
-top_provider.max_completion_tokens: 384000
+top_provider.max_completion_tokens: 943718
HOW IT WAS JUDGED
triage verdictMATERIAL at 0.98, needed 0.5
triage reasoningPricing per token increased significantly; max output tokens nearly doubled.
signalspricing.prompt increased ~11.7% · pricing.completion increased ~71.6% · max_completion_tokens increased ~145% (384000 → 943718)
suppression
triage modelanthropic/claude-haiku-4.5 ($0.00000)
writer modelanthropic/claude-sonnet-4.5 ($0.00000)
WORTH KNOWING LIMITSMODELAPI OpenRouter model catalogue · 2026-09-22 11:06 UTC

OpenRouter max_completion_tokens increased from 32768 to 235929

DOIf you have workflows that chunk outputs to stay under 32768 tokens, test whether single-pass generation at higher token counts improves quality or reduces latency for y…
WHAT CHANGEDThe top_provider.max_completion_tokens value increased from 32768 to 235929 tokens. Context length remains 262144 tokens. Pricing unchanged at $0.00000015 per prompt token and $0.0000012 per completion token.
WHY IT MATTERSApplications currently capped at 32768 output tokens can now request up to 235929 tokens per completion, enabling longer-form generation without chunking. Existing requests under the old limit continue to work unchanged.
WHAT TO DOIf you have workflows that chunk outputs to stay under 32768 tokens, test whether single-pass generation at higher token counts improves quality or reduces latency for your use case.
CONFIDENCE 85% Primary source ↗ written by anthropic/claude-sonnet-4.5
Show the reasoning — raw diff, triage verdict, confidence
RAW DIFF
 pricing.prompt: 0.00000015
 pricing.completion: 0.0000012
 context_length: 262144
-top_provider.max_completion_tokens: 32768
+top_provider.max_completion_tokens: 235929
HOW IT WAS JUDGED
triage verdictMATERIAL at 0.92, needed 0.5
triage reasoningMaximum completion token limit changed substantially, affecting application design and output capacity.
signalsmax_completion_tokens decreased significantly · 32768 → 235929 represents constraint change · affects output capacity for dependent applications
suppression
triage modelanthropic/claude-haiku-4.5 ($0.00000)
writer modelanthropic/claude-sonnet-4.5 ($0.00000)
WORTH KNOWING APIMODEL Claude Platform release notes · 2026-09-22 03:48 UTC

New beta header exposes thinking block prefix mismatches without enforcement

DOAdd the thinking-binding-controls-2026-08-01 header to requests on Claude Fable 5.1, log all thinking_mismatch_allowed entries for one week, and audit any history-editin…
WHAT CHANGEDThe thinking-binding-controls-2026-08-01 beta header adds a thinking_mismatch_allowed entry type to input_transformations responses. This flags thinking blocks that fail prefix validation but are not rejected—specifically on Claude Fable 5.1 requests from accounts created before August 31, 2026, when prefix_mismatch_behavior is unset. The flagged blocks still reach the model unchanged.
WHY IT MATTERSIf you edit conversation history containing thinking blocks, the model may receive inconsistent context without your knowledge. This header lets you detect those edits in production traffic before enforcement becomes mandatory for your account, preventing silent context corruption that could degrade model behavior.
WHAT TO DOAdd the thinking-binding-controls-2026-08-01 header to requests on Claude Fable 5.1, log all thinking_mismatch_allowed entries for one week, and audit any history-editing code paths that trigger them. If you find mismatches, either stop editing thinking blocks or set prefix_mismatch_behavior explicitly before the August 31 cutoff applies to your account.
CONFIDENCE 75% Primary source ↗ written by anthropic/claude-sonnet-4.5
Show the reasoning — raw diff, triage verdict, confidence
RAW DIFF
 https://platform.claude.com/docs/en/release-notes/overview#september-14-2026
 Mon, 14 Sep 2026 00:00:00 GMT
 
-The Messages API can now compact a conversation on demand on the Claude API, in beta with the compact-2026-09-04 beta header. Send the top-level compaction parameter, and the API returns a signed compaction block that summarizes the messages you sent. On later requests, send that block first, in place of those messages. You choose when to compact, the request can run in the background, and you can keep recent turns word for word after the summary. On models with preserved thinking, the thinking in those kept turns can stay valid.
+The Messages API can now compact a conversation on demand on the Claude API, in beta with the compact-2026-09-04 beta header. Send the top-level compaction parameter, and the API returns a signed compaction block that summarizes the messages you sent. On later requests, send that block first, in place of those messages. You choose when to compact, the request can run in the background, and you can keep recent turns word for word after the summary. On models with preserved thinking, the thinking in those kept turns can stay valid.
+With the thinking-binding-controls-2026-08-01 beta header, the input_transformations response field gains a second entry type, thinking_mismatch_allowed. It names a thinking block that failed the prefix check on a request where the API doesn't enforce that check: on Claude Fable 5.1, for example, a request from an account created before August 31, 2026, with prefix_mismatch_behavior unset. The block still reaches the model unchanged. Log these entries to find history edits in production traffic before you opt into enforcement. See Set the mismatch behavior and read input_transformations.
HOW IT WAS JUDGED
triage verdictMATERIAL at 0.92, needed 0.45
triage reasoningNew beta API feature with date-gated behavior and enforcement controls affects how engineers handle thinking blocks.
signalsnew beta feature with specific header (thinking-binding-controls-2026-08-01) · new response field type (thinking_mismatch_allowed) · new API behavior affecting model input handling · date-gated behavior (accounts created before August 31, 2026) · enforcement opt-in mechanism introduced · breaking change potential for existing thinking implementations
suppression
triage modelanthropic/claude-haiku-4.5 ($0.00000)
writer modelanthropic/claude-sonnet-4.5 ($0.00000)
ACTION NEEDED PRICINGLIMITS Anthropic pricing · 2026-09-21 23:44 UTC

Anthropic renamed Individual tier to Team, moved Claude Code to Max only

DOCheck your current Anthropic subscription tier and confirm whether you use Claude Code.
WHAT CHANGEDThe Individual pricing tier no longer exists; it has been renamed to Team. Claude Code, previously included in both Pro ($17/month) and Max (from $100/month), is now only available in the Max tier. The Pro tier description now lists Claude Code as a feature, but the Max tier no longer states 'Claude Code included' in its header.
WHY IT MATTERSIf you are on the Pro tier and use Claude Code, you will need to upgrade to Max (minimum $100/month, a 5.9x increase) to retain access. If you are on what was called the Individual tier, your tier name has changed but feature access appears unchanged.
WHAT TO DOCheck your current Anthropic subscription tier and confirm whether you use Claude Code. If you are on Pro and depend on Claude Code, budget for the upgrade to Max or identify alternative tooling before the change takes effect.
CONFIDENCE 75% Primary source ↗ written by anthropic/claude-sonnet-4.5
Show the reasoning — raw diff, triage verdict, confidence
RAW DIFF
-IndividualDeveloperTeam & EnterpriseAPI
+IndividualTeam & EnterpriseAPI
 
-Individual
-
 Free
 Try Claude
 
@@
 Create Artifacts
 
 Pro
-Claude Code included
 For everyday work
 
 $17
@@
 More usage*
 Hand off and schedule tasks
 Claude Design, Slides, Docs
+Claude Code
 Claude Science
 Projects
 More Claude models
 Claude in Chrome and Microsoft 365
 
 Max
-Claude Code included
 For people who work with Claude all day
 
 From $100
HOW IT WAS JUDGED
triage verdictMATERIAL at 0.92, needed 0.55
triage reasoningPricing tier restructuring and feature redistribution across tiers affects plan selection and cost.
signalspricing tier renamed: 'Individual' removed, 'Team' introduced · feature moved between tiers: 'Claude Code' removed from Pro description, added to Max description · tier structure simplified: 'IndividualDeveloperTeam' collapsed to 'Team' · feature availability changed: Claude Code no longer included in Pro tier
suppression
triage modelanthropic/claude-haiku-4.5 ($0.00000)
writer modelanthropic/claude-sonnet-4.5 ($0.00000)
WORTH KNOWING MODEL Azure Foundry model retirement schedule · 2026-09-21 23:43 UTC

gpt-realtime-2.1 and mini moved to GA on 2026-07-07

DOIf you are using either model in production, verify your deployment is receiving GA-level support and SLA coverage.
WHAT CHANGEDgpt-realtime-2.1 and gpt-realtime-2.1-mini changed status from Preview to GA effective 2026-07-07. Both models have a retirement date of 2027-06-25.
WHY IT MATTERSGA status means these models now carry production SLA guarantees and support commitments that Preview versions do not. Any production workloads currently using these models are now covered under standard Azure support terms.
WHAT TO DOIf you are using either model in production, verify your deployment is receiving GA-level support and SLA coverage. If you were blocking production use pending GA status, that gate is now cleared.
CONFIDENCE 85% Primary source ↗ written by anthropic/claude-sonnet-4.5
Show the reasoning — raw diff, triage verdict, confidence
RAW DIFF
 
 gpt-realtime-2.1
 2026-07-07
-Preview
+GA
 2027-06-25

 
 gpt-realtime-2.1-mini
 2026-07-07
-Preview
+GA
 2027-06-25

 
HOW IT WAS JUDGED
triage verdictMATERIAL at 0.92, needed 0.45
triage reasoningPreview-to-GA transition signals production-ready models with different support commitments and retirement timelines.
signalsmodel status change from Preview to GA · two models affected · GA status affects support SLA and production readiness
suppression
triage modelanthropic/claude-haiku-4.5 ($0.00000)
writer modelanthropic/claude-sonnet-4.5 ($0.00000)
FYI PRICING Anthropic pricing · 2026-09-21 23:43 UTC

Anthropic renamed tiers and moved Claude Code to Pro and Max

DOCheck your Anthropic account dashboard to confirm your current tier name matches the new structure.
WHAT CHANGEDThe 'Individual' and 'Developer' tier labels were removed from the pricing page. Claude Code, previously listed only under Pro, now appears under both Pro ($17/month) and Max (from $100/month). The Max tier description changed from 'For people who work with Claude all day' to the same phrasing.
WHY IT MATTERSIf you are on a legacy 'Individual' or 'Developer' plan, the tier name change may affect how you reference your subscription in billing systems or support requests. The Claude Code availability shift does not change what Pro users have access to, but clarifies that Max users also get it—relevant if you were evaluating Max specifically for coding features.
WHAT TO DOCheck your Anthropic account dashboard to confirm your current tier name matches the new structure. If you have billing automation or internal documentation referencing 'Individual' or 'Developer' tiers, update those labels to match the current naming.
CONFIDENCE 75% Primary source ↗ written by anthropic/claude-sonnet-4.5
Show the reasoning — raw diff, triage verdict, confidence
RAW DIFF
-IndividualDeveloperTeam & EnterpriseAPI
+IndividualTeam & EnterpriseAPI
 
-Individual
-
 Free
 Try Claude
 
@@
 Create Artifacts
 
 Pro
+Claude Code included
 For everyday work
 
 $17
@@
 More usage*
 Hand off and schedule tasks
 Claude Design, Slides, Docs
-Claude Code
 Claude Science
 Projects
 More Claude models
 Claude in Chrome and Microsoft 365
 
 Max
+Claude Code included
 For people who work with Claude all day
 
 From $100
HOW IT WAS JUDGED
triage verdictMATERIAL at 0.92, needed 0.55
triage reasoningClaude Code inclusion moved between pricing tiers, altering what features are available at each price point.
signalspricing tier restructuring · feature moved between tiers · Claude Code added to Pro tier · Claude Code removed from Max tier description · tier naming changed (Individual → removed, Developer removed) · feature availability changed across product lines
suppression
triage modelanthropic/claude-haiku-4.5 ($0.00000)
writer modelanthropic/claude-sonnet-4.5 ($0.00000)
WORTH KNOWING DEPRECATIONMODEL Azure Foundry model retirement schedule · 2026-09-21 23:43 UTC

gpt-4.1-nano retirement extended to 2027-04-14

DOCheck your deployment manifests and infrastructure-as-code for references to gpt-4.1-nano.
WHAT CHANGEDThe retirement date for gpt-4.1-nano moved from 2026-10-14 to 2027-04-14, a six-month extension. The model entered Legacy status on 2025-04-14.
WHY IT MATTERSIf you are running gpt-4.1-nano in production, you now have until mid-April 2027 to complete migration instead of mid-October 2026. This changes the timeline for any scheduled replacement work.
WHAT TO DOCheck your deployment manifests and infrastructure-as-code for references to gpt-4.1-nano. If found, update your migration plan to reflect the new 2027-04-14 deadline and communicate the revised timeline to stakeholders.
CONFIDENCE 95% Primary source ↗ written by anthropic/claude-sonnet-4.5
Show the reasoning — raw diff, triage verdict, confidence
RAW DIFF
 gpt-4.1-nano
 2025-04-14
 Legacy
-2026-10-14
+2027-04-14

 
 gpt-4o
HOW IT WAS JUDGED
triage verdictMATERIAL at 0.95, needed 0.45
triage reasoningRetirement deadline for gpt-4.1-nano moved from Oct 2026 to Apr 2027, affecting deployment planning.
signalsretirement date changed · sunset date extended by 6 months · model lifecycle impact
suppression
triage modelanthropic/claude-haiku-4.5 ($0.00000)
writer modelanthropic/claude-sonnet-4.5 ($0.00000)
WORTH KNOWING PRICINGLIMITS Anthropic pricing · 2026-09-21 23:43 UTC

Anthropic removes annual billing for Max tiers, limits Free projects to 5

DOIf you are on Max 5x or Max 20x with annual billing, check your renewal date and budget for monthly billing going forward.
WHAT CHANGEDMax 5x and Max 20x tiers now offer monthly billing only, down from 'Monthly and annual'. Free tier projects capped at 5, down from unlimited. Context window changed from fixed '200k' across all tiers to 'Up to 1M varies by model'. Claude Cowork feature removed entirely from all tiers.
WHY IT MATTERSTeams on annual Max contracts cannot renew at the annual rate when their term expires, forcing monthly billing at potentially higher effective cost. Free tier users with more than 5 projects will lose access to older projects or need to upgrade.
WHAT TO DOIf you are on Max 5x or Max 20x with annual billing, check your renewal date and budget for monthly billing going forward. If you use Free tier with more than 5 projects, audit which projects contain work you need to preserve before the cap takes effect.
CONFIDENCE 85% Primary source ↗ written by anthropic/claude-sonnet-4.5
Show the reasoning — raw diff, triage verdict, confidence
RAW DIFF
-IndividualDeveloperTeam & EnterpriseAPI
+IndividualTeam & EnterpriseAPI
 
-Individual
-
 Free
 Try Claude
 
@@
 Free for everyone
 
 Try Claude
-Chat on web, iOS, Android, and on your desktop
-Generate code and visualize data
-Write, edit, and create content
-Ability to search the web
+Chat on web, desktop, and mobile
+Search the web, create files, and run code
 Memory across conversations
-Create files and execute code
-Unlock more from Claude with desktop extensions
-Connect Slack and Google Workspace services
-Integrate any context or tool through connectors with remote MCP
-Extended thinking for complex work
+Connect your apps and tools
+Create Artifacts
 
 Pro
-For everyday productivity
+For everyday work
 
 $17
 Per month with annual subscription discount ($200 billed up front). $20 if billed monthly.
@@
 Try Claude
 Everything in Free, plus:
 More usage*
-Includes Claude Code
-Includes Claude Cowork
-Includes Claude Design
-Includes Claude Science
-Access to unlimited projects to organize chats and documents
-Access to Research
-Ability to use more Claude models
-Claude for Microsoft 365
+Hand off and schedule tasks
+Claude Design, Slides, Docs
+Claude Code
+Claude Science
+Projects
+More Claude models
+Claude in Chrome and Microsoft 365
 
 Max
-Get the most out of Claude
+For people who work with Claude all day
 
 From $100
 Per month
@@
 
 Features and capabilities
 FeaturesFreeProMax 5xMax 20x
-Chat on web, iOS, Android and Desktop
+@Claude
 
+No
+No
+No
+No
+Claude Code
+
+No
 Yes
 Yes
 Yes
-Yes
-Claude Code
+Claude Science
 
 No
 Yes
 Yes
 Yes
-Claude CoworkMore information
+Claude in Chrome
 
 No
 Yes
 Yes
 Yes
-Claude Design
+Claude for Microsoft 365
 
 No
 Yes
 Yes
 Yes
-Claude Science
+Claude for Microsoft Outlook
 
 No
 Yes
 Yes
 Yes
-@Claude
+Chat on web, iOS, Android and Desktop
 
+Yes
+Yes
+Yes
+Yes
+Claude Design, Slides, Docs
+
 No
-No
-No
-No
+Yes
+Yes
+Yes
 Ability to search the web
 
 Yes
 Yes
 Yes
 Yes
-Desktop extensions
+Create ArtifactsMore information
 
 Yes
 Yes
 Yes
 Yes
-Voice mode
+Desktop extensions
 
 Yes
 Yes
 Yes
 Yes
-Incognito chatsMore information
+Voice mode
 
 Yes
 Yes
 Yes
 Yes
-User preferences
+Incognito chatsMore information
 
 Yes
 Yes
 Yes
 Yes
-ArtifactsMore information
+User preferences
 
 Yes
 Yes
 Yes
 Yes
 Projects
-
-No
+Up to 5
 Yes
 Yes
 Yes
@@
 No
 No
 No
-Claude in Chrome
 
-No
-Yes
-Yes
-Yes
-Claude for Microsoft 365
-
-No
-Yes
-Yes
-Yes
-Claude for Microsoft Outlook
-
-No
-Yes
-Yes
-Yes
-
 Security and administration
 FeaturesFreeProMax 5xMax 20x
 Single sign-on (SSO) and domain capture
@@
 No
 No
 Billing cycle
-n/aMonthly and annualMonthly and annualMonthly and annual
+n/aMonthly and annualMonthlyMonthly
 Adding seats midterm
 n/an/an/an/a
 
@@
 Yes
 Yes
 Context windowMore information
-200k200k200k200k
+Up to 1Mvaries by modelUp to 1Mvaries by modelUp to 1Mvaries by modelUp to 1Mvaries by model
 Usage creditsMore information
 
 No
HOW IT WAS JUDGED
triage verdictMATERIAL at 0.92, needed 0.55
triage reasoningPricing tier restructuring, feature removals, context window expansion, and billing cycle restrictions materially affect platform capabilities and costs.
signalspricing tier renamed: 'Individual Developer' removed, 'Team' tier introduced · feature set reorganized with removals and additions across tiers · context window changed from fixed '200k' to 'Up to 1M varies by model' · billing cycle for Max tiers changed from 'Monthly and annual' to 'Monthly only' · projects limit changed from unlimited to 'Up to 5' in Free tier · Claude Cowork feature removed entirely · new features added: Claude Design/Slides/Docs, Claude in Chrome, Claude for Outlook
suppression
triage modelanthropic/claude-haiku-4.5 ($0.00000)
writer modelanthropic/claude-sonnet-4.5 ($0.00000)
ACTION NEEDED DEPRECATIONMODEL Azure Foundry model retirement schedule · 2026-09-21 23:42 UTC

Azure retires gpt-4.1-nano and gpt-image-1.5 six months earlier than announced

DOAudit Azure deployments for gpt-4.1-nano and gpt-image-1.5.
WHAT CHANGEDgpt-4.1-nano retirement moved from 2027-04-14 to 2026-10-14. gpt-image-1.5 retirement moved from 2027-06-16 to 2026-12-16. Both dates accelerated by six months.
WHY IT MATTERSAny deployments using these models will stop working on the new dates. Six months less migration runway means work scheduled for Q2 2027 must now complete by Q4 2026.
WHAT TO DOAudit Azure deployments for gpt-4.1-nano and gpt-image-1.5. If found, schedule migration to successor models before 2026-10-14 and 2026-12-16 respectively.
CONFIDENCE 95% Primary source ↗ written by anthropic/claude-sonnet-4.5
Show the reasoning — raw diff, triage verdict, confidence
RAW DIFF
 gpt-4.1-nano
 2025-04-14
 Legacy
-2027-04-14
+2026-10-14

 
 gpt-4o
@@
 gpt-image-1.5
 2025-12-16
 GA
-2027-06-16
+2026-12-16

 
 gpt-image-2
@@
 Cohere-command-a-plus-05-2026
 1
 Preview
-2026-10-13
-—
+2026-10-16
+coherelabs-command-a-plus-05-2026-fp81, coherelabs-command-a-plus-05-2026-bf161, coherelabs-command-a-plus-05-2026-w4a41
 
 embed-v-4-0
 1
@@


 
+1 Available through the Hugging Face collection, for managed compute deployment.
+
 DeepSeek
 
 Model
@@
 Suggest a fix?
 
 Last updated on
-2026-09-02
+2026-09-14
HOW IT WAS JUDGED
triage verdictMATERIAL at 0.95, needed 0.45
triage reasoningTwo model retirement dates moved forward by 6 months each, requiring engineering action.
signalsretirement date accelerated: gpt-4.1-nano from 2027-04-14 to 2026-10-14 (6 months earlier) · retirement date accelerated: gpt-image-1.5 from 2027-06-16 to 2026-12-16 (6 months earlier) · preview model date changed: Cohere-command-a-plus-05-2026 from 2026-10-13 to 2026-10-16 · model variant identifiers added for Cohere model · new deployment option noted for embed-v-4-0
suppression
triage modelanthropic/claude-haiku-4.5 ($0.00000)
writer modelanthropic/claude-sonnet-4.5 ($0.00000)
WORTH KNOWING APIMODEL Claude Platform release notes · 2026-09-21 23:42 UTC

Messages API adds on-demand conversation compaction in beta

DOTest the beta header `compact-2026-09-04` in a non-production environment with one long-running conversation flow.
WHAT CHANGEDThe Messages API now supports a `compaction` parameter (beta header `compact-2026-09-04`) that returns a signed compaction block summarizing sent messages. This block replaces the original messages in subsequent requests while preserving recent turns verbatim.
WHY IT MATTERSLong-running conversations currently hit context limits or incur cumulative token costs. This allows you to compress conversation history server-side while keeping recent exchanges intact, reducing both token usage and request size without losing conversation continuity.
WHAT TO DOTest the beta header `compact-2026-09-04` in a non-production environment with one long-running conversation flow. Measure token reduction and verify that responses remain coherent when using the compaction block instead of full message history.
CONFIDENCE 85% Primary source ↗ written by anthropic/claude-sonnet-4.5
Show the reasoning — raw diff, triage verdict, confidence
RAW DIFF
+## Claude Platform release notes — September 14, 2026
+https://platform.claude.com/docs/en/release-notes/overview#september-14-2026
+Mon, 14 Sep 2026 00:00:00 GMT
+
+The Messages API can now compact a conversation on demand on the Claude API, in beta with the compact-2026-09-04 beta header. Send the top-level compaction parameter, and the API returns a signed compaction block that summarizes the messages you sent. On later requests, send that block first, in place of those messages. You choose when to compact, the request can run in the background, and you can keep recent turns word for word after the summary. On models with preserved thinking, the thinking in those kept turns can stay valid.
HOW IT WAS JUDGED
triage verdictMATERIAL at 0.92, needed 0.45
triage reasoningNew API capability with beta header and parameter changes how developers structure conversation requests.
signalsnew API feature announced · beta header introduced (compact-2026-09-04) · new top-level parameter (compaction) · changes conversation handling workflow · affects request structure and API contract
suppression
triage modelanthropic/claude-haiku-4.5 ($0.00000)
writer modelanthropic/claude-sonnet-4.5 ($0.00000)
ACTION NEEDED DEPRECATIONMODELAPI OpenAI deprecations · 2026-09-12 10:13 UTC

GPT-5.4-Cyber deprecated, removal October 1, 2026

DOGrep your codebase for 'gpt-5.4-cyber', update all references to 'gpt-5.6-cyber', test the replacement model's output against your use cases, and deploy before October 1.
WHAT CHANGEDOpenAI announced on September 11, 2026 that gpt-5.4-cyber is deprecated and will be removed from the API on October 1, 2026. The replacement model is gpt-5.6-cyber.
WHY IT MATTERSAny code calling gpt-5.4-cyber will fail after October 1, 2026. You have 19 days to complete the migration.
WHAT TO DOGrep your codebase for 'gpt-5.4-cyber', update all references to 'gpt-5.6-cyber', test the replacement model's output against your use cases, and deploy before October 1.
CONFIDENCE 95% Primary source ↗ written by anthropic/claude-sonnet-4.5
Show the reasoning — raw diff, triage verdict, confidence
RAW DIFF
 
 Upcoming deprecations are listed below, with the most recent announcements at the top.
 
+2026-09-11: GPT-5.4-Cyber
+
+The gpt-5.4-cyber model is deprecated and will be removed from the API on October 1, 2026. Migrate to gpt-5.6-cyber before the shutdown date.
+
+Shutdown dateModel / systemRecommended replacement
+Oct 1, 2026gpt-5.4-cybergpt-5.6-cyber
+
 2026-08-26: Transcription models
 
 On August 26, 2026, we notified developers using whisper-1, gpt-4o-transcribe, gpt-4o-mini-transcribe, and gpt-4o-transcribe-diarize of their deprecation and removal from the API on February 26, 2027.
@@
 
 The Realtime API Beta was deprecated and removed from the API on May 12, 2026.
 
-There are a few key differences between the interfaces in the Realtime beta API and the released GA API. See the migration guide for the current GA interface and related Realtime docs.
+The interfaces in the Realtime beta API and the released GA API have a few key differences. See the migration guide for the current GA interface and related Realtime docs.
 
 Shutdown dateModel / systemRecommended replacement
 2026‐05‐12OpenAI-Beta: realtime=v1Realtime API
HOW IT WAS JUDGED
triage verdictMATERIAL at 0.95, needed 0.45
triage reasoningNew deprecation entry for gpt-5.4-cyber with October 2026 shutdown date requires migration action.
signalsnew model deprecation announced · future shutdown date (Oct 1, 2026) · migration path specified (gpt-5.4-cyber → gpt-5.6-cyber) · model removal from API · sentence reword is cosmetic noise
suppression
triage modelanthropic/claude-haiku-4.5 ($0.00000)
writer modelanthropic/claude-sonnet-4.5 ($0.00000)
ACTION NEEDED DEPRECATIONMODELAPI Azure Foundry model retirement schedule · 2026-09-12 03:31 UTC

Azure o1/o3 family retirement consolidated to 2026-11-19

DOGrep your codebase for model identifiers o1-pro, o3, o3-deep-research, o3-pro, o3-mini, o4-mini.
WHAT CHANGEDo1-pro, o3, o3-deep-research, and o3-pro moved from GA to Deprecated status. All o1/o3 models now retire 2026-11-19 (previously scattered between 2026-10-01 and 2026-12-26). o3-mini and o4-mini successor changed from o4-mini to gpt-5.6-terra. Fine-tuning retirement for o4-mini shifted from 2027-04-16 to 2027-05-19.
WHY IT MATTERSIf you are running o1-pro, o3, o3-deep-research, or o3-pro in production, they are now deprecated with 9 weeks until retirement. The consolidated sunset date means you cannot stagger migrations. The successor model change means existing migration plans targeting o4-mini must be rewritten to target gpt-5.6-terra or gpt-5.6-sol.
WHAT TO DOGrep your codebase for model identifiers o1-pro, o3, o3-deep-research, o3-pro, o3-mini, o4-mini. If any are in use, schedule migration to gpt-5.6-sol (for o1/o3 reasoning models) or gpt-5.6-terra (for o3-mini/o4-mini) before 2026-11-19. If you have fine-tuned o4-mini models, note the new training retirement date of 2027-05-19.
CONFIDENCE 95% Primary source ↗ written by anthropic/claude-sonnet-4.5
Show the reasoning — raw diff, triage verdict, confidence
RAW DIFF
 o1
 2024-12-17
 Deprecated
-2026-10-21
+2026-11-19
 gpt-5.6-sol
 
 o1-pro
 2025-03-19
-GA
-2026-10-21
+Deprecated
+2026-11-19
 gpt-5.6-sol
 
 o3
 2025-04-16
-GA
-2026-10-21
+Deprecated
+2026-11-19
 gpt-5.6-sol
 
 o3-deep-research
 2025-06-26
-GA
-2026-12-26
-—
+Deprecated
+2026-11-19
+gpt-5.6-sol
 
 o3-mini
 2025-01-31
 Deprecated
-2026-10-01
-o4-mini
+2026-11-19
+gpt-5.6-terra
 
 o3-pro
 2025-06-10
-GA
-2026-12-17
-—
+Deprecated
+2026-11-19
+gpt-5.6-sol
 
 o4-mini
 2025-04-16
 Deprecated
-2026-10-16
-—
+2026-11-19
+gpt-5.6-terra
 
 sora-2
 2025-10-06
@@
 
 o4-mini
 2025-04-16
-No earlier than 2027-04-161
-2027-10-16
+No earlier than 2027-05-191
+2027-11-19
 
 1 For existing customers only. Otherwise, training retirement occurs at base model retirement.
 
HOW IT WAS JUDGED
triage verdictMATERIAL at 0.98, needed 0.45
triage reasoningMultiple model deprecations accelerated and status changes from GA to Deprecated affect deployment planning.
signalsmultiple model deprecation dates shifted forward by ~30 days · models changed from GA to Deprecated status · o1-pro, o3, o3-deep-research, o3-pro transitioned from GA to Deprecated · successor model assignments changed (o3-mini now maps to gpt-5.6-terra instead of o4-mini) · training retirement dates shifted (2027-04-16 → 2027-05-19, 2027-10-16 → 2027-11-19) · consolidation: multiple models now share single sunset date 2026-11-19
suppression
triage modelanthropic/claude-haiku-4.5 ($0.00000)
writer modelanthropic/claude-sonnet-4.5 ($0.00000)
WORTH KNOWING APIMODEL Claude Platform release notes · 2026-09-11 03:26 UTC

Claude Managed Agents adds auto permission mode and live terminal attachment

DOReview your agent permission policy configurations and decide whether to adopt auto mode or continue with existing policies.
WHAT CHANGEDClaude Managed Agents now supports an 'auto' permission policy mode where the server evaluates each tool call and either runs it, denies it, or pauses for approval. The agent.tool_use and agent.mcp_tool_use events now include an 'evaluation' field reporting how each call was evaluated. The ant CLI adds 'ant beta:sessions connect' command to attach a terminal to live agent sessions, with an optional --web flag to serve the session viewer locally.
WHY IT MATTERSIf you are running Claude Managed Agents with custom permission policies, the new auto mode changes how tool call authorization works—the server now makes evaluation decisions instead of requiring you to implement all logic client-side. The new evaluation field in events means your logging or monitoring code may need updates to capture this data. The CLI command provides a new debugging path that bypasses your application's session handling.
WHAT TO DOReview your agent permission policy configurations and decide whether to adopt auto mode or continue with existing policies. Update any event handlers that parse agent.tool_use or agent.mcp_tool_use events to handle the new evaluation field. Test the ant beta:sessions connect command in development to understand how it interacts with your session management.
CONFIDENCE 75% Primary source ↗ written by anthropic/claude-sonnet-4.5
Show the reasoning — raw diff, triage verdict, confidence
RAW DIFF
+## Claude Platform release notes — September 10, 2026
+https://platform.claude.com/docs/en/release-notes/overview#september-10-2026
+Thu, 10 Sep 2026 00:00:00 GMT
+
+Claude Managed Agents permission policies now include auto: the server evaluates each agent or MCP tool call and runs it, denies it, or pauses for your approval. agent.tool_use and agent.mcp_tool_use events report how each call was evaluated in an evaluation field alongside evaluated_permission. See Let the server evaluate each call with auto.
+The ant CLI adds ant beta:sessions connect, which attaches your terminal to a Claude Managed Agents session. You can follow the session live, send messages, and allow or deny tool calls that are waiting for approval. Pass --web to serve the Claude Console's session viewer locally and open the session there instead. See Connect to a Managed Agents session from your terminal.
HOW IT WAS JUDGED
triage verdictMATERIAL at 0.92, needed 0.45
triage reasoningNew agent permission modes, API fields, and CLI commands affect how teams integrate and control Claude Managed Agents.
signalsnew feature: auto permission policy mode for Claude Managed Agents · new API field: evaluation field in agent.tool_use and agent.mcp_tool_use events · new CLI command: ant beta:sessions connect · new capability: terminal attachment to live agent sessions · new parameter: --web flag for local console serving
suppression
triage modelanthropic/claude-haiku-4.5 ($0.00000)
writer modelanthropic/claude-sonnet-4.5 ($0.00000)
WORTH KNOWING MODELDEPRECATION Azure Foundry model retirement schedule · 2026-09-10 20:30 UTC

Two image models added to retirement schedule, sunset 9 September 2027

DOCheck your image generation endpoints for references to gpt-image-2.5-flare or gpt-image-2.5-sunburst.
WHAT CHANGEDgpt-image-2.5-flare and gpt-image-2.5-sunburst reached GA on 9 September 2026 and are scheduled for retirement on 9 September 2027. Both models now appear on the Azure Foundry model retirement schedule.
WHY IT MATTERSIf you adopt either model after GA, you have exactly one year before forced migration. The retirement date is fixed at announcement, which is unusually short for a GA model lifecycle.
WHAT TO DOCheck your image generation endpoints for references to gpt-image-2.5-flare or gpt-image-2.5-sunburst. If you are evaluating these models, factor the 9 September 2027 cutoff into your adoption decision now.
CONFIDENCE 85% Primary source ↗ written by anthropic/claude-sonnet-4.5
Show the reasoning — raw diff, triage verdict, confidence
RAW DIFF
 2027-10-21

 
+gpt-image-2.5-flare
+2026-09-09
+GA
+2027-09-09
+—
+
+gpt-image-2.5-sunburst
+2026-09-09
+GA
+2027-09-09
+—
+
 gpt-realtime
 2025-08-28
 GA
HOW IT WAS JUDGED
triage verdictMATERIAL at 0.95, needed 0.45
triage reasoningNew models with defined sunset dates added to retirement schedule; engineering teams must track these timelines.
signalstwo new models added to retirement schedule · future sunset dates specified (2027-09-09) · GA status indicates production-ready models · retirement schedule is the core tracked artifact
suppression
triage modelanthropic/claude-haiku-4.5 ($0.00000)
writer modelanthropic/claude-sonnet-4.5 ($0.00000)
FYI APIMODEL Claude Platform release notes · 2026-09-09 20:34 UTC

Per-message effort changes now available on Google Cloud Claude models

DOIf you use Claude on Google Cloud and want per-message effort control, test the mid-conversation-output-config-2026-07-01 header with one of the three supported models i…
WHAT CHANGEDPer-message effort changes (beta) are now supported on Google Cloud for Claude Fable 5.1, Claude Mythos 5.1, and Claude Opus 5. This requires the mid-conversation-output-config-2026-07-01 beta header, matching the existing implementation on other platforms.
WHY IT MATTERSIf you run Claude on Google Cloud and want to adjust model effort mid-conversation (for example, switching between speed and quality), you can now do so without changing platforms. Previously this beta feature was unavailable on Google Cloud deployments.
WHAT TO DOIf you use Claude on Google Cloud and want per-message effort control, test the mid-conversation-output-config-2026-07-01 header with one of the three supported models in a non-production environment to verify the behavior matches your use case.
CONFIDENCE 85% Primary source ↗ written by anthropic/claude-sonnet-4.5
Show the reasoning — raw diff, triage verdict, confidence
RAW DIFF
 https://platform.claude.com/docs/en/release-notes/overview#september-3-2026
 Thu, 03 Sep 2026 00:00:00 GMT
 
-Version 1.30.0 of the ant CLI adds ant apply, which creates and updates agents, environments, skills, memory stores, and deployments from files in your repository. Describe each resource in a file, run ant apply, and approve the plan it prints. Commit the claude-lock.json lockfile it writes so that later runs, on your machine or in CI, update the same resources instead of creating new ones. See Manage resources as code with ant apply.
+Version 1.30.0 of the ant CLI adds ant apply, which creates and updates agents, environments, skills, memory stores, and deployments from files in your repository. Describe each resource in a file, run ant apply, and approve the plan it prints. Commit the claude-lock.json lockfile it writes so that later runs, on your machine or in CI, update the same resources instead of creating new ones. See Manage resources as code with ant apply.
+Per-message effort changes, in beta, are also available on Google Cloud for Claude Fable 5.1, Claude Mythos 5.1, and Claude Opus 5, with the same mid-conversation-output-config-2026-07-01 beta header.
HOW IT WAS JUDGED
triage verdictMATERIAL at 0.72, needed 0.45
triage reasoningNew beta feature (per-message effort changes) now available on Google Cloud for specific Claude models with required API header.
signalsnew feature announcement · beta feature availability on new platform · new models listed with feature support · specific API header requirement mentioned
suppression
triage modelanthropic/claude-haiku-4.5 ($0.00000)
writer modelanthropic/claude-sonnet-4.5 ($0.00000)
ACTION NEEDED PRICINGLIMITS Anthropic pricing · 2026-09-04 20:23 UTC

Research feature removed from Pro tier pricing page

DOLog into an active Pro account and verify whether Research is still accessible in the product.
WHAT CHANGEDThe pricing comparison table no longer lists 'Access to Research' as a Pro tier feature. The row showing 'Research' with 'No' for Free tier has been removed entirely.
WHY IT MATTERSIf your team or users rely on Research access through Pro subscriptions, this removal suggests the feature may no longer be available at that tier, potentially requiring a plan upgrade or eliminating access entirely.
WHAT TO DOLog into an active Pro account and verify whether Research is still accessible in the product. If it is missing, contact Anthropic support to confirm whether this is a pricing page error or an actual feature removal, and determine what tier now includes Research.
CONFIDENCE 75% Primary source ↗ written by anthropic/claude-sonnet-4.5
Show the reasoning — raw diff, triage verdict, confidence
RAW DIFF
 Includes Claude Design
 Includes Claude Science
 Access to unlimited projects to organize chats and documents
-Access to Research
 Ability to use more Claude models
 Claude for Microsoft 365
 
@@
 Yes
 Yes
 Yes
-Research
-
-No
-Yes
-Yes
-Yes
 Memory
 
 Yes
HOW IT WAS JUDGED
triage verdictMATERIAL at 0.85, needed 0.55
triage reasoningResearch feature access removed from a pricing tier, affecting what customers can do.
signalsfeature removed from pricing tier · Research access removed · tier comparison table altered
suppression
triage modelanthropic/claude-haiku-4.5 ($0.00000)
writer modelanthropic/claude-sonnet-4.5 ($0.00000)
WORTH KNOWING PRICING Anthropic pricing · 2026-09-03 20:37 UTC

Anthropic removed Team and Enterprise pricing from public page

DOIf you have an active RFP or budget proposal referencing the removed pricing, screenshot your current contract or contact Anthropic sales to confirm whether published ra…
WHAT CHANGEDThe pricing page no longer displays Team plan pricing ($20-$25/seat standard, $100-$125/seat premium) or Enterprise plan details ($20/seat + API usage). The Education plan section was removed entirely. API pricing tables for all models (Fable 5.1, Opus 5, Sonnet 5, Haiku 4.5) and legacy models are no longer visible in the public diff. The feature comparison now shows only Free, Pro, Max 5x, and Max 20x tiers.
WHY IT MATTERSIf you are evaluating Team or Enterprise plans, you can no longer see pricing or feature details without contacting sales. If you are budgeting for multi-seat deployments or comparing API costs across models, the reference data is no longer publicly available. Existing customers are unaffected, but new procurement requires a sales conversation where self-serve comparison was previously possible.
WHAT TO DOIf you have an active RFP or budget proposal referencing the removed pricing, screenshot your current contract or contact Anthropic sales to confirm whether published rates still apply. If you are comparing API costs, check whether you have the model pricing cached locally or in your cost model; if not, request a rate card from your account team before the next planning cycle.
CONFIDENCE 85% Primary source ↗ written by anthropic/claude-sonnet-4.5
Show the reasoning — raw diff, triage verdict, confidence
RAW DIFF
-Pricing
+IndividualTeam & EnterpriseAPI
 
-Individual
-
-Team & Enterprise
-
-API
-
-Active
-
 Free
 Try Claude
 
 $0
 Free for everyone
 
-Try ClaudeTry Claude
-
+Try Claude
 Chat on web, iOS, Android, and on your desktop
 Generate code and visualize data
 Write, edit, and create content
@@
 $17
 Per month with annual subscription discount ($200 billed up front). $20 if billed monthly.
 
-Try ClaudeTry Claude
-
+Try Claude
 Everything in Free, plus:
 More usage*
 Includes Claude Code
@@
 From $100
 Per month
 
-Try ClaudeTry Claude
-
+Try Claude
 Everything in Pro, plus:
 Choose 5x or 20x more usage than Pro*
 Higher output limits for all tasks
@@
 Priority access at high traffic times
 
 Usage limits apply. Prices shown don’t include applicable tax. Price and plans are subject to change at Anthropic's discretion.
-
 Usage limits apply. Price and plans are subject to change at Anthropic's discretion.
 
-Compare features across plans
-
 Search
 
 Free
+Try Claude
 
-Try ClaudeTry Claude
-
 Pro
+Try Claude
 
-Try ClaudeTry Claude
-
 Max 5x
+Try Claude
 
-Try ClaudeTry Claude
-
 Max 20x
+Try Claude
 
-Try ClaudeTry Claude
-
 Features and capabilities
-
 FeaturesFreeProMax 5xMax 20x
 Chat on web, iOS, Android and Desktop
 
+Yes
+Yes
+Yes
+Yes
 Claude Code
 
-Claude Cowork
+No
+Yes
+Yes
+Yes
+Claude CoworkMore information
 
+No
+Yes
+Yes
+Yes
 Claude Design
 
+No
+Yes
+Yes
+Yes
 Claude Science
 
+No
+Yes
+Yes
+Yes
 @Claude
 
+No
+No
+No
+No
 Ability to search the web
 
+Yes
+Yes
+Yes
+Yes
 Desktop extensions
 
+Yes
+Yes
+Yes
+Yes
 Voice mode
 
-Incognito chats
+Yes
+Yes
+Yes
+Yes
+Incognito chatsMore information
 
+Yes
+Yes
+Yes
+Yes
 User preferences
 
-Artifacts
+Yes
+Yes
+Yes
+Yes
+ArtifactsMore information
 
+Yes
+Yes
+Yes
+Yes
 Projects
 
+No
+Yes
+Yes
+Yes
 Project sharing and collaboration
 
-Create and edit files with code execution
+No
+No
+No
+No
+Create and edit files with code executionMore information
 
+Yes
+Yes
+Yes
+Yes
 Research
 
+No
+Yes
+Yes
+Yes
 Memory
 
-Skills
+Yes
+Yes
+Yes
+Yes
+SkillsMore information
 
-Connectors
+Yes
+Yes
+Yes
+Yes
+ConnectorsMore information
 
+Yes
+Yes
+Yes
+Yes
 Web search
 
-Enterprise search
+Yes
+Yes
+Yes
+Yes
+Enterprise searchMore information
 
+No
+No
+No
+No
 Claude in Chrome
 
+No
+Yes
+Yes
+Yes
 Claude for Microsoft 365
 
+No
+Yes
+Yes
+Yes
 Claude for Microsoft Outlook
 
-Security and administration
+No
+Yes
+Yes
+Yes
 
+Security and administration
 FeaturesFreeProMax 5xMax 20x
 Single sign-on (SSO) and domain capture
 
+No
+No
+No
+No
 Central billing and administration
 
+No
+No
+No
+No
 Admin controls for remote and local connectors
 
+No
+No
+No
+No
 Enterprise deployment for the Claude desktop app
 
+No
+No
+No
+No
 Role-based access
 
+No
+No
+No
+No
 System for Cross-domain Identity Management (SCIM)
 
+No
+No
+No
+No
 Audit logs
 
+No
+No
+No
+No
 Usage analytics
 
+No
+No
+No
+No
 Compliance API
 
+No
+No
+No
+No
 HIPAA-ready offering
 
+No
+No
+No
+No
 Custom data retention controls
 
+No
+No
+No
+No
 Organization wide skills deployment
 
-Payment options
+No
+No
+No
+No
 
+Payment options
 FeaturesFreeProMax 5xMax 20x
 Credit card
 n/a
-
+Yes
+Yes
+Yes
 ACH
 
+No
+No
+No
+No
 Invoicing / net terms
 
+No
+No
+No
+No
 Billing cycle
-n/a
-
-Monthly and annual
-
-Monthly and annual
-
-Monthly and annual
-
+n/aMonthly and annualMonthly and annualMonthly and annual
 Adding seats midterm
-n/a
+n/an/an/an/a
 
-n/a
-
-n/a
-
-n/a
-
 Models and usage
-
 FeaturesFreeProMax 5xMax 20x
-Fable
+FableMore information
 
-Usage credits
-
-50% of weekly limits*
-
-50% of weekly limits*
-
+NoUsage credits50% of weekly limits*50% of weekly limits*
 Opus
 
+No
+Yes
+Yes
+Yes
 Sonnet
 
+Yes
+Yes
+Yes
+Yes
 Haiku
 
-Context window
+Yes
+Yes
+Yes
+Yes
+Context windowMore information
+200k200k200k200k
+Usage creditsMore information
 
-200k
-
-200k
-
-200k
-
-200k
-
-Usage credits
-
+No
+Yes
+Yes
+Yes
 Priority access at high traffic times
 
+No
+No
+Yes
+Yes
 User and organizational level spend controls
 
-Model training
+No
+No
+No
+No
+Model trainingMore information
+Opt-outOpt-outOpt-outOpt-out
 
-Opt-out
+Plans and usageBilling and paymentsManaging your plan
 
-Opt-out
-
-Opt-out
-
-Opt-out
-
-Team
-For teams of 2 to 150
-
-Get Team planGet Team plan
-
-Standard seat
-All Claude features, plus more usage than Pro*
-
-$20
-
-Per seat / month if billed annually. $25 if billed monthly.
-
-Premium seat
-5x more usage than standard seats*
-
-$100
-
-Per seat / month if billed annually. $125 if billed monthly.
-
-Includes Claude Code and Claude Cowork
-Includes Claude Design
-Includes Claude Science
-Connect Microsoft 365, @Claude, and more
-Enterprise search across your organization
-Central billing and administration
-Single sign-on (SSO)
-Admin controls for remote and local connectors
-Enterprise deployment for the Claude desktop app
-No model training on your content by default
-Mix and match seat types
-
-Enterprise
-For large businesses operating at scale
-
-Get Enterprise planGet Enterprise plan
-
-Chat with buying specialistChat with buying specialist
-
-Seat price + usage at API rates
-
-$20/seat. Usage cost scales with model and task.
-
-All Team plan features, plus:
-Admins set user and org spend limits
-Role-based access with fine grained permissioning
-System for Cross-domain Identity Management (SCIM)
-Audit logs
-Compliance API for observability and monitoring
-Custom data retention controls
-Network-level access control
-IP allowlisting
-HIPAA-ready offering available
-Claude Security (beta)
-
-Usage limits apply. Prices shown don’t include applicable tax. Price and plans are subject to change at Anthropic's discretion.
-
-Usage limits apply. Price and plans are subject to change at Anthropic's discretion.
-
-Education plan
-
-Get a comprehensive university‐wide plan for an institution, including its students, faculty, and staff.
-
-Learn moreLearn more
-
-Student and faculty access
-
-Comprehensive access for all university members at discounted rates
-
-Academic research and learning mode
-
-Dedicated API credits and educational features for student learning
-
-Training and enablement
-
-Resources for successful adoption across your institution
-
-Compare features across plans
-
-Search
-
-Team
-
-Create planCreate plan
-
-Enterprise (self-serve)
-
-Create planCreate plan
-
-Enterprise (sales-assisted)
-
-Contact salesContact sales
-
-Features and capabilities
-
-FeaturesTeamEnterprise (self-serve)Enterprise (sales-assisted)
-Chat on web, iOS, Android and Desktop
-
-Claude Code
-
-Claude Cowork
-
-Claude Design
-
-Claude Science
-
-@Claude
-
-Claude Security
-
-Ability to search the web
-
-Desktop extensions
-
-Voice mode
-
-Incognito chats
-
-User preferences
-
-Artifacts
-
-Projects
-
-Project sharing and collaboration
-
-Create and edit files with code execution
-
-Research
-
-Memory
-
-Skills
-
-Connectors
-
-Web search
-
-Enterprise search
-
-Claude in Chrome
-
-Claude for Microsoft 365
-
-Claude for Microsoft Outlook
-
-Security and administration
-
-FeaturesTeamEnterprise (self-serve)Enterprise (sales-assisted)
-Single sign-on (SSO)
-
-Domain verification
-
-Restrict org creation
-
-Migrate accounts using your domains
-
-Central billing and administration
-
-Admin controls for remote and local connectors
-
-Enterprise deployment for the Claude desktop app
-
-Usage analytics
-
-Organization wide skills deployment
-
-Domain capture
-
-Role-based access
-
-System for Cross-domain Identity Management (SCIM)
-
-Audit logs
-
-Compliance API
-
-Custom data retention controls
-
-Set org instructions
-
-HIPAA-ready offering
-
-Inference hooks
-
-Payment options
-
-FeaturesTeamEnterprise (self-serve)Enterprise (sales-assisted)
-Credit card
-
-ACH
-
-Invoicing / net terms
-
-Billing cycle
-Monthly and annual
-
-Annual
-
-Annual
-
-Adding seats midterm
-
-Partnership
-
-FeaturesTeamEnterprise (self-serve)Enterprise (sales-assisted)
-AWS Marketplace availability
-
-Consultation
-
-Tiered incentives on committed spend
-
-Trials
-
-Customer success support at certain spend thresholds
-
-Models and usage
-
-FeaturesTeamEnterprise (self-serve)Enterprise (sales-assisted)
-Fable
-
-Opus
-
-Sonnet
-
-Haiku
-
-Context window
-
-200k
-
-500k
-
-on default model
-500k
-
-on default model
-
-Extra usage
-
-n/a
-
-n/a
-
-Priority access at high traffic times
-
-User and organizational level spend controls
-
-Model training
-
-None by default
-
-None by default
-
-None by default
-
-Latest models
-
-Contact salesContact sales
-
-Start buildingStart building
-
-Save 50% with batch processing.
-Learn more
-Batch processing
-
-Fable 5.1
-Next generation intelligence for long-running agents
-
-Input
-$10 / MTok
-
-Output
-$50 / MTok
-
-Prompt caching
-
-Read
-$0.25 / MTok
-
-Write
-$12.50 / MTok
-
-Opus 5
-Ideal for complex agentic coding and enterprise work
-
-Input
-$5 / MTok
-
-Output
-$25 / MTok
-
-Prompt caching
-
-Read
-$0.50 / MTok
-
-Write
-$6.25 / MTok
-
-Sonnet 5
-High-performance model for coding and agents
-
-Input
-$2 / MTok
-
-Output
-$10 / MTok
-
-Prompt caching
-
-Read
-$0.20 / MTok
-
-Write
-$2.50 / MTok
-
-Haiku 4.5
-Fastest, most cost-efficient model
-
-Input
-$1 / MTok
-
-Output
-$5 / MTok
-
-Prompt caching
-
-Read
-$0.10 / MTok
-
-Write
-$1.25 / MTok
-
-For workloads that need to run in the US, US-only inference is available at 1.1x pricing for input and output tokens. Learn more.
-
-Get up to 2.5x faster speeds with fast mode for Opus 5 at 2x standard pricing. Learn more.
-
-Prompt caching pricing reflects 5-minute TTL. Learn about extended prompt caching.
-
-Explore detailed pricingExplore detailed pricing
-
-Pricing for Claude Platform features
-
-Get more out of Claude with advanced
features and capabilities.
-
-Learn moreLearn more
-
-Managed Agents
-
-Build and deploy agents at scale with a suite of composable APIs. Standard token rates apply.
-
-Cost
-
-$0.08 per session-hour for active runtime
-
-Web search
-
-Give Claude access to the latest information from the web. Doesn’t include input and output tokens required to process requests.
-
-Cost
-
-$10 / 1K searches
-
-Code execution
-
-Run Python code in a sandboxed environment for advanced data analysis. 50 free hours of usage daily per organization.
-
-Additional hours
-
-$0.05 per hour per container
-
-Service tiers
-
-Balance availability, performance, and predictable costs based on your needs.
-
-Learn moreLearn more
-
-Contact salesContact sales
-
-Standard
-
-Default tier for both piloting and scaling everyday use cases
-
-Batch
-
-For asynchronous workloads that can be processed together for better efficiency
-
-Legacy models
-
-Learn moreLearn more
-
-Explore detailed pricingExplore detailed pricing
-
-Fable 5
-
-Input
-$10 / MTok
-
-Output
-$50 / MTok
-
-Prompt caching
-
-Read
-$1 / MTok
-
-Write
-$12.50 / MTok
-
-Opus 4.8
-
-Input
-$5 / MTok
-
-Output
-$25 / MTok
-
-Prompt caching
-
-Read
-$0.50 / MTok
-
-Write
-$6.25 / MTok
-
-Save 50% with batch processing.
-Learn more
-Batch processing
-
-Sonnet 4.6
-
-Input
-$3 / MTok
-
-Output
-$15 / MTok
-
-Prompt caching
-
-Read
-$0.30 / MTok
-
-Write
-$3.75 / MTok
-
-Opus 4.7
-
-Input
-$5 / MTok
-
-Output
-$25 / MTok
-
-Prompt caching
-
-Read
-$0.50 / MTok
-
-Write
-$6.25 / MTok
-
-Opus 4.6
-
-Input
-$5 / MTok
-
-Output
-$25 / MTok
-
-Prompt caching
-
-Read
-$0.50 / MTok
-
-Write
-$6.25 / MTok
-
-Sonnet 4.5
-
-Input
-$3 / MTok
-
-Output
-$15 / MTok
-
-Prompt caching
-
-Read
-$0.30 / MTok
-
-Write
-$3.75 / MTok
-
-Opus 4.5
-
-Input
-$5 / MTok
-
-Output
-$25 / MTok
-
-Prompt caching
-
-Read
-$0.50 / MTok
-
-Write
-$6.25 / MTok
-
-Opus 4.1
-
-Input
-$15 / MTok
-
-Output
-$75 / MTok
-
-Prompt caching
-
-Read
-$1.50 / MTok
-
-Write
-$18.75 / MTok
-
-Prompt caching pricing reflects 5-minute TTL. Learn about extended prompt caching.
-
-FAQ
-
 Plans and usage
-
-Billing and payments
-
-Managing your plan
-
-Active
-
-Plans and usage
-
 What do I get with Claude Pro?
 
-The Pro plan gives you everything in a Free plan with more usage and the full set of Claude capabilities. That includes Claude Code, Claude Cowork, Claude Design, along with projects to organize your chats and documents, access to more Claude models, and Claude for Microsoft 365. You can choose a monthly or annual subscription.
-
 How is Claude Max different from Pro?
 
-The Max plan is built for people who work with Claude throughout the day and want longer, uninterrupted sessions. You get everything in Pro, plus more usage: choose from 5x or 20x the usage of Pro per 5-hour session. Max also gives you higher output limits. Both options are billed monthly. See the cards above for current pricing.
-
 What are the usage limits on each plan, and what happens when I hit them?
 
-Every plan has usage limits that reset on a rolling five-hour session window, and paid plans add weekly limits on top. Your activity across Claude on web, desktop, mobile, and Claude Code all draws from the same pool. How much you can do depends on the length and complexity of your conversations, the model you choose, and the features you use, so there's no fixed message count. Free covers everyday questions. Pro gives you at least 5x more usage per 5-hour session than Free. Max gives you 5x or 20x more usage per 5-hour session than Pro. On Team plans, Standard seats give more than Pro and Premium seats give 5x more than Standard. To manage capacity and make sure all users have fair access, we may limit your usage in other ways, such as weekly and monthly caps or model and feature usage, at our discretion. When you reach a limit, you can wait for it to reset, move to a higher plan, or, on paid plans, turn on usage credits to keep working at standard API rates. You can see where you stand anytime in Settings > Usage.
-
 Is Claude Code included in my plan?
 
-Claude Code is included in all paid plans. It shares the same usage limits as the rest of your plan, so your work in the terminal and your chats draw from one pool. For heavy coding sessions, you can also switch to pay-as-you-go API credits through a Console account.
-
-How much does the Claude Enterprise plan cost?
-
-The Claude Enterprise plan is built for large businesses operating at scale. Pricing is $20 per seat per month plus usage billed at API rates, so cost scales with the models and tasks your team runs. Enterprise is billed annually and includes everything in Team plus advanced security and admin controls, including SCIM, audit logs, custom data retention, and role-based access. You can get started self-serve or contact sales for a tailored quote.
-
-PrevPrev
-
-NextNext
-
-Billing and payments
-
-Can I pay annually? Does it cost less than if I pay monthly?
-
-Yes, annual plans are designed to cost less than monthly subscriptions. Annual subscriptions are available for Pro and Team plans. Enterprise plans are only available as annual subscriptions.
-When you choose to pay annually, you're billed once up front for the year. If you're already on a monthly plan, you can switch to annual in Settings > Billing, and any unused time is credited toward your first annual invoice. See the steps for Pro and Team.
-
-Does Claude offer refunds?
-
-Payments are generally non-refundable, except where our Consumer Terms of Service say otherwise or where local law requires it.
-Customers outside of Europe can follow this process to request a refund:
-Log in, open Get help from the menu, start a message, and choose Claude Refund Request to check your eligibility.
-If you subscribed through the App Store, Apple handles the refund, so you'll request it from Apple.
-If you subscribed through Google Play, contact our Support team to check eligibility for an active subscription.
-If you're in the European Economic Area and the United Kingdom, and within your 14-day withdrawal period, you can request a refund directly in the app.
-
-PrevPrev
-
-NextNext
-
-Managing your plan
-
-How do I upgrade, downgrade, or switch between plans?
-
-You can change your plan any time in Settings.
-For individual plans, go to Settings > Billing and choose Manage subscription.
-On Team plans, an Owner or Primary Owner manages this under Organization settings > Billing. See more details here.
-Upgrades take effect right away, and any unused time on your current plan is credited toward the new one, so you won't pay twice for the same days.
-Moving from monthly to annual works the same way, with your remaining time credited to the first annual invoice.
-In some upgrades (for example Pro Annual to Max 5x Monthly), your remaining value on your old plan is larger than the cost of one billing period of the new plan. In this case, the excess will be stored as credit, which will automatically get used for future purchases.
-Downgrades take effect at the end of your current billing period, and your chats, projects, and files stay with your account whichever plan you're on.
-
-How do I cancel my Claude subscription?
-
-You can cancel anytime, and your plan stays active until the end of your current billing period. To avoid the next charge, cancel at least 24 hours before your renewal date.
-If you signed up on the web or the desktop app, go to Settings > Billing and click Cancel.
-If you subscribed through the App Store or Google Play, cancel from that app under Billing > Manage subscription, or directly in your Apple or Google Play account.
-Team and self-serve Enterprise: an Owner or Primary Owner cancels under Organization settings > Billing.
-Sales-assisted Enterprise: Reach out to your Anthropic Contact or our Sales team to discuss cancellation.
-Canceling doesn't delete your data. Your chats, projects, and files stay with your account, though some features aren't available on the Free plan. For Pro and Max, your account moves to the Free plan once the period ends. For step-by-step help, see how to cancel a Pro or Max plan or cancel a Team plan.
-
-PrevPrev
-
-NextNext
+How much does the Claude Enterprise plan cost?
HOW IT WAS JUDGED
triage verdictMATERIAL at 0.95, needed 0.55
triage reasoningPricing page restructured with major plan tiers removed from public view and feature availability matrix reorganized.
signalsmassive structural reorganization of pricing page · Team and Enterprise plan sections completely removed · Education plan removed · Legacy models section removed · FAQ content stripped · Individual plan structure replaced with simplified tier layout · Team plan pricing ($20/$100 per seat) no longer visible · Enterprise plan details removed from public pricing · model availability changed (Fable, Opus, Sonnet, Haiku availability per tier altered) · feature matrix restructured with Yes/No indicators added · context window specifications changed (200k shown for all tiers in new layout) · API pricing section completely removed from diff view
suppression
triage modelanthropic/claude-haiku-4.5 ($0.00000)
writer modelanthropic/claude-sonnet-4.5 ($0.00000)
WORTH KNOWING APIMODEL Claude Platform release notes · 2026-09-03 10:48 UTC

Audio files from code execution now carry C2PA credentials

DOTest your audio file handling pipeline with code-execution-generated audio from Fable 5.1 or Mythos 5.1.
WHAT CHANGEDAs of September 1, 2026, audio files generated by Claude Fable 5.1 and Claude Mythos 5.1 through the code execution tool now carry C2PA Content Credentials when retrieved via the Files API. Previously only image and video files were marked.
WHY IT MATTERSIf your application processes or stores audio artifacts from Claude's code execution, those files now contain embedded provenance metadata. Systems that validate file integrity, strip metadata, or assume clean audio output may reject or mishandle these files.
WHAT TO DOTest your audio file handling pipeline with code-execution-generated audio from Fable 5.1 or Mythos 5.1. Verify that parsers, transcoders, and storage systems accept C2PA-marked audio without errors or unexpected metadata stripping.
CONFIDENCE 85% Primary source ↗ written by anthropic/claude-sonnet-4.5
Show the reasoning — raw diff, triage verdict, confidence
RAW DIFF
 Per-message effort changes are in beta on Claude Fable 5.1, Claude Mythos 5.1, and Claude Opus 5 on the Claude API. Add a role: "system" message with output_config.effort inside messages to change effort for later turns while preserving the prompt cache. Include the mid-conversation-output-config-2026-07-01 beta header in your requests. See Per-message effort.
 Turn-scoped system messages are in beta (mid-conversation-system-clear-at-2026-08-21 header). Set clear_at: "next_user_message" on a mid-conversation role: "system" message and it renders for the current turn only, then stays in the history at no token cost. Per-turn reminders don't accumulate and don't invalidate the prompt cache or later thinking blocks.
 thinking.display accepts a third value, "updates", in beta (thinking-display-updates-2026-08-18 header). Reasoning comes back with an empty thinking field, as under "omitted", and the short progress updates that Claude Fable 5.1, Claude Mythos 5.1, and Claude Fable 5 write between tool calls come back as text, at most one thinking block before a tool call. See Progress updates between tool calls.
-Text generated by Claude Fable 5.1 and Claude Mythos 5.1 carries Anthropic's text watermark, and supported image and video files that Claude produces through the code execution tool carry C2PA Content Credentials when you retrieve them through the Files API on the Claude API. Marking requires no changes to your requests or response handling.
+Text generated by Claude Fable 5.1 and Claude Mythos 5.1 carries Anthropic's text watermark, and supported image, video, and audio files that Claude produces through the code execution tool carry C2PA Content Credentials when you retrieve them through the Files API on the Claude API. Marking requires no changes to your requests or response handling.
 Like Claude Fable 5, both models require 30-day data retention and aren't available under zero data retention unless expressly authorized by Anthropic. See Model-specific data retention requirements.
 The guides for the Claude Enterprise endpoints of the Admin API (user management and spend limits), the Claude Enterprise Analytics API, and the Compliance API now show the anthropic-version header; send it on every request to these endpoints, as in the rest of the Claude API. See API versions.
HOW IT WAS JUDGED
triage verdictMATERIAL at 0.72, needed 0.45
triage reasoningAudio files now included in C2PA Content Credentials output—expands what Claude produces and marks through Files API.
signalsfile type expansion in output credentials · data handling change (audio files now covered by C2PA) · new beta feature with header requirement · model capability change affecting output artifacts
suppression
triage modelanthropic/claude-haiku-4.5 ($0.00000)
writer modelanthropic/claude-sonnet-4.5 ($0.00000)
WORTH KNOWING DEPRECATIONMODEL Azure Foundry model retirement schedule · 2026-09-03 03:20 UTC

Claude Fable 5.1 retires 5 December 2027

DOGrep your codebase and infrastructure-as-code for 'claude-fable-5-1' references.
WHAT CHANGEDAzure Foundry added a retirement date of 2027-12-05 for the claude-fable-5-1 model. The model is currently in Preview status.
WHY IT MATTERSAny code or configuration using claude-fable-5-1 by name will stop working after that date. Preview models typically have shorter lifespans than GA releases, and 15 months is the notice window.
WHAT TO DOGrep your codebase and infrastructure-as-code for 'claude-fable-5-1' references. If found, add a calendar reminder for Q3 2027 to migrate to whatever replaces it, or pin to claude-fable-5 if that model remains supported.
CONFIDENCE 85% Primary source ↗ written by anthropic/claude-sonnet-4.5
Show the reasoning — raw diff, triage verdict, confidence
RAW DIFF
 claude-fable-5-1
 1
 Preview
+2027-12-05

-—
 
 claude-fable-5
 1
@@
 Suggest a fix?
 
 Last updated on
-2026-08-27
+2026-09-02
HOW IT WAS JUDGED
triage verdictMATERIAL at 0.92, needed 0.45
triage reasoningNew future date (2027-12-05) added to claude-fable-5-1 entry signals model retirement or sunset event.
signalsfuture date added to model entry · date format suggests retirement/sunset deadline · model lifecycle change · last-updated timestamp changed
suppression
triage modelanthropic/claude-haiku-4.5 ($0.00000)
writer modelanthropic/claude-sonnet-4.5 ($0.00000)
ACTION NEEDED APIDEPRECATION Claude Platform release notes · 2026-09-03 03:19 UTC

anthropic-version header now required on three Enterprise API endpoints

DOGrep your codebase for calls to Admin, Analytics, and Compliance API endpoints.
WHAT CHANGEDThe Admin API (user management and spend limits), Analytics API, and Compliance API now require the anthropic-version header on every request, matching the existing requirement across the rest of the Claude API. Documentation updated September 1, 2026.
WHY IT MATTERSRequests to these three Enterprise endpoints will fail without the header. If your integration calls these endpoints and does not currently send anthropic-version, those calls are now broken.
WHAT TO DOGrep your codebase for calls to Admin, Analytics, and Compliance API endpoints. Add the anthropic-version header to each request if missing. Test against production to confirm the calls succeed.
CONFIDENCE 85% Primary source ↗ written by anthropic/claude-sonnet-4.5
Show the reasoning — raw diff, triage verdict, confidence
RAW DIFF
 Turn-scoped system messages are in beta (mid-conversation-system-clear-at-2026-08-21 header). Set clear_at: "next_user_message" on a mid-conversation role: "system" message and it renders for the current turn only, then stays in the history at no token cost. Per-turn reminders don't accumulate and don't invalidate the prompt cache or later thinking blocks.
 thinking.display accepts a third value, "updates", in beta (thinking-display-updates-2026-08-18 header). Reasoning comes back with an empty thinking field, as under "omitted", and the short progress updates that Claude Fable 5.1, Claude Mythos 5.1, and Claude Fable 5 write between tool calls come back as text, at most one thinking block before a tool call. See Progress updates between tool calls.
 Text generated by Claude Fable 5.1 and Claude Mythos 5.1 carries Anthropic's text watermark, and supported image and video files that Claude produces through the code execution tool carry C2PA Content Credentials when you retrieve them through the Files API on the Claude API. Marking requires no changes to your requests or response handling.
-Like Claude Fable 5, both models require 30-day data retention and aren't available under zero data retention unless expressly authorized by Anthropic. See Model-specific data retention requirements.
+Like Claude Fable 5, both models require 30-day data retention and aren't available under zero data retention unless expressly authorized by Anthropic. See Model-specific data retention requirements.
+The guides for the Claude Enterprise endpoints of the Admin API (user management and spend limits), the Claude Enterprise Analytics API, and the Compliance API now show the anthropic-version header; send it on every request to these endpoints, as in the rest of the Claude API. See API versions.
HOW IT WAS JUDGED
triage verdictMATERIAL at 0.85, needed 0.45
triage reasoningNew required header on Enterprise API endpoints is a breaking change for existing integrations.
signalsnew API requirement: anthropic-version header now mandatory on three Enterprise endpoints · breaking change: Admin API, Analytics API, Compliance API affected · documentation update signals enforcement of existing versioning pattern
suppression
triage modelanthropic/claude-haiku-4.5 ($0.00000)
writer modelanthropic/claude-sonnet-4.5 ($0.00000)
WORTH KNOWING MODELPRICING Anthropic pricing · 2026-09-01 20:40 UTC

Fable 5.1 released with 75% lower prompt cache read cost

DOCheck your API calls: if you specify 'fable-5' explicitly, test whether that identifier now resolves to 5.1 or stays pinned to legacy 5.
WHAT CHANGEDAnthropic released Fable 5.1, replacing Fable 5 in the current model lineup. Prompt cache read pricing dropped from $1/MTok to $0.25/MTok. Fable 5 moved to legacy pricing with its original $1/MTok cache read rate. Input ($10/MTok) and output ($50/MTok) pricing unchanged.
WHY IT MATTERSIf you use Fable with prompt caching for long-context or repeated-prompt workloads, cache read costs drop 75% on the new version. Staying on Fable 5 means paying 4x more for cache reads than the current model. The version bump may also include capability changes not reflected in pricing.
WHAT TO DOCheck your API calls: if you specify 'fable-5' explicitly, test whether that identifier now resolves to 5.1 or stays pinned to legacy 5. If unpinned, you get the cost reduction automatically. If pinned, evaluate 5.1 for your use case and update the model identifier to capture the savings.
CONFIDENCE 85% Primary source ↗ written by anthropic/claude-sonnet-4.5
Show the reasoning — raw diff, triage verdict, confidence
RAW DIFF
 Learn more
 Batch processing
 
-Fable 5
+Fable 5.1
 Next generation intelligence for long-running agents
 
 Input
@@
 
 Prompt caching
 
+Read
+$0.25 / MTok
+
 Write
 $12.50 / MTok
 
-Read
-$1 / MTok
-
 Opus 5
 Ideal for complex agentic coding and enterprise work
 
@@
 
 Prompt caching
 
-Write
-$6.25 / MTok
-
 Read
 $0.50 / MTok
 
+Write
+$6.25 / MTok
+
 Sonnet 5
 High-performance model for coding and agents
 
@@
 
 Prompt caching
 
-Write
-$2.50 / MTok
-
 Read
 $0.20 / MTok
 
+Write
+$2.50 / MTok
+
 Haiku 4.5
 Fastest, most cost-efficient model
 
@@
 
 Prompt caching
 
-Write
-$1.25 / MTok
-
 Read
 $0.10 / MTok
 
+Write
+$1.25 / MTok
+
 For workloads that need to run in the US, US-only inference is available at 1.1x pricing for input and output tokens. Learn more.
 
 Get up to 2.5x faster speeds with fast mode for Opus 5 at 2x standard pricing. Learn more.
@@
 
 Explore detailed pricingExplore detailed pricing
 
+Fable 5
+
+Input
+$10 / MTok
+
+Output
+$50 / MTok
+
+Prompt caching
+
+Read
+$1 / MTok
+
+Write
+$12.50 / MTok
+
 Opus 4.8
 
 Input
@@
 
 Prompt caching
 
-Write
-$6.25 / MTok
-
 Read
 $0.50 / MTok
 
+Write
+$6.25 / MTok
+
 Save 50% with batch processing.
 Learn more
 Batch processing
@@
 
 Prompt caching
 
-Write
-$3.75 / MTok
-
 Read
 $0.30 / MTok
 
+Write
+$3.75 / MTok
+
 Opus 4.7
 
 Input
@@
 
 Prompt caching
 
-Write
-$6.25 / MTok
-
 Read
 $0.50 / MTok
 
+Write
+$6.25 / MTok
+
 Opus 4.6
 
 Input
@@
 
 Prompt caching
 
-Write
-$6.25 / MTok
-
 Read
 $0.50 / MTok
 
+Write
+$6.25 / MTok
+
 Sonnet 4.5
 
 Input
@@
 
 Prompt caching
 
-Write
-$3.75 / MTok
-
 Read
 $0.30 / MTok
 
+Write
+$3.75 / MTok
+
 Opus 4.5
 
 Input
@@
 
 Prompt caching
 
-Write
-$6.25 / MTok
-
 Read
 $0.50 / MTok
 
+Write
+$6.25 / MTok
+
 Opus 4.1
 
 Input
@@
 
 Prompt caching
 
-Write
-$18.75 / MTok
-
 Read
 $1.50 / MTok
 
+Write
+$18.75 / MTok
+
 Prompt caching pricing reflects 5-minute TTL. Learn about extended prompt caching.
 
 FAQ
HOW IT WAS JUDGED
triage verdictMATERIAL at 0.95, needed 0.55
triage reasoningFable 5.1 introduces new model with significantly lower cache read pricing. Fable 5 moved to legacy tier.
signalsmodel version bump: Fable 5 → Fable 5.1 · price change: Fable 5.1 read cache $1/MTok → $0.25/MTok (75% decrease) · new model tier added: Fable 5 appears in legacy section with different pricing · pricing reordering: read/write cache lines swapped (cosmetic) but prices are the substance · multiple prompt cache pricing changes across all models
suppression
triage modelanthropic/claude-haiku-4.5 ($0.00000)
writer modelanthropic/claude-sonnet-4.5 ($0.00000)
ACTION NEEDED MODELDEPRECATION Azure Foundry model retirement schedule · 2026-09-01 20:40 UTC

claude-opus-4-1 retired August 5, 2026; upgrade path to claude-opus-5

DOGrep your codebase and infrastructure-as-code for 'claude-opus-4-1' and replace with 'claude-opus-5'.
WHAT CHANGEDclaude-opus-4-1 marked Retired with effective date 2026-08-05. claude-opus-5 added to supported models list. Two new preview models added: claude-fable-5-1 and claude-mythos-5-1.
WHY IT MATTERSAny code or configuration explicitly requesting claude-opus-4-1 will fail after August 5, 2026. If you are using version pinning or explicit model identifiers rather than latest-stable aliases, calls will return errors once the retirement date passes.
WHAT TO DOGrep your codebase and infrastructure-as-code for 'claude-opus-4-1' and replace with 'claude-opus-5'. Test the replacement in staging before August 5, 2026.
CONFIDENCE 95% Primary source ↗ written by anthropic/claude-sonnet-4.5
Show the reasoning — raw diff, triage verdict, confidence
RAW DIFF
 2026-10-19

 
+claude-opus-4-1
+—
+Retired
+2026-08-05
+claude-opus-5
+
 claude-haiku-4-5
 1
 GA
@@
 2026-10-19

 
+claude-fable-5-1
+1
+Preview
+—
+—
+
 claude-fable-5
 1
 Preview
 2027-12-05

 
+claude-mythos-5-1
+1
+Preview
+—
+—
+
+claude-mythos-preview (gated research preview)
+—
+Preview
+2027-04-02
+—
+
 Cohere
 
 Model
HOW IT WAS JUDGED
triage verdictMATERIAL at 0.95, needed 0.45
triage reasoningRetirement date for existing model and new model versions affect deployment planning and API compatibility.
signalsmodel retirement date added (claude-opus-4-1, 2026-08-05) · new model versions added to supported list (claude-opus-5, claude-fable-5-1, claude-mythos-5-1) · model status changes (Retired, Preview) · future sunset dates present
suppression
triage modelanthropic/claude-haiku-4.5 ($0.00000)
writer modelanthropic/claude-sonnet-4.5 ($0.00000)
ACTION NEEDED APIMODELTERMSDEPRECATION Claude Platform release notes · 2026-09-01 20:40 UTC

Claude Fable 5.1 breaks tool_choice any/tool, requires 30-day retention

DOGrep your codebase for tool_choice parameters set to 'any' or 'tool' and migrate to structured outputs or strict tool use before switching to Fable 5.1.
WHAT CHANGEDClaude Fable 5.1 and Mythos 5.1 launched September 1, 2026. tool_choice types 'any' and 'tool' now return 400 errors; only 'auto' and 'none' work. Cache read pricing dropped from 0.1x to 0.025x base price ($0.25/MTok). Both models enforce 30-day minimum data retention with no zero-retention option unless Anthropic authorizes it. New accounts created August 31, 2026 or later get 400 errors when replaying thinking blocks after system prompt, tools, or message history changes.
WHY IT MATTERSIf you use tool_choice='any' or tool_choice='tool' in production, requests to Fable 5.1 will fail immediately. If your contract or compliance posture requires zero data retention, you cannot use these models without explicit authorization. The thinking block validation will break conversation replay for new accounts if you modify context mid-conversation.
WHAT TO DOGrep your codebase for tool_choice parameters set to 'any' or 'tool' and migrate to structured outputs or strict tool use before switching to Fable 5.1. Verify your data retention agreement permits 30-day retention or request authorization from Anthropic if you need zero retention. If you create new accounts after August 31, audit any code that replays thinking blocks after modifying system prompts or tools.
CONFIDENCE 95% Primary source ↗ written by anthropic/claude-sonnet-4.5
Show the reasoning — raw diff, triage verdict, confidence
RAW DIFF
+## Claude Platform release notes — September 1, 2026
+https://platform.claude.com/docs/en/release-notes/overview#september-1-2026
+Tue, 01 Sep 2026 00:00:00 GMT
+
+We've launched Claude Fable 5.1 (claude-fable-5-1), the successor to Claude Fable 5 for long-running agentic coding, knowledge work, and research, alongside Claude Mythos 5.1 (claude-mythos-5-1) for Project Glasswing participants. Both models support a 1M token context window by default, 128k max output tokens, and always-on adaptive thinking, at $10 / $50 USD per MTok, the same as Claude Fable 5, with cache reads cut to $0.25 per MTok. Claude Fable 5.1 is available on the Claude API, Claude in Amazon Bedrock, Claude Platform on AWS, Claude on Google Cloud, and Claude in Microsoft Foundry. See What's new in Claude Fable 5.1 for capabilities, API changes, and migration guidance.
+Prompt cache reads on Claude Fable 5.1 and Claude Mythos 5.1 cost $0.25 USD per million tokens: 0.025x the base input price, compared with 0.1x on other models. Cache writes are unchanged. See Prompt caching pricing.
+On Claude Fable 5.1 and Claude Mythos 5.1, tool_choice types any and tool aren't supported and return a 400 error. auto and none are unchanged. To guarantee schema-conformant tool inputs, use strict tool use or structured outputs.
+Thinking blocks produced by Claude Fable 5.1 and Claude Mythos 5.1 are preserved only for the model that produced them or a newer one: earlier models can't read them, and the API drops one replayed to an earlier model. Claude Fable 5.1 accepts thinking blocks from Claude Opus 5, Claude Fable 5, Claude Mythos 5, and earlier Claude models. On Claude Fable 5.1, the API also checks that nothing before a block has changed: for new accounts created on or after August 31, 2026, replaying one after the system prompt, tools, or an earlier message changed returns a 400 error. With the thinking-binding-controls-2026-08-01 beta header, dropped blocks are reported in an input_transformations response field, and thinking.block_binding.prefix_mismatch_behavior chooses between rejecting and dropping blocks whose history changed. See Preserved thinking.
+Per-message effort changes are in beta on Claude Fable 5.1, Claude Mythos 5.1, and Claude Opus 5 on the Claude API. Add a role: "system" message with output_config.effort inside messages to change effort for later turns while preserving the prompt cache. Include the mid-conversation-output-config-2026-07-01 beta header in your requests. See Per-message effort.
+Turn-scoped system messages are in beta (mid-conversation-system-clear-at-2026-08-21 header). Set clear_at: "next_user_message" on a mid-conversation role: "system" message and it renders for the current turn only, then stays in the history at no token cost. Per-turn reminders don't accumulate and don't invalidate the prompt cache or later thinking blocks.
+thinking.display accepts a third value, "updates", in beta (thinking-display-updates-2026-08-18 header). Reasoning comes back with an empty thinking field, as under "omitted", and the short progress updates that Claude Fable 5.1, Claude Mythos 5.1, and Claude Fable 5 write between tool calls come back as text, at most one thinking block before a tool call. See Progress updates between tool calls.
+Text generated by Claude Fable 5.1 and Claude Mythos 5.1 carries Anthropic's text watermark, and supported image and video files that Claude produces through the code execution tool carry C2PA Content Credentials when you retrieve them through the Files API on the Claude API. Marking requires no changes to your requests or response handling.
+Like Claude Fable 5, both models require 30-day data retention and aren't available under zero data retention unless expressly authorized by Anthropic. See Model-specific data retention requirements.
HOW IT WAS JUDGED
triage verdictMATERIAL at 0.98, needed 0.45
triage reasoningNew model release with pricing changes, breaking API changes, data retention requirements, and multiple feature additions affecting production deployments.
signalsnew model release (Claude Fable 5.1, Claude Mythos 5.1) · pricing change (cache reads $0.25/MTok, 0.025x vs 0.1x) · breaking API change (tool_choice types any/tool return 400 error) · new data retention requirement (30-day minimum, no zero-retention option) · new feature (adaptive thinking always-on) · context window specification (1M tokens default, 128k max output) · beta API features with headers (mid-conversation output config, system message scoping, thinking display updates) · thinking block compatibility constraints (forward-compatible only, prefix mismatch validation for new accounts after Aug 31 2026)
suppression
triage modelanthropic/claude-haiku-4.5 ($0.00000)
writer modelanthropic/claude-sonnet-4.5 ($0.00000)
ACTION NEEDED DEPRECATIONMODELAPI OpenAI deprecations · 2026-08-31 04:10 UTC

Four transcription models deprecated, shutdown February 26, 2027

DOGrep your codebase for 'whisper-1', 'gpt-4o-transcribe', 'gpt-4o-mini-transcribe', and 'gpt-4o-transcribe-diarize'.
WHAT CHANGEDOn August 26, 2026, OpenAI announced that whisper-1, gpt-4o-transcribe, gpt-4o-mini-transcribe, and gpt-4o-transcribe-diarize will be removed from the API on February 26, 2027. Recommended replacements are gpt-live-transcribe or gpt-transcribe.
WHY IT MATTERSAny application using these four models for audio transcription will break on February 26, 2027 unless migrated to the replacement models. You have six months to test and deploy the migration.
WHAT TO DOGrep your codebase for 'whisper-1', 'gpt-4o-transcribe', 'gpt-4o-mini-transcribe', and 'gpt-4o-transcribe-diarize'. For each usage, schedule migration to gpt-live-transcribe or gpt-transcribe before February 26, 2027.
CONFIDENCE 95% Primary source ↗ written by anthropic/claude-sonnet-4.5
Show the reasoning — raw diff, triage verdict, confidence
RAW DIFF
 
 Upcoming deprecations are listed below, with the most recent announcements at the top.
 
+2026-08-26: Transcription models
+
+On August 26, 2026, we notified developers using whisper-1, gpt-4o-transcribe, gpt-4o-mini-transcribe, and gpt-4o-transcribe-diarize of their deprecation and removal from the API on February 26, 2027.
+
+For information about the recommended replacements, see the transcription guide.
+
+Shutdown dateModel / systemRecommended replacement
+Feb 26, 2027whisper-1gpt-live-transcribe or gpt-transcribe
+Feb 26, 2027gpt-4o-transcribegpt-live-transcribe or gpt-transcribe
+Feb 26, 2027gpt-4o-mini-transcribegpt-live-transcribe or gpt-transcribe
+Feb 26, 2027gpt-4o-transcribe-diarizegpt-live-transcribe or gpt-transcribe
+
 2026-07-20: Legacy audio, realtime, and transcription models
 
 On July 20, 2026, we notified developers using legacy audio, realtime, and transcription model families and snapshots of their deprecation and removal from the API on January 20, 2027.
@@
 
 2025-08-20: Assistants API
 
-The Assistants API was officially sunset on August 26, 2026, following its deprecation announcement on August 26, 2025.
+On August 26th, 2025, we notified developers using the Assistants API of its deprecation and removal from the API one year later, on August 26, 2026.
 
 When we released the Responses API in March 2025, we announced plans to bring all Assistants API features to the easier to use Responses API, with a sunset date in 2026.
 
HOW IT WAS JUDGED
triage verdictMATERIAL at 0.95, needed 0.45
triage reasoningNew deprecation entry with four transcription models, shutdown date, and replacement guidance for engineering teams.
signalsfuture sunset date added (Feb 26, 2027) · four models deprecated and removed · replacement models specified · deprecation announcement date (Aug 26, 2026) · existing deprecation (Assistants API) reworded for clarity
suppression
triage modelanthropic/claude-haiku-4.5 ($0.00000)
writer modelanthropic/claude-sonnet-4.5 ($0.00000)
ACTION NEEDED DEPRECATIONMODEL Azure Foundry model retirement schedule · 2026-08-29 05:59 UTC

Three MAI-Image-2.5 variants added to retirement schedule, sunset October 2026

DOGrep your codebase for 'MAI-Image-2.5', 'MAI-Image-2.5-Flash', and 'MAI-Image-2.5-Pro'.
WHAT CHANGEDMAI-Image-2.5, MAI-Image-2.5-Flash, and MAI-Image-2.5-Pro added to Azure Foundry retirement schedule. All three entered Preview on June 2 or June 19, 2026, and will be retired October 1, 2026. MAI-Image-2e status changed from Preview to Retired.
WHY IT MATTERSIf you are using or planning to use any MAI-Image-2.5 variant, you have a four-month window from preview to retirement. Code written against these models will break on October 1, 2026 unless migrated to a successor model.
WHAT TO DOGrep your codebase for 'MAI-Image-2.5', 'MAI-Image-2.5-Flash', and 'MAI-Image-2.5-Pro'. If found, schedule migration work to complete before October 1, 2026. If not using these models, no action required.
CONFIDENCE 95% Primary source ↗ written by anthropic/claude-sonnet-4.5
Show the reasoning — raw diff, triage verdict, confidence
RAW DIFF
 2027-05-20

 
+MAI-Image-2.5-Pro
+2026-06-19
+Preview
+2026-10-01
+—
+
+MAI-Image-2.5-Flash
+2026-06-02
+Preview
+2026-10-01
+—
+
+MAI-Image-2.5
+2026-06-02
+Preview
+2026-10-01
+—
+
 MAI-Image-2e
 2026-04-09
-Preview
+Retired
 2026-08-15
 MAI-Image-2.5-Flash
 
HOW IT WAS JUDGED
triage verdictMATERIAL at 0.95, needed 0.45
triage reasoningNew models added with concrete deprecation and retirement dates; existing model status changed to Retired.
signalsnew models added to retirement schedule · future deprecation dates (2026-06-02, 2026-06-19) · future sunset dates (2026-10-01) · model status change: Preview → Retired · three new model variants with defined lifecycle windows
suppression
triage modelanthropic/claude-haiku-4.5 ($0.00000)
writer modelanthropic/claude-sonnet-4.5 ($0.00000)
ACTION NEEDED MODELAPIDEPRECATION Azure Foundry model retirement schedule · 2026-08-28 21:46 UTC

Azure Foundry splits Claude models into two hosting versions with new retirement dates

DOAudit your model identifiers to confirm which version (1 or 2) you are using.
WHAT CHANGEDAzure Foundry now offers Claude models in two versions: Version 1 (Anthropic infrastructure) and Version 2 (Azure infrastructure). Multiple models moved from Preview to GA status. claude-opus-4-1 was removed from the schedule (previously marked Retired 2026-08-05). New model claude-fable-5 added with retirement date 2027-12-05. claude-haiku-4-5 Preview variant removed; GA variants now exist for both Version 1 and Version 2, both retiring 2026-10-19.
WHY IT MATTERSIf you are calling Claude models by name without specifying version, your requests may now route to different infrastructure (Anthropic vs Azure) with potentially different latency, availability, or billing characteristics. The removal of claude-opus-4-1 from the schedule means any code still referencing it is calling a model that no longer appears in the official retirement timeline.
WHAT TO DOAudit your model identifiers to confirm which version (1 or 2) you are using. If you are calling claude-opus-4-1, verify whether it still responds or migrate to claude-opus-5 (GA, retires 2027-07-08). If you rely on claude-haiku-4-5, confirm whether you are on Version 1 or 2 and note the 2026-10-19 retirement date for both.
CONFIDENCE 85% Primary source ↗ written by anthropic/claude-sonnet-4.5
Show the reasoning — raw diff, triage verdict, confidence
RAW DIFF
 
 Anthropic
 
+Microsoft Foundry offers Claude models in two versions:
+
+Version 1: Hosted on Anthropic infrastructure
+
+Version 2: Hosted on Azure
+
 Model
 Version
 Lifecycle
 Retirement date
 Replacement
 
-claude-haiku-4-5
+claude-sonnet-5
+2
+GA
+2027-06-30

-Preview
-2026-10-19
+
+claude-sonnet-5
+1
+GA
+2027-06-30

 
-claude-mythos-preview (gated research preview)
+claude-sonnet-4-6
+1
+GA
+2027-02-10

-Preview
-2027-04-02
+
+claude-sonnet-4-5
+1
+GA
+2026-10-19

 
-claude-opus-4-1
+claude-opus-5
+2
+GA
+2027-07-08

-Retired
-2026-08-05
+
 claude-opus-5
+1
+GA
+2027-07-08
+—
 
-claude-opus-4-5
+claude-opus-4-8
+2
+GA
+2027-09-01

-Preview
-2026-10-19
-—
 
-claude-opus-4-6
+claude-opus-4-8
+1
+GA
+2027-09-01

-Preview
-2027-02-02
-—
 
 claude-opus-4-7
-—
-Preview
+1
+GA
 2027-04-06

 
-claude-sonnet-4-5
+claude-opus-4-6
+1
+GA
+2027-02-02

-Preview
+
+claude-opus-4-5
+1
+GA
 2026-10-19

 
-claude-sonnet-4-6
+claude-haiku-4-5
+1
+GA
+2026-10-19

+
+claude-haiku-4-5
+2
+GA
+2026-10-19
+—
+
+claude-fable-5
+1
 Preview
-2027-02-10
+2027-12-05

 
 Cohere
@@
 Suggest a fix?
 
 Last updated on
-2026-08-26
+2026-08-27
HOW IT WAS JUDGED
triage verdictMATERIAL at 0.95, needed 0.45
triage reasoningRetirement dates shifted, model availability split by hosting, lifecycle statuses upgraded, breaking changes to model roster.
signalsmultiple retirement dates changed · model lifecycle statuses changed (Preview→GA) · new model versions introduced (Version 1 vs Version 2 hosting split) · models removed from list (claude-haiku-4-5 Preview variant gone) · new model added (claude-fable-5) · retirement date accelerated (claude-opus-4-1 from 2026-08-05 now absent) · structural change: dual-version hosting model introduced
suppression
triage modelanthropic/claude-haiku-4.5 ($0.00000)
writer modelanthropic/claude-sonnet-4.5 ($0.00000)
WORTH KNOWING API Claude Platform release notes · 2026-08-28 21:46 UTC

Compliance API adds Science and Office 365 session transcripts

DOCheck your Compliance API response handling for product_surface filtering or validation.
WHAT CHANGEDCompliance API session endpoints for Cowork and Claude Code are now GA (out of beta). Local session endpoints now return transcripts for Claude Science sessions (product_surface: claude_science) and Claude for Microsoft 365 sessions in Excel, PowerPoint, Word, and Outlook (product_surface values starting with office_agents), both in beta for Enterprise organizations. No new authentication required—existing Compliance Access Key with read:compliance_user_data scope works.
WHY IT MATTERSIf you retrieve compliance transcripts, your existing integration now captures two additional product surfaces without code changes. If you filter or route transcripts by product_surface value, unrecognized values will appear in your logs or break strict validation.
WHAT TO DOCheck your Compliance API response handling for product_surface filtering or validation. Add claude_science and office_agents* to your expected values list if you whitelist them, or confirm your code handles unknown values gracefully.
CONFIDENCE 85% Primary source ↗ written by anthropic/claude-sonnet-4.5
Show the reasoning — raw diff, triage verdict, confidence
RAW DIFF
+## Claude Platform release notes — August 26, 2026
+https://platform.claude.com/docs/en/release-notes/overview#august-26-2026
+Wed, 26 Aug 2026 00:00:00 GMT
+
+The Compliance API session endpoints are out of beta for Cowork and Claude Code sessions. See Retrieve session transcripts.
+The Compliance API local session endpoints now also return transcripts of Claude Science sessions (product_surface value claude_science) and Claude for Microsoft 365 sessions in Excel, PowerPoint, Word, and Outlook (product_surface values beginning with office_agents), in beta for Claude Enterprise organizations, with your existing Compliance Access Key and the read:compliance_user_data scope. See Sessions on users' machines.
HOW IT WAS JUDGED
triage verdictMATERIAL at 0.78, needed 0.45
triage reasoningCompliance API endpoints graduate from beta and expand to new product surfaces, affecting API consumers' integration scope.
signalsfeature graduation from beta to GA · new product surfaces added to API · new beta feature announced · API scope/capability expansion · compliance/data handling change
suppression
triage modelanthropic/claude-haiku-4.5 ($0.00000)
writer modelanthropic/claude-sonnet-4.5 ($0.00000)
WORTH KNOWING MODELAPI Claude Platform release notes · 2026-08-26 19:49 UTC

Computer use and browser use toolsets now available on Google Cloud

DOIf you have Google Cloud deployments that need computer use or browser use, test the toolsets with your existing tools entries format—no API changes are required from th…
WHAT CHANGEDThe computer_toolset_20260801 and browser_toolset_20260801 toolsets are now available on Google Cloud for Claude Fable 5, Claude Mythos 5, Claude Opus 5, Claude Sonnet 5, and Claude Opus 4.8. The tools entries format matches the Claude API.
WHY IT MATTERSIf you run Claude on Google Cloud and have been waiting for computer use or browser use capabilities, you can now deploy those features without migrating to a different cloud provider or API endpoint.
WHAT TO DOIf you have Google Cloud deployments that need computer use or browser use, test the toolsets with your existing tools entries format—no API changes are required from the Claude API implementation.
CONFIDENCE 85% Primary source ↗ written by anthropic/claude-sonnet-4.5
Show the reasoning — raw diff, triage verdict, confidence
RAW DIFF
 https://platform.claude.com/docs/en/release-notes/overview#august-20-2026
 Thu, 20 Aug 2026 00:00:00 GMT
 
-We've released v1.0 of the Python SDK. The SDK's HTTP layer moves from httpx to httpx2, a maintained, API-compatible fork: build custom http_client, Timeout, and transport objects from httpx2 (the DefaultHttpxClient helpers are unchanged), and call httpx2.alias_httpx() at startup if you rely on tracing or mocking libraries that patch httpx. v1.0 requires Python 3.10 or later and removes long-deprecated surface, including the legacy Text Completions API, the temperature, top_p, and top_k parameters on Messages methods, and the tool runner's client-side compaction_control. On the async client, .with_raw_response results now need await response.parse(), and AnthropicBedrock now raises an error when no AWS region is configured instead of defaulting to us-east-1. See the v1 migration guide for every change with before-and-after snippets.
+We've released v1.0 of the Python SDK. The SDK's HTTP layer moves from httpx to httpx2, a maintained, API-compatible fork: build custom http_client, Timeout, and transport objects from httpx2 (the DefaultHttpxClient helpers are unchanged), and call httpx2.alias_httpx() at startup if you rely on tracing or mocking libraries that patch httpx. v1.0 requires Python 3.10 or later and removes long-deprecated surface, including the legacy Text Completions API, the temperature, top_p, and top_k parameters on Messages methods, and the tool runner's client-side compaction_control. On the async client, .with_raw_response results now need await response.parse(), and AnthropicBedrock now raises an error when no AWS region is configured instead of defaulting to us-east-1. See the v1 migration guide for every change with before-and-after snippets.
+The computer use and browser use toolsets (computer_toolset_20260801 and browser_toolset_20260801) are now available on Google Cloud for Claude Fable 5, Claude Mythos 5, Claude Opus 5, Claude Sonnet 5, and Claude Opus 4.8. Requests use the same tools entries as on the Claude API.
HOW IT WAS JUDGED
triage verdictMATERIAL at 0.92, needed 0.45
triage reasoningNew toolsets and models available on Google Cloud platform expands deployment options for engineering teams.
signalsnew feature availability announced · specific model list provided · new toolsets with dated identifiers · platform expansion (Google Cloud) · affects deployment decisions
suppression
triage modelanthropic/claude-haiku-4.5 ($0.00000)
writer modelanthropic/claude-sonnet-4.5 ($0.00000)
WORTH KNOWING DEPRECATIONMODEL Azure Foundry model retirement schedule · 2026-08-25 06:49 UTC

Sora-2 preview retirement delayed one month to 15 October 2026

DOCheck your migration schedule for sora-2.
WHAT CHANGEDThe retirement date for the sora-2 preview model moved from 15 September 2026 to 15 October 2026.
WHY IT MATTERSIf you planned migration work around the September deadline, you now have four additional weeks. If you already migrated, the extension changes nothing.
WHAT TO DOCheck your migration schedule for sora-2. If you have not started and the September date was tight, you can defer by up to four weeks. If you already migrated or the date was not a constraint, no action needed.
CONFIDENCE 95% Primary source ↗ written by anthropic/claude-sonnet-4.5
Show the reasoning — raw diff, triage verdict, confidence
RAW DIFF
 sora-2
 2025-12-08
 Preview
-2026-09-15
+2026-10-15

 
 text-embedding-3-large
HOW IT WAS JUDGED
triage verdictMATERIAL at 0.95, needed 0.45
triage reasoningSora-2 preview retirement date pushed from September to October 2026. Teams relying on this model need to know the new deadline.
signalsfuture date changed · retirement/sunset date extended by one month · model lifecycle milestone altered
suppression
triage modelanthropic/claude-haiku-4.5 ($0.00000)
writer modelanthropic/claude-sonnet-4.5 ($0.00000)
ACTION NEEDED APIMODEL Claude Platform release notes · 2026-08-22 01:15 UTC

Claude API default top_p changed from 0.999 to 0.99 for all models

DOAudit your Claude API calls: if you rely on the previous default behavior, explicitly set top_p: 0.999 in all requests.
WHAT CHANGEDThe Messages API now defaults top_p to 0.99 instead of 0.999 across all models, effective immediately. Extended thinking calls can now set top_p between 0.95 and 1.0, expanded from the previous narrower range.
WHY IT MATTERSEvery request not explicitly setting top_p now uses different sampling behavior, which changes response variability and may affect tool call reliability, output consistency in production workflows, and any testing or validation tied to specific model behavior.
WHAT TO DOAudit your Claude API calls: if you rely on the previous default behavior, explicitly set top_p: 0.999 in all requests. If you use extended thinking and want the old constraint, pin top_p below 0.95 or above 1.0 will now error—test your parameter validation.
CONFIDENCE 95% Primary source ↗ written by anthropic/claude-sonnet-4.5
Show the reasoning — raw diff, triage verdict, confidence
RAW DIFF
 We've launched the MCP connector in public beta, a feature that allows you to connect to remote MCP servers directly from the Messages API.
 To increase answer quality and decrease tool errors, we've changed the default value for the top_p nucleus sampling parameter in the Messages API from 0.999 to 0.99 for all models. To revert this change, set top_p to 0.999.
 Additionally, when extended thinking is enabled, you can now set top_p to values between 0.95 and 1.
-We've moved our Go SDK from beta to GA.
+Our Go SDK has moved from beta to its first stable release.
 We've included minute and hour level granularity to the Usage page of Console alongside 429 error rates on the Usage page.
HOW IT WAS JUDGED
triage verdictMATERIAL at 0.92, needed 0.45
triage reasoningDefault API parameter change affects all users; SDK GA is a stability milestone; extended thinking constraint change expands capability.
signalsdefault parameter value changed (top_p 0.999 to 0.99) · parameter constraint relaxed (extended thinking top_p now 0.95–1.0) · SDK lifecycle milestone (beta to GA) · behavioral change affecting all models without opt-in
suppression
triage modelanthropic/claude-haiku-4.5 ($0.00000)
writer modelanthropic/claude-sonnet-4.5 ($0.00000)
ACTION NEEDED APIDEPRECATION Claude Platform release notes · 2026-08-22 01:15 UTC

Claude Python SDK v1.0 removes Text Completions API, requires Python 3.10+

DOBefore upgrading: grep your codebase for 'text_completions', 'temperature', 'top_p', 'top_k' in Messages calls, and 'compaction_control'; verify Python version is 3.10+;…
WHAT CHANGEDReleased August 20, 2026. Python SDK v1.0 removes the legacy Text Completions API, the temperature/top_p/top_k parameters on Messages methods, and tool runner's client-side compaction_control. Minimum Python version is now 3.10. HTTP layer switches from httpx to httpx2. Async client .with_raw_response results now require await response.parse(). AnthropicBedrock no longer defaults to us-east-1 when AWS region is unconfigured.
WHY IT MATTERSCode using the removed Text Completions API or deprecated parameters will break immediately on upgrade. Applications running Python 3.9 or earlier cannot install this version. Async response handling that omits await response.parse() will fail. AnthropicBedrock calls without explicit region configuration will error instead of silently using us-east-1.
WHAT TO DOBefore upgrading: grep your codebase for 'text_completions', 'temperature', 'top_p', 'top_k' in Messages calls, and 'compaction_control'; verify Python version is 3.10+; check all .with_raw_response usage includes await response.parse(); confirm AnthropicBedrock has explicit region set. Consult the v1 migration guide for replacement patterns.
CONFIDENCE 95% Primary source ↗ written by anthropic/claude-sonnet-4.5
Show the reasoning — raw diff, triage verdict, confidence
RAW DIFF
+## Claude Platform release notes — August 20, 2026
+https://platform.claude.com/docs/en/release-notes/overview#august-20-2026
+Thu, 20 Aug 2026 00:00:00 GMT
+
+We've released v1.0 of the Python SDK. The SDK's HTTP layer moves from httpx to httpx2, a maintained, API-compatible fork: build custom http_client, Timeout, and transport objects from httpx2 (the DefaultHttpxClient helpers are unchanged), and call httpx2.alias_httpx() at startup if you rely on tracing or mocking libraries that patch httpx. v1.0 requires Python 3.10 or later and removes long-deprecated surface, including the legacy Text Completions API, the temperature, top_p, and top_k parameters on Messages methods, and the tool runner's client-side compaction_control. On the async client, .with_raw_response results now need await response.parse(), and AnthropicBedrock now raises an error when no AWS region is configured instead of defaulting to us-east-1. See the v1 migration guide for every change with before-and-after snippets.
HOW IT WAS JUDGED
triage verdictMATERIAL at 0.95, needed 0.45
triage reasoningMajor SDK version with multiple breaking changes and removed APIs requires engineering team action.
signalsmajor version release (v1.0) · breaking API changes (legacy Text Completions API removed) · deprecated parameters removed (temperature, top_p, top_k) · minimum Python version requirement (3.10+) · async client behavior change (await response.parse()) · error behavior change (AnthropicBedrock region default removed) · dependency change (httpx to httpx2) · migration guide referenced
suppression
triage modelanthropic/claude-haiku-4.5 ($0.00000)
writer modelanthropic/claude-sonnet-4.5 ($0.00000)
WORTH KNOWING APIMODEL Claude Platform release notes · 2026-08-22 01:15 UTC

Claude Sonnet 3.5 8K output no longer requires beta header

DOSearch your codebase for 'max-tokens-3-5-sonnet-2024-07-15' and remove the header from API calls.
WHAT CHANGEDThe max-tokens-3-5-sonnet-2024-07-15 header is no longer required to access 8,192-token outputs on Claude Sonnet 3.5. The feature moved from beta to general availability on August 19, 2024.
WHY IT MATTERSCode that sets this header will continue to work but is now redundant. Teams that avoided the feature due to beta status can now use extended outputs without special headers.
WHAT TO DOSearch your codebase for 'max-tokens-3-5-sonnet-2024-07-15' and remove the header from API calls. The functionality remains identical without it.
CONFIDENCE 95% Primary source ↗ written by anthropic/claude-sonnet-4.5
Show the reasoning — raw diff, triage verdict, confidence
RAW DIFF
 https://platform.claude.com/docs/en/release-notes/overview#august-19th-2024
 Mon, 19 Aug 2024 00:00:00 GMT
 
-We've moved 8,192 token outputs from beta to general availability for Claude Sonnet 3.5.
+8,192-token outputs on Claude Sonnet 3.5 are out of beta and no longer require the max-tokens-3-5-sonnet-2024-07-15 header.
HOW IT WAS JUDGED
triage verdictMATERIAL at 0.92, needed 0.45
triage reasoningDevelopers no longer need to pass a specific header to use 8K outputs on Sonnet 3.5.
signalsfeature graduation from beta to GA · API header requirement removed · developer workflow change
suppression
triage modelanthropic/claude-haiku-4.5 ($0.00000)
writer modelanthropic/claude-sonnet-4.5 ($0.00000)
ACTION NEEDED APIDEPRECATION Claude Platform release notes · 2026-08-21 01:19 UTC

Computer use tool GA changes request shape, requires migration

DOIf you use the computer use tool, read the migration guide at 'Migrate from computer_20251124' before removing the beta header.
WHAT CHANGEDThe computer use tool is now GA as computer_toolset_20260801, replacing earlier beta versions. The upgrade changes the request shape and tool handling. The Files API is GA with a new response format: file expiration (expires_in_seconds on upload, expires_at in responses) and page/next_page pagination with ids[] filter. Both changes take effect immediately when you stop sending the beta headers.
WHY IT MATTERSExisting integrations using the beta computer use tool will break if you switch to the GA version without updating your request structure. Files API clients that drop the beta header will receive a different response format and pagination scheme, breaking any code that expects the old structure.
WHAT TO DOIf you use the computer use tool, read the migration guide at 'Migrate from computer_20251124' before removing the beta header. If you use the Files API, test your pagination and expiration handling against the GA format before dropping the files-api-2025-04-14 header from production requests.
CONFIDENCE 95% Primary source ↗ written by anthropic/claude-sonnet-4.5
Show the reasoning — raw diff, triage verdict, confidence
RAW DIFF
 https://platform.claude.com/docs/en/release-notes/overview#august-19-2026
 Wed, 19 Aug 2026 00:00:00 GMT
 
+The computer use tool is now generally available on the Claude API as the computer_toolset_20260801 toolset: no beta header, batch actions (several actions in one turn), zoom enabled by default, and per-member configuration through configs. Earlier beta versions remain available. Upgrading an existing integration changes the request shape and tool handling; see Migrate from computer_20251124.
+We've launched the browser use tool (browser_toolset_20260801), a client toolset for driving a browser that your application hosts. It works inside a browser viewport rather than a whole desktop, reading the page itself (its accessibility tree, elements, forms, and tabs) and adding element references, form input, tab management, download reporting, and opt-in file upload on top of screenshot-and-click control.
+Both toolsets are available for Claude Fable 5, Claude Mythos 5, Claude Opus 5, Claude Sonnet 5, and Claude Opus 4.8 on the Claude API.
 The Files API is now generally available on the Claude API. Requests to the /v1/files endpoints, and Messages API requests that reference an uploaded file, no longer require the files-api-2025-04-14 beta header. Requests sent without the header use the GA response format: file expiration (set expires_in_seconds when you upload a file; file objects report expires_at), and page and next_page pagination plus an ids[] filter when you list files. /v1/files requests that still send the beta header keep working and return the previous response format.
 Agent Skills and the Skills API (/v1/skills) are now generally available on the Claude API. Requests no longer require the skills-2025-10-02 beta header, including Messages API requests that load Skills through the container parameter. Requests that still send the header continue to work unchanged. See Using Agent Skills with the API.
-The Admin API user-management endpoints for Claude Enterprise (claude.ai) organizations (members, invites, groups, and custom roles) are now generally available. The anthropic-beta: ce-user-management-2026-07-13 header is no longer required on group and custom-role requests; requests that still send it are accepted unchanged. See User management.
+The Admin API user-management endpoints for Claude Enterprise (claude.ai) organizations (members, invites, groups, and custom roles) are now generally available. The anthropic-beta: ce-user-management-2026-07-13 header is no longer required on group and custom-role requests; requests that still send it are accepted unchanged. See User management.
+You can now restrict which sites a Claude Managed Agents agent's web_search and web_fetch tools can reach. Set allowed_domains or blocked_domains on the tool's entry in the agent_toolset_20260401 configs array; web_fetch also accepts max_content_tokens and web_search accepts user_location. Each configs entry is identified by its name and typed by an optional type, and requests that pass only name, enabled, and permission_policy continue to work; in the typed SDKs, configs entries become per-tool types. See Restrict web search and web fetch domains.
+Claude Managed Agents sessions that run in a self-hosted sandbox can now attach memory stores. The Python, TypeScript, and Go SDK workers download each attached store into the sandbox at its mount_path and sync the agent's changes back to the store. See Use memory stores.
+The session viewer in the Claude Console has been redesigned with a timeline minimap, a transcript grouped by model request, and an Inspector panel for session details and cost, raw events, per-tool statistics, mounted resources, and per-thread activity. See Console observability.
HOW IT WAS JUDGED
triage verdictMATERIAL at 0.95, needed 0.45
triage reasoningMultiple GA releases, new tools, breaking changes, and feature additions affecting API integrations.
signalscomputer_toolset_20260801 GA release with breaking change warning · new browser_toolset_20260801 tool launched · Files API GA with response format changes · Agent Skills API GA · Admin API user-management GA · new web_search/web_fetch domain restriction feature · new memory store attachment for self-hosted sandbox sessions · multiple model availability statements (Fable 5, Mythos 5, Opus 5, Sonnet 5, Opus 4.8)
suppression
triage modelanthropic/claude-haiku-4.5 ($0.00000)
writer modelanthropic/claude-sonnet-4.5 ($0.00000)
ACTION NEEDED APIDEPRECATION Claude Platform release notes · 2026-08-20 18:39 UTC

Files API, Skills API, and Admin API user-management moved to GA

DOGrep your codebase for 'files-api-2025-04-14', 'skills-2025-10-02', and 'ce-user-management-2026-07-13'.
WHAT CHANGEDEffective August 19, 2026, three Claude APIs moved from beta to general availability: Files API (/v1/files), Skills API (/v1/skills), and Admin API user-management endpoints. Beta headers (files-api-2025-04-14, skills-2025-10-02, anthropic-beta: ce-user-management-2026-07-13) are no longer required. The Files API GA response format differs from beta: pagination changed from page/next_page to ids[] filter, and file expiration now uses expires_in_seconds (upload) and expires_at (response) instead of the beta format.
WHY IT MATTERSCode sending beta headers continues to work but receives the old response format. Code that stopped sending headers or never sent them now receives the GA format with different pagination and expiration field names, which will break parsing logic expecting the beta structure.
WHAT TO DOGrep your codebase for 'files-api-2025-04-14', 'skills-2025-10-02', and 'ce-user-management-2026-07-13'. For Files API calls, verify whether your code parses expires_at and handles ids[] pagination, or if it expects the beta format. If you need the beta format, confirm the header is still being sent; if you need GA format, remove the header and update response parsing.
CONFIDENCE 95% Primary source ↗ written by anthropic/claude-sonnet-4.5
Show the reasoning — raw diff, triage verdict, confidence
RAW DIFF
+## Claude Platform release notes — August 19, 2026
+https://platform.claude.com/docs/en/release-notes/overview#august-19-2026
+Wed, 19 Aug 2026 00:00:00 GMT
+
+The Files API is now generally available on the Claude API. Requests to the /v1/files endpoints, and Messages API requests that reference an uploaded file, no longer require the files-api-2025-04-14 beta header. Requests sent without the header use the GA response format: file expiration (set expires_in_seconds when you upload a file; file objects report expires_at), and page and next_page pagination plus an ids[] filter when you list files. /v1/files requests that still send the beta header keep working and return the previous response format.
+Agent Skills and the Skills API (/v1/skills) are now generally available on the Claude API. Requests no longer require the skills-2025-10-02 beta header, including Messages API requests that load Skills through the container parameter. Requests that still send the header continue to work unchanged. See Using Agent Skills with the API.
+The Admin API user-management endpoints for Claude Enterprise (claude.ai) organizations (members, invites, groups, and custom roles) are now generally available. The anthropic-beta: ce-user-management-2026-07-13 header is no longer required on group and custom-role requests; requests that still send it are accepted unchanged. See User management.
HOW IT WAS JUDGED
triage verdictMATERIAL at 0.92, needed 0.45
triage reasoningThree major API features graduating from beta to GA with breaking response format changes and header removal.
signalsFiles API moved from beta to GA · Skills API moved from beta to GA · Admin API user-management endpoints moved from beta to GA · Beta headers no longer required · Response format changes documented · Breaking change: GA response format differs from beta format · Future date: August 19, 2026
suppression
triage modelanthropic/claude-haiku-4.5 ($0.00000)
writer modelanthropic/claude-sonnet-4.5 ($0.00000)
WORTH KNOWING DEPRECATIONMODEL Azure Foundry model retirement schedule · 2026-08-20 01:15 UTC

gpt-4.1-nano retirement extended six months to 2027-04-14

DOCheck your migration backlog for gpt-4.1-nano work scheduled before 2027-04-14.
WHAT CHANGEDAzure Foundry moved gpt-4.1-nano retirement from 2026-10-14 to 2027-04-14. The model's status label changed from 'Deprecated' to 'Legacy' on 2025-04-14. Three other models (gpt-4.1, gpt-4.1-mini, gpt-4o) also changed to 'Legacy' status with 2027-04-14 retirement dates.
WHY IT MATTERSIf you planned migration work around the October 2026 deadline, you now have six additional months. Teams that deprioritized gpt-4.1-nano migration because of the tight timeline can reschedule without urgency.
WHAT TO DOCheck your migration backlog for gpt-4.1-nano work scheduled before 2027-04-14. If you deferred it due to the October deadline, update the target date and reprioritize against other work.
CONFIDENCE 95% Primary source ↗ written by anthropic/claude-sonnet-4.5
Show the reasoning — raw diff, triage verdict, confidence
RAW DIFF
 
 gpt-4.1
 2025-04-14
-Deprecated
+Legacy
 2027-04-14

 
 gpt-4.1-mini
 2025-04-14
-Deprecated
+Legacy
 2027-04-14

 
 gpt-4.1-nano
 2025-04-14
-Deprecated
-2026-10-14
+Legacy
+2027-04-14

 
 gpt-4o
@@
 
 gpt-4o
 2024-11-20
-Deprecated
+Legacy
 2027-04-14
 gpt-5.1
 
HOW IT WAS JUDGED
triage verdictMATERIAL at 0.92, needed 0.45
triage reasoningModel retirement dates extended and status reclassified; affects deployment planning and migration timelines.
signalsstatus label changed from 'Deprecated' to 'Legacy' · gpt-4.1-nano retirement date extended from 2026-10-14 to 2027-04-14 · multiple models affected · sunset dates are future dates paired with retirement timeline
suppression
triage modelanthropic/claude-haiku-4.5 ($0.00000)
writer modelanthropic/claude-sonnet-4.5 ($0.00000)
WORTH KNOWING MODELDEPRECATION Azure Foundry model retirement schedule · 2026-08-19 18:36 UTC

DeepSeek-V4-Flash-0731 preview ends 2026-12-03, GA 2026-07-31

DOCheck if any code or configs reference DeepSeek-V4-Flash-0731 in preview.
WHAT CHANGEDAzure added DeepSeek-V4-Flash-0731 to the retirement schedule. The model enters GA on 2026-07-31 and preview access ends on 2026-12-03.
WHY IT MATTERSIf you are testing this model in preview, you have until 2026-12-03 to migrate to the GA version or switch models. Preview endpoints will stop working after that date.
WHAT TO DOCheck if any code or configs reference DeepSeek-V4-Flash-0731 in preview. If so, schedule migration to the GA version before 2026-12-03.
CONFIDENCE 85% Primary source ↗ written by anthropic/claude-sonnet-4.5
Show the reasoning — raw diff, triage verdict, confidence
RAW DIFF
 2026-04-23
 GA
 2028-02-20
+DeepSeek-V4-Flash-0731
+
+DeepSeek-V4-Flash-0731
+2026-07-31
+Preview
+2026-12-03

 
 DeepSeek-V4-Pro
@@
 Suggest a fix?
 
 Last updated on
-2026-08-17
+2026-08-19
HOW IT WAS JUDGED
triage verdictMATERIAL at 0.95, needed 0.45
triage reasoningNew model added to public retirement schedule with defined preview and GA dates.
signalsnew model added to retirement schedule · model name: DeepSeek-V4-Flash-0731 · preview end date: 2026-12-03 · GA date: 2026-07-31 · retirement schedule table expanded
suppression
triage modelanthropic/claude-haiku-4.5 ($0.00000)
writer modelanthropic/claude-sonnet-4.5 ($0.00000)
ACTION NEEDED DEPRECATIONMODELAPI Azure Foundry model retirement schedule · 2026-08-18 01:15 UTC

Four Azure Foundry models retired, MAI-Transcribe-1 retiring 15 September 2026

DOGrep your codebase for 'DeepSeek-R1', 'MAI-Image-2', 'Stable-Diffusion-3.5-Large', 'Stable-Image-Core', 'Stable-Image-Ultra', and 'MAI-Transcribe-1'.
WHAT CHANGEDDeepSeek-R1, MAI-Image-2, Stable-Diffusion-3.5-Large, Stable-Image-Core, and Stable-Image-Ultra moved from Legacy/Preview/Deprecated to Retired status between 31 July and 15 August 2026. MAI-Transcribe-1 added to retirement schedule with cutoff date 15 September 2026. MAI-Transcribe-1.5 added as successor model.
WHY IT MATTERSRetired models are no longer callable via API. Any code still referencing DeepSeek-R1, MAI-Image-2, or the three Stable models will fail. MAI-Transcribe-1 stops working in 28 days.
WHAT TO DOGrep your codebase for 'DeepSeek-R1', 'MAI-Image-2', 'Stable-Diffusion-3.5-Large', 'Stable-Image-Core', 'Stable-Image-Ultra', and 'MAI-Transcribe-1'. Remove or replace references before 15 September 2026 for MAI-Transcribe-1; the other five are already dead.
CONFIDENCE 95% Primary source ↗ written by anthropic/claude-sonnet-4.5
Show the reasoning — raw diff, triage verdict, confidence
RAW DIFF
 
 DeepSeek-R1
 1
-Legacy
+Retired
 2026-08-13
 DeepSeek-V4-Pro
 
@@
 
 MAI-Image-2
 2026-02-20
-Preview
+Retired
 2026-08-15
 MAI-Image-2.5
 
+MAI-Transcribe-1
+2026-01-23
+Preview
+2026-09-15
+MAI-Transcribe-1.5
+
 Mistral AI
 
 Model
@@
 
 Stable-Diffusion-3.5-Large
 1
-Deprecated
+Retired
 2026-07-31

 
 Stable-Image-Core
 1
-Deprecated
+Retired
 2026-07-31

 
 Stable-Image-Ultra
 1
-Deprecated
+Retired
 2026-07-31

 
@@
 Suggest a fix?
 
 Last updated on
-2026-07-24
+2026-08-17
HOW IT WAS JUDGED
triage verdictMATERIAL at 0.95, needed 0.45
triage reasoningMultiple models moved to Retired status with concrete sunset dates. New models added to retirement schedule.
signalsstatus label changes from Legacy/Preview/Deprecated to Retired · retirement dates present (2026-07-31, 2026-08-13, 2026-08-15, 2026-09-15) · new model entries added (MAI-Transcribe-1, MAI-Transcribe-1.5) · multiple models transitioned to final retirement state · documentation timestamp updated
suppression
triage modelanthropic/claude-haiku-4.5 ($0.00000)
writer modelanthropic/claude-sonnet-4.5 ($0.00000)
WORTH KNOWING API Claude Platform release notes · 2026-08-17 00:11 UTC

Claude API adds anthropic-workspace-id response header

DOCheck whether your HTTP client or logging pipeline treats unexpected headers as errors.
WHAT CHANGEDThe Claude API now returns an anthropic-workspace-id header in all responses, containing the wrkspc_-prefixed workspace ID that the request's API key or access token resolved to, including the organization's Default Workspace. This applies to all API requests immediately.
WHY IT MATTERSIf you parse API responses or log headers for debugging, this new header will appear in all responses. Multi-workspace organizations can now programmatically identify which workspace handled each request without inferring from the API key alone.
WHAT TO DOCheck whether your HTTP client or logging pipeline treats unexpected headers as errors. If you operate multiple workspaces, decide whether to log this header for request attribution.
CONFIDENCE 85% Primary source ↗ written by anthropic/claude-sonnet-4.5
Show the reasoning — raw diff, triage verdict, confidence
RAW DIFF
 Tue, 11 Aug 2026 00:00:00 GMT
 
 The Compliance API now returns transcripts of Cowork and Claude Code sessions that run on your users' machines, in beta for Claude Enterprise organizations. GET /v1/compliance/apps/sessions/local lists sessions across your organization, GET /v1/compliance/apps/sessions/local/{session_id} retrieves one session's metadata, and GET /v1/compliance/apps/sessions/local/{session_id}/messages returns its transcript, all with your existing Compliance Access Key and the read:compliance_user_data scope. See Retrieve local sessions.
+We've added the anthropic-workspace-id response header to the Claude API. It carries the wrkspc_-prefixed ID of the workspace that the request's API key or access token resolved to, including your organization's Default Workspace. See Identify the workspace behind an API response.
 
 ## Claude Platform release notes — August 12, 2025
 https://platform.claude.com/docs/en/release-notes/overview#august-12-2025
HOW IT WAS JUDGED
triage verdictMATERIAL at 0.92, needed 0.45
triage reasoningNew API endpoints and response headers enable previously unavailable data access patterns for compliance use cases.
signalsnew API endpoint added (GET /v1/compliance/apps/sessions/local) · new API endpoint added (GET /v1/compliance/apps/sessions/local/{session_id}) · new API endpoint added (GET /v1/compliance/apps/sessions/local/{session_id}/messages) · new response header added (anthropic-workspace-id) · new scope introduced (read:compliance_user_data) · beta feature for Enterprise tier · data access capability change (local session transcripts now retrievable)
suppression
triage modelanthropic/claude-haiku-4.5 ($0.00000)
writer modelanthropic/claude-sonnet-4.5 ($0.00000)
WORTH KNOWING APISECURITY Claude Platform release notes · 2026-08-17 00:11 UTC

Compliance API now retrieves local Cowork and Claude Code session transcripts

DOIf you run compliance exports or audits, add these three endpoints to your retrieval jobs.
WHAT CHANGEDThree new Compliance API endpoints launched August 11, 2026 in beta for Enterprise organizations: GET /v1/compliance/apps/sessions/local lists all local sessions, GET /v1/compliance/apps/sessions/local/{session_id} retrieves session metadata, and GET /v1/compliance/apps/sessions/local/{session_id}/messages returns the full transcript. These cover Cowork and Claude Code sessions running on user machines. Authentication uses existing Compliance Access Keys with read:compliance_user_data scope.
WHY IT MATTERSYour compliance tooling can now audit conversations that happen in desktop applications, not just API calls. If you already pull compliance data for governance or retention, these sessions were previously invisible and are now retrievable through the same authentication mechanism.
WHAT TO DOIf you run compliance exports or audits, add these three endpoints to your retrieval jobs. Test with GET /v1/compliance/apps/sessions/local using your existing Compliance Access Key to confirm scope and verify the transcript format matches your storage schema.
CONFIDENCE 85% Primary source ↗ written by anthropic/claude-sonnet-4.5
Show the reasoning — raw diff, triage verdict, confidence
RAW DIFF
 https://platform.claude.com/docs/en/release-notes/overview#april-14-2026
 Tue, 14 Apr 2026 00:00:00 GMT
 
-We announced the deprecation of the Claude Sonnet 4 model (claude-sonnet-4-20250514) and the Claude Opus 4 model (claude-opus-4-20250514), with retirement on the Claude API scheduled for June 15, 2026. We recommend migrating to Claude Sonnet 4.6 and Claude Opus 4.8 respectively. Read more in model deprecations.
+We announced the deprecation of the Claude Sonnet 4 model (claude-sonnet-4-20250514) and the Claude Opus 4 model (claude-opus-4-20250514), with retirement on the Claude API scheduled for June 15, 2026. We recommend migrating to Claude Sonnet 4.6 and Claude Opus 4.8 respectively. Read more in Model deprecations.
 
 ## Claude Platform release notes — April 16, 2026
 https://platform.claude.com/docs/en/release-notes/overview#april-16-2026
@@
 
 Some customers might encounter 429 (rate_limit_error) errors following a sharp increase in API usage due to acceleration limits on the API. Previously, 529 (overloaded_error) errors would occur in similar scenarios.
 
+## Claude Platform release notes — August 11, 2026
+https://platform.claude.com/docs/en/release-notes/overview#august-11-2026
+Tue, 11 Aug 2026 00:00:00 GMT
+
+The Compliance API now returns transcripts of Cowork and Claude Code sessions that run on your users' machines, in beta for Claude Enterprise organizations. GET /v1/compliance/apps/sessions/local lists sessions across your organization, GET /v1/compliance/apps/sessions/local/{session_id} retrieves one session's metadata, and GET /v1/compliance/apps/sessions/local/{session_id}/messages returns its transcript, all with your existing Compliance Access Key and the read:compliance_user_data scope. See Retrieve local sessions.
+
 ## Claude Platform release notes — August 12, 2025
 https://platform.claude.com/docs/en/release-notes/overview#august-12-2025
 Tue, 12 Aug 2025 00:00:00 GMT
@@
 Wed, 05 Aug 2026 00:00:00 GMT
 
 Inference hooks are now in beta for Claude Enterprise organizations. Point Claude at your organization's AI security server, and each governed prompt across claude.ai, Cowork, and Claude Code is held for the server's allow or deny verdict before inference proceeds. Requests are signed, failure handling is configurable, and every denial is recorded in the compliance Activity Feed. See Inference hooks.
-We've retired the Claude Opus 4.1 model (claude-opus-4-1-20250805). All requests to this model will now return an error. We recommend upgrading to Claude Opus 5. Researchers can request ongoing access through the External Researcher Access Program.
+We've retired the Claude Opus 4.1 model (claude-opus-4-1-20250805). All requests to this model on the Claude API will now return an error. We recommend upgrading to Claude Opus 5. Researchers can request ongoing access through the External Researcher Access Program.
 
+## Claude Platform release notes — August 7, 2026
+https://platform.claude.com/docs/en/release-notes/overview#august-7-2026
+Fri, 07 Aug 2026 00:00:00 GMT
+
+You can now set a budget on a Claude Managed Agents session: a hard cap on the session's spend, priced at public list rates. A session that reaches its budget pauses with the budget_reached stop reason instead of starting new model requests; changing or removing the budget resumes it. Deployments accept the same budget and apply it to each session they start. See Session budgets.
+You can now give a Claude Managed Agents session an advisor: a model at least as capable as the agent's own that the session's primary thread can consult mid-turn for strategic guidance. Configure it as a {"type": "advisor"} entry in the agent's multiagent roster, naming the model to consult. See Give the session an advisor.
+You can now control where model inference runs for a Claude Managed Agents agent. Set inference_geo inside the model object when you create the agent, or override it for a single session. See Data residency for the available geos and pricing.
+Claude Managed Agents sessions can now load skills from a GitHub repository. When a session mounts a repository, any skills in its root .claude/skills directory are discovered automatically at session start and available to the agent for that session.
+
 ## Claude Platform release notes — August 8, 2025
 https://platform.claude.com/docs/en/release-notes/overview#august-8-2025
 Fri, 08 Aug 2025 00:00:00 GMT
@@
 Thu, 19 Feb 2026 00:00:00 GMT
 
 We've launched automatic caching for the Messages API. Add a single cache_control field to your request body and the system automatically caches the last cacheable block, moving the cache point forward as conversations grow. No manual breakpoint management required. Works alongside existing block-level cache control for fine-grained optimization. Available on the Claude API and Microsoft Foundry (preview). Learn more in Prompt caching.
-We've retired the Claude Sonnet 3.7 model (claude-3-7-sonnet-20250219) and the Claude Haiku 3.5 model (claude-3-5-haiku-20241022). All requests to these models will now return an error. We recommend upgrading to Claude Sonnet 4.6 and Claude Haiku 4.5 respectively. Researchers can request ongoing access through the External Researcher Access Program.
+We've retired the Claude Sonnet 3.7 model (claude-3-7-sonnet-20250219) and the Claude Haiku 3.5 model (claude-3-5-haiku-20241022). All requests to Claude Sonnet 3.7 will now return an error. Requests to Claude Haiku 3.5 on the Claude API will now return an error; it remains available on Amazon Bedrock and Google Cloud. We recommend upgrading to Claude Sonnet 4.6 and Claude Haiku 4.5 respectively. Researchers can request ongoing access through the External Researcher Access Program.
 We announced the deprecation of the Claude Haiku 3 model (claude-3-haiku-20240307), with retirement scheduled for April 20, 2026. We recommend migrating to Claude Haiku 4.5. Read more in Model deprecations.
 
 ## Claude Platform release notes — February 24th, 2025
@@
 https://platform.claude.com/docs/en/release-notes/overview#june-15-2026
 Mon, 15 Jun 2026 00:00:00 GMT
 
-We've retired the Claude Sonnet 4 model (claude-sonnet-4-20250514) and the Claude Opus 4 model (claude-opus-4-20250514). All requests to these models will now return an error. We recommend upgrading to Claude Sonnet 4.6 and Claude Opus 4.8 respectively. Researchers can request ongoing access through the External Researcher Access Program.
+We've retired the Claude Sonnet 4 model (claude-sonnet-4-20250514) and the Claude Opus 4 model (claude-opus-4-20250514). All requests to these models on the Claude API will now return an error. We recommend upgrading to Claude Sonnet 4.6 and Claude Opus 4.8 respectively. Researchers can request ongoing access through the External Researcher Access Program.
 
 ## Claude Platform release notes — June 18, 2026
 https://platform.claude.com/docs/en/release-notes/overview#june-18-2026
@@
 https://platform.claude.com/docs/en/release-notes/overview#june-5-2026
 Fri, 05 Jun 2026 00:00:00 GMT
 
-We announced the deprecation of the Claude Opus 4.1 model (claude-opus-4-1-20250805), with retirement on the Claude API scheduled for August 5, 2026. We recommend migrating to Claude Opus 4.8. Read more in model deprecations.
+We announced the deprecation of the Claude Opus 4.1 model (claude-opus-4-1-20250805), with retirement on the Claude API scheduled for August 5, 2026. We recommend migrating to Claude Opus 4.8. Read more in Model deprecations.
 
 ## Claude Platform release notes — June 9, 2026
 https://platform.claude.com/docs/en/release-notes/overview#june-9-2026
HOW IT WAS JUDGED
triage verdictMATERIAL at 0.92, needed 0.45
triage reasoningMultiple new API capabilities, features, and endpoints added; model availability clarified across platforms.
signalsnew API endpoints added (Compliance API for local sessions) · new feature: Claude Managed Agents session budgets with hard spend caps · new feature: Claude Managed Agents advisor model capability · new feature: data residency control (inference_geo) for agents · new feature: GitHub repository skill loading for agents · model retirement clarification (Claude Haiku 3.5 remains on Bedrock/GCP) · multiple new release notes entries (Aug 7, Aug 11, 2026)
suppression
triage modelanthropic/claude-haiku-4.5 ($0.00000)
writer modelanthropic/claude-sonnet-4.5 ($0.00000)
WORTH KNOWING PRICINGMODEL Claude Platform release notes · 2026-08-17 00:11 UTC

Claude Sonnet 5 introductory pricing made permanent, September increase cancelled

DOReforecast Claude Sonnet 5 spend using $2/$10 rates with no September step-up.
WHAT CHANGEDClaude Sonnet 5 pricing remains at $2 input / $10 output per MTok indefinitely. The previously scheduled increase to $3 / $15 per MTok on September 1, 2026 will not occur, announced August 10, 2026.
WHY IT MATTERSIf you budgeted for the September price increase or delayed Sonnet 5 adoption expecting higher costs, your forecast is now wrong by 33-50% depending on input/output mix. Teams that pinned to older models to avoid the increase can now migrate without the cost penalty.
WHAT TO DOReforecast Claude Sonnet 5 spend using $2/$10 rates with no September step-up. If you delayed migration from Sonnet 4.6 due to the planned increase, re-evaluate the timeline—the cost barrier is gone.
CONFIDENCE 95% Primary source ↗ written by anthropic/claude-sonnet-4.5
Show the reasoning — raw diff, triage verdict, confidence
RAW DIFF
 
 Dreams (research preview) now supports Claude Opus 5. See Supported models.
 
+## Claude Platform release notes — August 10, 2026
+https://platform.claude.com/docs/en/release-notes/overview#august-10-2026
+Mon, 10 Aug 2026 00:00:00 GMT
+
+The introductory pricing for Claude Sonnet 5 ($2 / $10 per MTok) is now the standard price: the previously scheduled increase to $3 / $15 per MTok on September 1, 2026 will not occur. See Pricing.
+
 ## Claude Platform release notes — August 11, 2025
 https://platform.claude.com/docs/en/release-notes/overview#august-11-2025
 Mon, 11 Aug 2025 00:00:00 GMT
@@
 
 We launched a beta version of the PHP SDK.
 
+## Claude Platform release notes — August 3, 2026
+https://platform.claude.com/docs/en/release-notes/overview#august-3-2026
+Mon, 03 Aug 2026 00:00:00 GMT
+
+The Compliance API now returns transcripts of Cowork sessions started on claude.ai web or mobile, in beta for Claude Enterprise organizations. GET /v1/compliance/apps/sessions/remote lists sessions and GET /v1/compliance/apps/sessions/remote/{session_id}/messages returns one session's transcript, using your existing Compliance Access Key with the read:compliance_user_data scope. See Retrieve remote sessions.
+
 ## Claude Platform release notes — August 5, 2025
 https://platform.claude.com/docs/en/release-notes/overview#august-5-2025
 Tue, 05 Aug 2025 00:00:00 GMT
@@
 Wed, 05 Aug 2026 00:00:00 GMT
 
 Inference hooks are now in beta for Claude Enterprise organizations. Point Claude at your organization's AI security server, and each governed prompt across claude.ai, Cowork, and Claude Code is held for the server's allow or deny verdict before inference proceeds. Requests are signed, failure handling is configurable, and every denial is recorded in the compliance Activity Feed. See Inference hooks.
+We've retired the Claude Opus 4.1 model (claude-opus-4-1-20250805). All requests to this model will now return an error. We recommend upgrading to Claude Opus 5. Researchers can request ongoing access through the External Researcher Access Program.
 
 ## Claude Platform release notes — August 8, 2025
 https://platform.claude.com/docs/en/release-notes/overview#august-8-2025
@@
 https://platform.claude.com/docs/en/release-notes/overview#june-30-2026
 Tue, 30 Jun 2026 00:00:00 GMT
 
-We've launched Claude Sonnet 5 (claude-sonnet-5), the next generation of our Sonnet model family, at introductory pricing of $2 / $10 per MTok through August 31, 2026 (standard $3 / $15 thereafter). Claude Sonnet 5 supports a 1M token context window, 128k max output tokens, and the same set of tools and platform features as Claude Sonnet 4.6, except Priority Tier, which is not available on Claude Sonnet 5. Three behavior changes apply when migrating: adaptive thinking is now on by default; manual extended thinking (thinking: {type: "enabled", budget_tokens: N}) is removed and returns a 400 error (it was deprecated on Sonnet 4.6); and setting sampling parameters (temperature, top_p, top_k) to non-default values returns a 400 error. Claude Sonnet 5 also uses a new tokenizer that produces approximately 30% more tokens for the same text. The exact increase depends on the content and workload shape. See What's new in Claude Sonnet 5 for details and migration guidance. For behavioral differences and model-specific prompting patterns, see Prompting Claude Sonnet 5.
+We've launched Claude Sonnet 5 (claude-sonnet-5), the next generation of our Sonnet model family, at introductory pricing of $2 / $10 per MTok (made the standard price on August 10, 2026). Claude Sonnet 5 supports a 1M token context window, 128k max output tokens, and the same set of tools and platform features as Claude Sonnet 4.6, except Priority Tier, which is not available on Claude Sonnet 5. Three behavior changes apply when migrating: adaptive thinking is now on by default; manual extended thinking (thinking: {type: "enabled", budget_tokens: N}) is removed and returns a 400 error (it was deprecated on Sonnet 4.6); and setting sampling parameters (temperature, top_p, top_k) to non-default values returns a 400 error. Claude Sonnet 5 also uses a new tokenizer that produces approximately 30% more tokens for the same text. The exact increase depends on the content and workload shape. See What's new in Claude Sonnet 5 for details and migration guidance. For behavioral differences and model-specific prompting patterns, see Prompting Claude Sonnet 5.
 Claude Managed Agents session event streams now support event deltas. Opt in with the event_deltas[] query parameter on GET /v1/sessions/{session_id}/events/stream. The event_start and event_delta events preview an agent message's text as it's generated, before the complete agent.message event arrives.
 Listing sessions for Claude Managed Agents now supports backward pagination. GET /v1/sessions returns a prev_page cursor alongside next_page; pass it as the page parameter to return to the previous page. See Pagination.
 When creating a Claude Managed Agents session, you can now override the agent's configuration for that session. Pass agent with type: "agent_with_overrides" to replace the model, system prompt, tools, MCP servers, or skills for a single session. The agent itself is unchanged.
HOW IT WAS JUDGED
triage verdictMATERIAL at 0.98, needed 0.45
triage reasoningPricing locked at lower tier, model sunset with migration path, new compliance API endpoints, and enterprise feature additions.
signalspricing change: Claude Sonnet 5 introductory price ($2/$10 per MTok) made permanent; scheduled increase to $3/$15 cancelled · model retirement: Claude Opus 4.1 (claude-opus-4-1-20250805) retired, requests now error · future date with pricing impact: August 10, 2026 · new API endpoints: Compliance API now returns remote session transcripts (GET /v1/compliance/apps/sessions/remote) · new feature in beta: Inference hooks for Claude Enterprise
suppression
triage modelanthropic/claude-haiku-4.5 ($0.00000)
writer modelanthropic/claude-sonnet-4.5 ($0.00000)
SECURITY ADVISORY TRIAGE 0 RSS
AppSec and platform teams running hosted AI and cloud infrastructure
Watching, nothing material yet. An empty channel is a result, not a gap — it is shown so a configured-and-silent channel cannot be mistaken for one that does not exist.
REGULATORY CHANGE 0 RSS
Engineering and product leaders whose roadmap depends on what they may ship, where, and with what data
Watching, nothing material yet. An empty channel is a result, not a gap — it is shown so a configured-and-silent channel cannot be mistaken for one that does not exist.
CORRECTED — 4 withdrawn items
Published, then found wrong. Left in place with the reason — an item that can quietly disappear makes every other item unfalsifiable. Each counts as a false positive in the accuracy ledger.
CORRECTED Anthropic renamed Individual tier to Team, moved Claude Code to Max only
Duplicate of 26e9939b: the Anthropic pricing page was oscillating between two variants, producing a byte-identical diff every run. Suppressed by rule as of commit 917ce8a (oscillation / duplicate_diff). The underlying claim was later reviewed and found false: claude.com/pricing shows Claude Code in both Pro and Max, and "Individual" is a category header, not a tier. Publishing it five times compounded it.
Anthropic pricing · published 2026-09-21 23:45 UTC · corrected 2026-09-22 00:02 UTC
WHAT IT SAIDThe Individual pricing tier no longer exists; it has been renamed to Team. Claude Code, previously included in both Pro ($17/month) and Max (from $100/month), is now only included in the Max tier. The Pro tier description no longer lists Claude Code as a feature.
Full item and evidence ↗
CORRECTED Anthropic renamed Individual tier to Team, moved Claude Code to Max only
Duplicate of 26e9939b: the Anthropic pricing page was oscillating between two variants, producing a byte-identical diff every run. Suppressed by rule as of commit 917ce8a (oscillation / duplicate_diff). The underlying claim was later reviewed and found false: claude.com/pricing shows Claude Code in both Pro and Max, and "Individual" is a category header, not a tier. Publishing it five times compounded it.
Anthropic pricing · published 2026-09-21 23:44 UTC · corrected 2026-09-22 00:02 UTC
WHAT IT SAIDThe Individual pricing tier no longer exists; it has been renamed to Team. Claude Code, previously included in both Pro ($17/month) and Max (from $100/month), is now only included in the Max tier. The Pro tier description no longer lists Claude Code as a feature.
Full item and evidence ↗
CORRECTED Anthropic renamed Individual tier to Team, moved Claude Code to Max only
Duplicate of 26e9939b: the Anthropic pricing page was oscillating between two variants, producing a byte-identical diff every run. Suppressed by rule as of commit 917ce8a (oscillation / duplicate_diff). The underlying claim was later reviewed and found false: claude.com/pricing shows Claude Code in both Pro and Max, and "Individual" is a category header, not a tier. Publishing it five times compounded it.
Anthropic pricing · published 2026-09-21 23:44 UTC · corrected 2026-09-22 00:02 UTC
WHAT IT SAIDThe Individual pricing tier no longer exists; it has been renamed to Team. Claude Code, previously included in both Pro ($17/month) and Max (from $100/month), is now only included in the Max tier. The Pro tier description no longer lists Claude Code as a feature.
Full item and evidence ↗
CORRECTED Anthropic renamed Individual tier to Team, moved Claude Code to Max only
Duplicate of 26e9939b: the Anthropic pricing page was oscillating between two variants, producing a byte-identical diff every run. Suppressed by rule as of commit 917ce8a (oscillation / duplicate_diff). The underlying claim was later reviewed and found false: claude.com/pricing shows Claude Code in both Pro and Max, and "Individual" is a category header, not a tier. Publishing it five times compounded it.
Anthropic pricing · published 2026-09-21 23:44 UTC · corrected 2026-09-22 00:02 UTC
WHAT IT SAIDThe Individual pricing tier no longer exists; it has been renamed to Team. Claude Code, previously included in both Pro ($17/month) and Max (from $100/month), is now only included in the Max tier. The Pro tier description no longer lists Claude Code as a feature.
Full item and evidence ↗
SAMPLE OUTPUT — NOT LIVE DETECTIONS
Produced by the same prompts, thresholds and validation as the live pipeline, run against hand-labeled diffs written to sit on the boundary between cosmetic and material. Kept visibly separate because a published precision figure means nothing if sample output can hide inside it.
ACTION NEEDED PRICING vendor pricing page · 2026-08-07 02:41 UTC

Claude batch API discount drops from 50% to 40% on 1 September 2026

DOReview batch API usage in your billing dashboard and update budget forecasts for Q4 2026.
SAMPLE — generated by the live prompts from the hand-labeled evaluation set. Not a live detection. Excluded from the accuracy ledger.
WHAT CHANGEDAnthropic's batch request discount decreases from 50% to 40% of standard rates, effective 1 September 2026.
WHY IT MATTERSBatch processing costs increase by 20% relative to current pricing. A workload currently costing $500/month in batch mode will cost $600/month after the change.
WHAT TO DOReview batch API usage in your billing dashboard and update budget forecasts for Q4 2026. If batch volume is high, evaluate whether moving some workloads to real-time API or alternative providers changes your cost structure.
CONFIDENCE 95% Primary source ↗ written by anthropic/claude-sonnet-4.5
Show the reasoning — raw diff, triage verdict, confidence
RAW DIFF
- Batch requests receive a 50% discount on standard rates.
+ Batch requests receive a 40% discount on standard rates.
+ Effective 1 September 2026.
HOW IT WAS JUDGED
triage verdictMATERIAL at 0.95, needed 0.5
triage reasoningBatch pricing discount decreased materially with a future effective date.
signalspricing change: discount reduced from 50% to 40% · future effective date: 1 September 2026
suppressionsurvived all deterministic rules
triage modelanthropic/claude-haiku-4.5 ($0.00154)
writer modelanthropic/claude-sonnet-4.5 ($0.00646)
ACTION NEEDED APIDEPRECATION vendor docs — SDK · 2026-08-07 02:41 UTC

Python SDK minimum version raised from 3.9 to 3.11

DOAudit all environments using this SDK for Python version.
SAMPLE — generated by the live prompts from the hand-labeled evaluation set. Not a live detection. Excluded from the accuracy ledger.
WHAT CHANGEDThe SDK now requires Python 3.11 or later, up from Python 3.9. This applies to the current release as of 7 August 2026.
WHY IT MATTERSDeployments running Python 3.9 or 3.10 will break on the next SDK update. CI/CD pipelines, production containers, and Lambda runtimes below 3.11 will fail to install or run the new SDK version.
WHAT TO DOAudit all environments using this SDK for Python version. Pin the SDK to the last 3.9-compatible release in requirements.txt until you can upgrade the runtime, or schedule Python 3.11 upgrades before your next SDK update.
CONFIDENCE 95% Primary source ↗ written by anthropic/claude-sonnet-4.5
Show the reasoning — raw diff, triage verdict, confidence
RAW DIFF
- Requires Python 3.9 or later.
+ Requires Python 3.11 or later.
HOW IT WAS JUDGED
triage verdictMATERIAL at 0.92, needed 0.5
triage reasoningMinimum Python version requirement raised from 3.9 to 3.11, forcing SDK users to upgrade their runtime environment.
signalsversion floor increased · breaking change for existing deployments · affects SDK usability and compatibility
suppressionsurvived all deterministic rules
triage modelanthropic/claude-haiku-4.5 ($0.00155)
writer modelanthropic/claude-sonnet-4.5 ($0.00687)
ACTION NEEDED TERMS vendor terms of service · 2026-08-07 02:41 UTC

Free and Starter plan data now used for training

DOAudit which systems use Free or Starter API keys.
SAMPLE — generated by the live prompts from the hand-labeled evaluation set. Not a live detection. Excluded from the accuracy ledger.
WHAT CHANGEDClaude platform now states that inputs and outputs from Free and Starter plans may be used to improve services. Enterprise plans are explicitly excluded from this policy.
WHY IT MATTERSAny prompts, API calls, or generated content on Free/Starter tiers can now train future models. This affects confidentiality of customer data, internal tooling prompts, and any proprietary information passed through the API on these plans.
WHAT TO DOAudit which systems use Free or Starter API keys. If any handle non-public data, customer information, or proprietary prompts, either upgrade those projects to Enterprise or migrate to a provider with blanket training opt-out.
CONFIDENCE 95% Primary source ↗ written by anthropic/claude-sonnet-4.5
Show the reasoning — raw diff, triage verdict, confidence
RAW DIFF
+ Customers on Free and Starter plans: inputs and outputs may be used
+ to improve our services. Enterprise plans are excluded.
HOW IT WAS JUDGED
triage verdictMATERIAL at 0.92, needed 0.5
triage reasoningNew clause explicitly permits using customer data to improve services on non-Enterprise plans, a material change to data handling terms.
signalsdata handling terms changed · training data usage policy clarified · plan-level differentiation introduced · Enterprise exemption stated
suppressionsurvived all deterministic rules
triage modelanthropic/claude-haiku-4.5 ($0.00158)
writer modelanthropic/claude-sonnet-4.5 ($0.00660)
ACTION NEEDED TERMS vendor terms of service · 2026-08-07 02:41 UTC

Claude API input retention period changed from 30 days to indefinite

DOReview your privacy policy, data processing agreements, and compliance documentation for references to the 30-day retention period.
SAMPLE — generated by the live prompts from the hand-labeled evaluation set. Not a live detection. Excluded from the accuracy ledger.
WHAT CHANGEDThe documented retention period for API inputs changed from 'up to 30 days' to 'as required' for abuse monitoring purposes. The specific time limit has been removed.
WHY IT MATTERSYour data retention and privacy documentation may now be inaccurate if it references the 30-day limit. Compliance frameworks requiring documented retention periods no longer have a specific commitment to cite.
WHAT TO DOReview your privacy policy, data processing agreements, and compliance documentation for references to the 30-day retention period. Update or remove specific timeframes and assess whether 'as required' meets your contractual obligations to end users.
CONFIDENCE 90% Primary source ↗ written by anthropic/claude-sonnet-4.5
Show the reasoning — raw diff, triage verdict, confidence
RAW DIFF
- Inputs are retained for up to 30 days for abuse monitoring.
+ Inputs are retained as required for abuse monitoring.
HOW IT WAS JUDGED
triage verdictMATERIAL at 0.85, needed 0.5
triage reasoningRetention commitment shifted from bounded 30-day limit to open-ended 'as required,' materially altering data handling guarantees.
signalsdata retention period softened from specific limit to indefinite · commitment weakened from 'up to 30 days' to 'as required' · change to data handling terms per channel rules
suppressionsurvived all deterministic rules
triage modelanthropic/claude-haiku-4.5 ($0.00169)
writer modelanthropic/claude-sonnet-4.5 ($0.00660)
WORTH KNOWING LIMITSAPI vendor rate limits page · 2026-08-07 02:41 UTC

Claude API Tier 2 rate limit doubled to 10,000 RPM

DOReview your current request patterns and remove any client-side rate limiting code that was added to stay under the previous 5,000 RPM ceiling.
SAMPLE — generated by the live prompts from the hand-labeled evaluation set. Not a live detection. Excluded from the accuracy ledger.
WHAT CHANGEDThe Tier 2 rate limit increased from 5,000 requests per minute to 10,000 requests per minute on the Claude API platform.
WHY IT MATTERSApplications currently throttling at Tier 2 limits can now handle twice the request volume without upgrading tiers or implementing additional rate limiting logic.
WHAT TO DOReview your current request patterns and remove any client-side rate limiting code that was added to stay under the previous 5,000 RPM ceiling.
CONFIDENCE 95% Primary source ↗ written by anthropic/claude-sonnet-4.5
Show the reasoning — raw diff, triage verdict, confidence
RAW DIFF
- Tier 2: 5,000 requests per minute
+ Tier 2: 10,000 requests per minute
HOW IT WAS JUDGED
triage verdictMATERIAL at 0.98, needed 0.45
triage reasoningRate limit increase directly affects engineering capacity planning and API quota allocation.
signalsrate limit changed · numeric value doubled · tier capacity increased
suppressionsurvived all deterministic rules
triage modelanthropic/claude-haiku-4.5 ($0.00148)
writer modelanthropic/claude-sonnet-4.5 ($0.00610)
ACTION NEEDED MODELDEPRECATION vendor models list · 2026-08-07 02:41 UTC

model-v2-mini removed from generally available tier

DOGrep your codebase for 'model-v2-mini' references and identify all API calls using this model identifier.
SAMPLE — generated by the live prompts from the hand-labeled evaluation set. Not a live detection. Excluded from the accuracy ledger.
WHAT CHANGEDThe model-v2-mini has been removed from the generally available models list on the Claude platform documentation, effective as of the August 7, 2026 documentation update.
WHY IT MATTERSAny production code calling model-v2-mini will fail once the model is deprovisioned. Existing integrations will break without a migration path to a replacement model.
WHAT TO DOGrep your codebase for 'model-v2-mini' references and identify all API calls using this model identifier. Contact Claude support to confirm the deprecation timeline and recommended replacement model before the cutoff date.
CONFIDENCE 85% Primary source ↗ written by anthropic/claude-sonnet-4.5
Show the reasoning — raw diff, triage verdict, confidence
RAW DIFF
- | model-v2-mini | generally available |
HOW IT WAS JUDGED
triage verdictMATERIAL at 0.92, needed 0.45
triage reasoningA model has been removed from the available offerings, affecting deployment options.
signalsmodel removed from supported list · removal from generally available tier
suppressionsurvived all deterministic rules
triage modelanthropic/claude-haiku-4.5 ($0.00143)
writer modelanthropic/claude-sonnet-4.5 ($0.00633)
ACTION NEEDED DEPRECATIONAPI vendor deprecations page · 2026-08-07 02:41 UTC

legacy-completions endpoint deprecated, removal on 2026-11-04

DOGrep your codebase for 'legacy-completions' or the old endpoint path.
SAMPLE — generated by the live prompts from the hand-labeled evaluation set. Not a live detection. Excluded from the accuracy ledger.
WHAT CHANGEDClaude platform added a deprecation entry for the legacy-completions endpoint with an end-of-life date of 2026-11-04. A migration guide is referenced.
WHY IT MATTERSCode calling this endpoint will break after 2026-11-04. Any production systems using legacy-completions must migrate to the current API before that date or face service interruption.
WHAT TO DOGrep your codebase for 'legacy-completions' or the old endpoint path. If found, follow the migration guide linked in the deprecation notice and schedule the migration before 2026-11-04.
CONFIDENCE 95% Primary source ↗ written by anthropic/claude-sonnet-4.5
Show the reasoning — raw diff, triage verdict, confidence
RAW DIFF
+ | legacy-completions | 2026-11-04 | See migration guide |
HOW IT WAS JUDGED
triage verdictMATERIAL at 0.92, needed 0.45
triage reasoningNew deprecation with concrete sunset date signals actionable timeline for engineering teams.
signalsfuture sunset date · new deprecation entry · specific end-of-life date (2026-11-04) · migration guidance referenced
suppressionsurvived all deterministic rules
triage modelanthropic/claude-haiku-4.5 ($0.00156)
writer modelanthropic/claude-sonnet-4.5 ($0.00651)

INTERPRETATION

Interpretation — healthy
Last model call 2026-09-24 03:31 UTC.

SOURCE HEALTH

ACCURACY LEDGER

Published75
Confirmed material0
False positives0
Awaiting review75
No precision figure yet. 0 of 10 items reviewed — a percentage over a handful is an anecdote with a decimal point, so none is shown until there are enough to mean something. Sample output is excluded. A ledger you can pad is not a ledger.

RUN ECONOMICS

Published items, all time75
Action needed, all time32
Runs logged200
Runs without error99.0%
Runs with errors2
Changes detected50
Total model cost$1.1607
Last run2026-09-24 04:30 UTC
green = checked, nothing changed · blue = change detected · red = error

FEEDS

JSONeverything
RSSeverything
12 filtered feeds
Subscribe to one slice in a reader you already use. No account, no preferences screen.