Anthropic cancels the Claude Sonnet 5 price increase, DeepSeek switches to peak/off-peak pricing today, Neon acquires the Electric team
The radar watched 63 sources across 32 tools this window and published 27 changes; these are the thirteen worth your attention, ranked. More than the usual ten, because this window genuinely produced that many changes clearing the bar, from a cancelled Claude Sonnet 5 price increase and a same-day DeepSeek pricing switch to a scope correction on Claude Haiku 3.5's retirement notice. Every item carries the before/after evidence the pipeline captured; expand it before you take our word.
The footnote on Anthropic's pricing page reading 'introductory pricing of $2/$10 per million input/output tokens through August 31, 2026; $3/$15 standard pricing thereafter' is gone, and this is not page cleanup: the docs pricing page now states that $2/$10 is Claude Sonnet 5's standard price and the increase scheduled for September 1 will not occur. Teams that budgeted for the 1.5x bump or planned migrations to dodge it can drop those plans.
pricinghigh
Removal of introductory pricing notation and terms for Claude API
Developers will no longer see the explicit introductory pricing rates ($2/$10) and the sunset date (August 31, 2026), or the standard pricing thereafter ($3/$15). This could affect pricing decisions and understanding of rate changes.
Evidence
−Input*
Output*
Write*
Read*
*Introductory pricing of $2/$10 per million input/output tokens through August 31, 2026; $3/$15 standard pricing thereafter.
DeepSeek's API moves from a vague "pricing will rise" warning to a concrete peak/off-peak schedule: peak hours (01:00–04:00 and 06:00–10:00 UTC) cost double the off-peak rate, with the new prices taking effect at 16:00 UTC today, August 16. Workloads that can shift outside those four-hour peak windows get cheaper inference for free; batch jobs and anything latency-insensitive are the obvious candidates to reschedule.
pricinghigh
DeepSeek API transitions from general price increase warning to specific peak/off-peak tiered pricing model
All DeepSeek API users will face new pricing structure effective August 16, 2026. Peak hours (01:00-04:00 and 06:00-10:00 UTC) charge double the off-peak rates. Off-peak rates are half of peak rates.
Evidence
−We plan to raise the overall pricing for DeepSeek API services in the near future, with a significant increase expected. Please plan your usage accordingly. The specific pricing plan will be subject to official notice.
+DeepSeek API pricing will be updated to peak / off-peak billing, with off-peak rates at half the peak rates. Peak hours are 01:00 - 04:00 and 06:00 - 10:00 UTC (all other hours are off-peak). The new prices take effect at 16:00 UTC on August 16, 2026
Neon is acquiring Electric, the team behind the Electric sync engine and PGlite, folding real-time sync and in-browser Postgres into Neon's stack. Teams using Electric standalone should watch for roadmap changes now that its team answers to a different owner; Neon users get a credible sync story without adding a separate vendor.
otherhigh
Electric team and technology joins Neon
Neon is acquiring Electric, the team behind the Electric sync engine and PGlite. This expands Neon's capabilities with data synchronization technology and PGlite.
Evidence
+Electric joins Neon. Electric, the team behind the Electric sync engine and PGlite, is joining Neon. The sync engine keeps data continuously synchronized betwee...
Zep pulled the public pricing for its "Emerging Companies" tier, previously $13,000/year for startups that raised $1M–$10M with SOC 2, HIPAA BAA, and guaranteed rate limits included. The page now just invites you to "get Zep Enterprise at an emerging company price," meaning that number is no longer something you can quote without talking to sales first.
pricinghigh
Emerging Companies tier pricing details and plan removed from pricing page
Emerging companies ($1M-$10M raised) no longer have publicly displayed pricing information for the dedicated tier; pricing details previously listed at $13,000/year with specific features are now unavailable without contacting sales
Evidence
−Zep for Emerging Companies
$13,000for your first year
Enterprise controls at a price built for companies that have raised between $1M and $10M.
Check your eligibility
Includes
Everything in Flex Plus
SOC 2 Type II, HIPAA BAA, and DPA
Guaranteed rate limits
BYOK via AWS KMS
More than double the included usage of Flex Plus
Shared Slack channel with the Zep team
+Fast growing venture-capital funded startup? Get Zep Enterprise at an emerging company price.
Anthropic quietly narrowed the scope of its Claude Haiku 3.5 retirement notice: the model is only dead on the Claude API, not on Amazon Bedrock or Google Cloud, where it keeps running. Anyone who read the original notice as a full retirement and started migrating everywhere can stop the Bedrock/GCP portion of that work; only direct Claude API callers still need to move to Claude Haiku 4.5.
deprecation
Clarity added: Claude Haiku 3.5 retirement is API-specific, not universal
Developers using Claude Haiku 3.5 on Amazon Bedrock or Google Cloud can continue using it; only Claude API users need to migrate to Claude Haiku 4.5.
Evidence
−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'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.
CrewAI bumped its torch dependency to 2.13.0 to close a security vulnerability. The release notes don't name a CVE or describe the exploit, but pulling the update is a routine dependency bump, not a breaking change, so there's no reason to wait for more detail before applying it.
otherhigh
Bump torch to version 2.13.0 to address security vulnerability.
Security patch for torch dependency - users should update to get the vulnerability fix.
Evidence
+Bump torch to version 2.13.0 to address security vulnerability.
GitHub Copilot's memory feature, retaining context across chat sessions, is now available in JetBrains IDEs, not just VS Code. It's a toggle in the Copilot settings portal, off by default per prior rollout pattern, so JetBrains users who want it need to turn it on rather than assume it's already running.
featurehigh
Copilot memory feature now available in GitHub Copilot for JetBrains to retain context across chat sessions
Users can maintain context between conversations without repeatedly providing the same project details or preferences. Managed via toggle in Copilot settings portal.
Evidence
+Copilot memory can now retain and recall useful information across agent chat sessions. This helps you maintain context between conversations instead of repeatedly providing the same project details or preferences.
Together AI added Qwen3.8-2.4T-A95B to its catalog at $2.50/$6.25 per million input/output tokens, with a $0.50 cached-input rate. It's a large model at that parameter count, worth benchmarking against whatever you're currently running on Together if quality per dollar on long-context or complex tasks matters to your workload.
featurehigh
Added Qwen3.8-2.4T-A95B model with pricing $2.50/$6.25 and cached token option
New model option available to users with standard and cached pricing tiers
Vercel Connect now exposes line-level visibility into the token lifecycle: filter events, track metrics, and forward data to any log drain. If you've been debugging token usage in Connect by guesswork, this closes that gap without needing a separate observability integration.
featurehigh
Vercel Connect adds observability support with token lifecycle tracking
Users can now filter events, track metrics, and forward data to log drains for better visibility into token usage in Vercel Connect
Evidence
+Vercel Connect adds line-level visibility into the token lifecycle. Filter events, track metrics, and forward data to any log drain endpoint.
DeepSeek-V4-Pro now supports the Responses API, which was previously limited to deepseek-v4-flash. Anyone who picked flash specifically to get Responses API compatibility can now move back to Pro without giving up that interface.
apihigh
DeepSeek-V4-Pro now supports Responses API
Developers using DeepSeek-V4-Pro can now use the Responses API, previously limited to deepseek-v4-flash model.
Evidence
−The Responses API currently only supports the deepseek-v4-flash model, and does not yet support the deepseek-v4-pro model. We will add support for the deepseek-v4-pro model in early August 2026.
The Compliance API now covers local sessions from Cowork and Claude Code, not just cloud-hosted ones, through three new beta endpoints for listing sessions, fetching metadata, and pulling transcripts. Claude Enterprise organizations doing audit or data-retention work finally get visibility into sessions that were running on employees' own machines.
feature
Compliance API expanded to support local sessions from Cowork and Claude Code
Claude Enterprise organizations can now retrieve transcripts and metadata from Cowork and Claude Code sessions running locally on users' machines using new endpoints: GET /v1/compliance/apps/sessions/local, GET /v1/compliance/apps/sessions/local/{session_id}, and GET /v1/compliance/apps/sessions/local/{session_id}/messages.
Evidence
+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
Claude Code fixed an MCP OAuth sign-in bug that broke authentication for servers using a pre-registered OAuth client, Slack among them, due to a redirect URI mismatch. If MCP OAuth sign-in to Slack or similar servers was failing before, it's worth retrying after upgrading rather than assuming it's a config problem on your end.
other
Fixed MCP OAuth sign-in redirect URI mismatch issue for pre-registered OAuth clients
Developers using MCP with pre-registered OAuth clients like Slack can now successfully authenticate without redirect URI mismatches.
Evidence
+Fixed MCP OAuth sign-in failing with a redirect URI mismatch for servers that use a pre-registered OAuth client, such as Slack
The Claude API now returns an anthropic-workspace-id response header carrying the requesting key or token's workspace ID, including the default workspace. Organizations routing logs or costs by workspace can now read that directly off every response instead of maintaining their own key-to-workspace mapping.
apihigh
New anthropic-workspace-id response header added to Claude API
Developers can now identify the workspace behind an API response using the new wrkspc_-prefixed header, enabling better workspace management and organization tracking.
Evidence
+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.