PulseAugur
LIVE 23:24:18
tool · [2 sources] ·
0
tool

xAI silently rebrands Grok models, increasing costs and altering behavior

xAI silently retired eight Grok model slugs on May 15, 2026, without requiring code changes from users. This change redirects requests to different, more expensive models and alters reasoning capabilities without explicit error signals. The silent nature of this deprecation means that cost attribution dashboards may become inaccurate, and applications relying on specific model behaviors could experience degraded performance or unexpected cost increases. AI

Summary written by gemini-2.5-flash-lite from 2 sources. How we write summaries →

IMPACT Developers face silent cost increases and potential performance degradation due to opaque model deprecations, necessitating robust monitoring and configuration management.

RANK_REASON The cluster describes a change to an existing product's API and pricing, not a new model release or significant industry shift.

Read on dev.to — LLM tag →

COVERAGE [2]

  1. dev.to — LLM tag TIER_1 · FlareCanary ·

    xAI retired 8 Grok models on May 15 — the slugs still resolve, so your bill and output quality changed silently

    <p>On <strong>May 15, 2026 at 12:00 PM PT</strong>, xAI retired eight model slugs from the Grok API:</p> <ul> <li><code>grok-4-1-fast-reasoning</code></li> <li><code>grok-4-1-fast-non-reasoning</code></li> <li><code>grok-4-fast-reasoning</code></li> <li><code>grok-4-fast-non-reas…

  2. dev.to — LLM tag TIER_1 Français(FR) · Model Radar ·

    Your LLM provider will deprecate your model. xAI just gave 9 days' notice.

    <p>If your app has a hard-coded model ID, you are one provider email away from a production incident. Here is what just happened, and why it keeps happening.</p> <h2> xAI: 8 models, ~9 days </h2> <p>Around May 6, 2026, xAI emailed API customers announcing Grok 4.3 and the retirem…