惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

U
Unit 42
Google DeepMind News
Google DeepMind News
Stack Overflow Blog
Stack Overflow Blog
H
Help Net Security
MongoDB | Blog
MongoDB | Blog
I
InfoQ
N
Netflix TechBlog - Medium
T
Tailwind CSS Blog
量子位
博客园 - 叶小钗
月光博客
月光博客
IT之家
IT之家
G
Google Developers Blog
钛媒体:引领未来商业与生活新知
钛媒体:引领未来商业与生活新知
小众软件
小众软件
S
SegmentFault 最新的问题
Engineering at Meta
Engineering at Meta
奇客Solidot–传递最新科技情报
奇客Solidot–传递最新科技情报
aimingoo的专栏
aimingoo的专栏
云风的 BLOG
云风的 BLOG
Vercel News
Vercel News
爱范儿
爱范儿
让小产品的独立变现更简单 - ezindie.com
让小产品的独立变现更简单 - ezindie.com
宝玉的分享
宝玉的分享

DEV Community

Authentication Security Deep Dive: From Brute Force to Salted Hashing (With Java Examples) Why AI Systems Don’t Fail — They Drift Spilling beans for how i learn for exam😁"Reinforcement Learning Cheat Sheet" I Replaced Chrome with Safari for AI Browser Automation. Here's What Broke (and What Finally Worked) How Python Borrows Other People's Work The $40 Architecture: Processing 1 Billion API Requests with 99.99% Uptime Vibe Coding: A Workflow Guide (From Zero to SaaS) Most webhook security guides protect the wrong side. The scary part is delivery. Headless CMS for TanStack Start: Build a Blog with Cosmic EU Age Verification App "Hacked in 2 Minutes" — What Actually Happened Comfy Cloud’s delete function does not actually remove files Running AI Models on GPU Cloud Servers: A Beginner Guide Event-driven media intelligence with AWS Step Functions and Bedrock I scored 500 AI prompts across 8 quality dimensions — here's what broke How to Call Google Gemini API from Next.js (Free Tier, No Backend Needed) The Portal Protocol: Reclaiming Human Connection in the Age of AI How to Fix Your Team's Scattered Knowledge Problem With a Self-Hosted Forum Intro to tc Cloud Functors: A Graph-First Mental Model for the Modern Cloud Designing Multi-Tenant Backends With Both Ownership and Team Access I Built a Neumorphic CSS Library with 77+ Components — Here's What I Learned PostgreSQL Performance Optimization: Why Connection Pooling Is Critical at Scale Cómo construí un SaaS multi-rubro para gestionar expensas en Argentina con FastAPI + Vue 3 🚀 I Built an Ethical Hacking Scanner Tool – Open Source Project I Replaced /usage and /context in Claude Code With a Single Statusline A Pythonic Way to Handle Emails (IMAP/SMTP) with Auto-Discovery and AI-Ready Design I Collected 8.9 Million Polymarket Price Points — Here's What I Found About How Markets Really Move EcoTrack AI — Carbon Footprint Tracker & Dashboard Everyone's Using AI. No One Agrees How. 5 self-hosted ebook managers worth trying in 2026 Building Your First AI Agent with LangChain: From Chatbot to Autonomous Assistant
LLM providers are retiring models faster than you can mig...
Model Radar · 2026-05-16 · via DEV Community

Model Radar

On May 15, 2026, xAI retired 8 Grok API models. The notice period was 9 days.

If you had grok-2, grok-3, or grok-4-fast pinned in production, here's the part that actually bites: the retired slugs don't hard-error. They silently redirect to grok-4.3 — reasoning models drop to low effort, non-reasoning to none — and you get billed at grok-4.3 pricing ($1.25 / $2.50 per 1M tokens). xAI's original retirement email said the requests would "no longer work"; a later docs update introduced the silent-redirect behavior. The two are contradictory, and either way your output quality and your bill changed without a single error in your logs.

This is not an xAI problem. It's the whole industry right now:

  • OpenAI removed chatgpt-4o-latest from the API on Feb 17, 2026. The Assistants API sunsets Aug 26, 2026.
  • Anthropic ends Claude Opus 4 and Sonnet 4 on Jun 15, 2026 (Opus 3 already retired Jan 5; Haiku 3 on Apr 19).
  • Google can shut off Gemini 2.0 Flash / Flash-Lite as early as Jun 1, 2026; they've been restricted to existing customers since Mar 6.

Pinning model IDs is correct — and it's now a liability

The standard advice is to pin explicit model versions for reproducibility, and that advice is right. A floating alias means your behavior changes silently under you. But a pinned ID means that when the provider retires it, you break — or worse, get silently rerouted. Either way, the failure mode is the same: something you depend on changed, and nobody told you in a channel you actually watch. Provider changelogs are scattered across docs pages, status pages, dashboard banners, and one-off emails to whatever address owns the billing account.

What I did about it

I started keeping a normalized, cross-provider timeline of every deprecation / breaking change / pricing change I could verify against provider docs: provider, model, event type, announced date, effective date, recommended replacement, source link.

It currently covers OpenAI, Anthropic, Gemini, and xAI. It's manually curated and fact-checked right now — the data is the hard part, not the page. If you spot a missing or wrong event, or a provider you want covered, tell me and I'll add it.

If you run anything against an LLM API in production, subscribe to the RSS feed or check it before your next deploy. The next 9-day notice is already on the calendar.