Skip to content

Cost and FinOpsChecklist

Opus 4.8 fast mode ends Nov 30: find every caller and re-price

Anthropic deprecated fast mode for Claude Opus 4.8 on October 30 and removes it on November 30, 2026. After that, any request to claude-opus-4-8 that sets speed "fast" returns an error. This checklist finds those callers, re-prices them at standard speed, and lists the options to test before the date.

By INFRO Editorial

Published

7 min read

Glowing token streams being compressed into a precise efficient AI infrastructure pipeline

In short

Fast mode on Claude Opus 4.8 is removed on November 30, 2026, and requests that still set speed "fast" will return an error rather than run slower 1. Find the callers now, drop or move the flag, and re-price: list rates halve, but output speed falls by up to 2.5x 2.

Key takeaways

  • After November 30, 2026, a request to claude-opus-4-8 with speed "fast" returns an error; it does not quietly run at standard speed.
  • Standard Opus 4.8 lists at half the fast-mode rate, but fast mode's up-to-2.5x output speed goes with it, so total latency SLOs can break even as the bill falls.
  • Fast mode speeds up output tokens per second, not time to first token, so a TTFT objective should be unaffected and a total-duration objective is the one at risk.
  • Moving to Opus 5.5 keeps fast mode but brings always-on adaptive thinking and rejected request settings, so it is a migration, not a model-id swap.
  • Switching speed misses the prompt cache, so expect cache writes on the first requests after cutover.

What changes on November 30

On October 30, 2026 Anthropic deprecated fast mode for Claude Opus 4.8, with removal on November 30. After removal, requests to claude-opus-4-8 with speed: "fast" return an error, and Anthropic points callers who want to keep fast mode to Claude Opus 5.5.1 That is 22 days from today, November 8.

Two details shape the work. First, it is a hard failure, not a silent downgrade: a caller you miss turns into an error rate. The fast mode page does describe a fallback pattern, but it catches rate-limit errors (429) and retries without speed; a removed feature is a different error, and the release note says only "an error".2 Second, the model is not going anywhere. Anthropic lists claude-opus-4-8 as active, with retirement not sooner than May 28, 2027.3 Only the flag is removed, so the cheapest fix is often to stop sending it.

Fast mode on Opus 4.8 was a research-preview feature, and Anthropic's notes say to keep sending the beta header with fast requests to that model.1 So there are two strings to search for: the speed field and the fast-mode-2026-02-01 header.

Step 1: find every caller

Do the code search and the traffic search, because each misses things the other catches. Code search misses feature flags, config files and third-party agents; traffic search misses callers that only run monthly.

  • Grep every repository, infrastructure config and notebook for speed, "fast" and fast-mode-2026-02-01.
  • Search for the model id claude-opus-4-8 in environment variables, prompt-management tools and route definitions, not only in code.
  • For Claude Managed Agents, check agent definitions: speed is set on the agent's model object, for example {"id": "claude-opus-5-5", "speed": "fast"}.2
  • Log usage.speed from every Opus 4.8 response for a week. The response reports "fast" or "standard", which tells you which calls really ran fast.2
  • Watch the fast-mode rate-limit response headers (anthropic-fast-output-tokens-limit and related) in your logs; their presence marks a fast request.2
  • Pull a usage export grouped by API key and model from the Claude Console, which Anthropic documents for auditing deprecated usage, and match keys to owners.3
  • If you call Claude through a gateway, group Opus 4.8 requests by key, project and feature, so every owner of an Opus 4.8 key is asked.
  • Ask the owners of scheduled jobs and evaluation harnesses, which rarely appear in a one-week window.

A single shim makes the cutover safe while the owners fix their code. It strips the flag for this model after a switch date and logs what it removed:

fast_shim.py
import logging
from datetime import datetime, timezone

CUTOFF = datetime(2026, 11, 30, tzinfo=timezone.utc)
log = logging.getLogger("fast-shim")

def create(client, **params):
    if params.get("model") == "claude-opus-4-8" and params.get("speed") == "fast":
        if datetime.now(timezone.utc) >= CUTOFF:
            params.pop("speed")
            # drop the research-preview beta header too if you send it
            log.warning("removed speed=fast for opus-4-8 caller=%s", params.get("metadata"))
    return client.messages.create(**params)

Step 2: decide per caller

Not every fast caller needs the same answer. Sort each one by what its latency target is made of.

CallerWhat it needsFirst option to test
Interactive chat, streamedFast token streamOpus 5.5 with speed: "fast"
Agent loop, many turnsShort total run timeOpus 5.5 standard or fast; fewer turns
Background job nobody waits onThroughput, not speedDrop the flag, stay on Opus 4.8
Short answers, tight SLOLow total timeSonnet 5.5 or Haiku 5.5
Batchn/aFast mode is not available in the Batch API2

The background-job row is the most common saving: a caller that set fast mode by habit and has no user waiting pays double for nothing.

Step 3: re-price

Fast mode is a multiplier on standard rates across the full context window.2 On Opus 4.8 and Opus 5 it lists at $10 input and $50 output per million tokens; on Opus 5.5 at $8 and $40.2 Standard Opus 4.8 lists at $5 and $25, and standard Opus 5.5 at $4 and $20, with cache reads at $0.50 and $0.20.4 Anthropic's pricing page states the Opus 5.5 fast mode as 2x standard pricing.5 Sonnet 5.5 lists at $2 and $10, and Haiku 5.5 at $0.10 and $0.50 for prompts up to 100,000 tokens.4 These are list rates; if your contract carries different rates, apply them to the same arithmetic.

The last line matters. On Opus 5.5 every request runs with adaptive thinking, thinking tokens bill as output tokens, and workloads that ran without a thinking field on Opus 4.8 can produce more output tokens per request.6 Re-baseline cost at your chosen effort level, not just from the rate card.

Also plan for cache: requests at different speeds do not share cached prefixes, so moving off fast mode causes a cache miss.2 Expect the first requests after cutover to pay cache writes, which are 1.25x the base input price for the five-minute duration.4

Step 4: what happens to latency objectives

Fast mode delivers up to 2.5x higher output tokens per second, and Anthropic says the benefit is in output speed, not time to first token.2 That splits your objectives in two:

  • Time to first token: should not move when you drop the flag, since fast mode was not what made it quick.
  • Total response time and tokens per second: can lengthen by up to 2.5x for the generation phase, the biggest effect on long, streamed answers.

Rate limits change too. Fast mode has a dedicated rate limit separate from standard Opus limits, and exceeding it returns a 429.2 Callers moved to standard speed fall under the standard Opus limits instead, so check headroom for the combined volume. If any caller is on a Priority Tier commitment, note that fast mode is unavailable with one, and Priority Tier is not supported on Opus 5.5.26

Step 5: options to test

Run each option on a replay of your own traffic and score cost per successful task, not rate-card price; the benchmark claims below are Anthropic's, not yours.

  • Opus 4.8 at standard speed. Same model, half the list rate, slower output. Test the total-time objective only.
  • Opus 5.5, standard and fast. Keeps fast mode and lists lower, but the migration guide requires changes: no thinking: disabled, effort set explicitly (default medium), no forced tool_choice of any or a named tool, no sampling parameters, and no prefilled assistant turn.6 Read content blocks by type, because responses can start with thinking blocks.
  • Sonnet 5.5. Anthropic says it runs 30%+ faster than Sonnet 5 and costs up to 30% less for most work; that comparison is against Sonnet 5, not Opus.7 Test it on tasks where Opus-level depth was never the constraint.
  • Haiku 5.5. Described by Anthropic as its fastest small model, built for high-volume work such as summarization and subagents.7 The right test for short, latency-bound calls.
  • Another vendor's fast tier. Compare against service tiers across vendors and the ultrafast agent-loop analysis, and check equivalence with the method in your fallback tests.

A dated plan to November 30

  1. Nov 8–14: run the code search, turn on usage.speed logging, and list every Opus 4.8 key and its owner.
  2. Nov 15–19: classify each caller with the table above and set a latency and cost target for each.
  3. Nov 20–25: replay traffic on the chosen options in staging; ship the shim as a safety net.
  4. Nov 26–29: cut over callers by owner, starting with background jobs, and watch error rate and p95 per caller.
  5. Dec 1: confirm no request carries speed: "fast" for claude-opus-4-8, and re-forecast December from the new mix.

Where a gateway helps

If your Claude traffic goes through a gateway, usage per request already records model, latency and estimated provider cost, and can be grouped by key, project, feature or tag, which narrows the owner list in Step 1 and gives you p50/p95 per caller to compare before and after.8 Routing rules in INFRO can send a matching feature or key to a different target, which lets you move one caller to Opus 5.5 or Sonnet 5.5 without a deploy. Enter your contract rates under negotiated rates so the re-price uses what your provider bills. Confirm in staging whether your path forwards the speed field before relying on it.

Questions readers ask

Does fast mode change the answers I get from Opus 4.8?
Anthropic describes fast mode as the same model on a faster inference configuration, with no change to intelligence or capabilities 2. Dropping the flag should therefore change speed and price, not answer quality, though thinking and token counts are what to compare if you also change models.
Can I use fast mode in the Batch API instead?
No. Anthropic's fast mode page lists the Batch API as unsupported, and fast mode is also unavailable with a Priority Tier commitment 2.

From the team that builds it

Where this shows up in INFRO

INFRO is a control plane in front of the provider accounts you already hold. The capabilities below are the parts of it this article touches, each with the documentation that defines its behaviour.

  • Usage and cost per request

    Available with a plan

    Every request records its model, latency, token or unit counts, and estimated provider cost, queryable by project and key.

    Read the documentation for Usage and cost per request
  • Spend attribution

    Available with a plan

    Group cost by model, project, key, or an end-user id you attach to the request.

    Read the documentation for Spend attribution
  • Routing rules

    Available with a plan

    If-rules on a route send matching requests to their own targets, by metadata, feature, end user, key, project, prompt size, streaming, images, tools or time of day. Failure rules decide per failure kind whether to retry, move on or stop.

    Read the documentation for Routing rules
  • Usage, request and FOCUS exports

    Available with a plan

    GET /v1/usage and GET /v1/requests on any gateway key, the request log and usage series as CSV, plus a FOCUS v1.4 Cost and Usage dataset as JSON or CSV, so AI spend lands in your FinOps platform beside the rest of your cloud cost.

    Read the documentation for Usage, request and FOCUS exports
  • Negotiated provider rates

    Available with a plan

    Enter the rates your contracts actually carry, per model and optionally per provider, so estimated cost uses them before the vendor's list rate. Included on every plan.

    Read the documentation for Negotiated provider rates

INFRO accounts are self-serve. Provider usage is billed to you by your providers; INFRO charges a software subscription and takes 0% of model spend. See plans.

Sources

Numbered in order of first citation. Each was opened and checked against the claim on the date shown.

  1. 1.Claude Platform release notes (opens in a new tab) — Anthropic. Accessed Nov 8, 2026.
  2. 2.Fast mode (opens in a new tab) — Anthropic. Accessed Nov 8, 2026.
  3. 3.Model deprecations (opens in a new tab) — Anthropic. Accessed Nov 8, 2026.
  4. 4.Pricing (opens in a new tab) — Anthropic. Accessed Nov 8, 2026.
  5. 5.Plans & pricing (opens in a new tab) — Anthropic. Accessed Nov 8, 2026.
  6. 6.Claude Opus 5.5 migration guide (opens in a new tab) — Anthropic. Accessed Nov 8, 2026.
  7. 7.Newsroom (opens in a new tab) — Anthropic. Accessed Nov 8, 2026.
  8. 8.Usage analytics (opens in a new tab) — INFRO. Accessed Nov 8, 2026.

About this article

Read on 8 November 2026: Anthropic's API release notes, fast mode page, pricing and deprecations pages, the Opus 5.5 migration guide, the Anthropic newsroom, claude.com/pricing and INFRO's usage analytics docs. Left out: the HTTP status code of the post-removal error, whether the removal applies identically on each cloud platform, and any quality comparison of replacement models, because none of those pages state them.

Last checked against its sources on . The next review is due by . No separate named reviewer is recorded for this article.

How articles are written, sourced and corrected is set out in the editorial standards.