AI news · 2 min read

Haiku 5.5 makes small AI jobs cheaper, with a migration catch

Anthropic’s October 7 Haiku 5.5 launch cuts API rates for short prompts. Recount tokens and check request settings before switching a creator workflow.

Announcement date:

Affiliate disclosure: Some links may earn CreatorStack a commission at no extra cost to you.

At a glance

Haiku 5.5 launched October 7 with lower API rates for frequent, bounded tasks. Short-prompt input costs $0.10 and output $0.50 per million tokens; longer prompts use a higher band. Recount tokens and migrate request settings before switching.

An illustrated code review with branching changes and a checklist
CreatorStack illustration. Editorial illustration of this story’s topic, rather than a product screenshot or tested result.

A creator’s automation often needs a small job done hundreds of times: sort a research note, condense a description or extract a field. Anthropic’s October 7, 2026 Haiku 5.5 launch targets that kind of bounded work. It also reduces Sonnet 5.5 cache-read pricing. Launch and availability.

The interesting decision is which step deserves the smaller model. Keep an editor or a more capable setup responsible for the final argument; consider a cheaper model for repetitive preparation with a clear acceptance check. That is our suggested workflow, not a performance result.

Price the prompt you actually send

Anthropic lists these API rates in USD per million tokens, before separate cache charges. Current pricing documentation.

Prompt lengthInputOutput
Up to 100,000 tokens$0.10$0.50
Over 100,000 tokens$0.50$2.50

Sonnet 5.5 cache reads fall from $0.20 to $0.10 per million tokens. That saving depends on cache use; it does not halve every Sonnet bill. The launch names AWS, Google Cloud and Azure availability alongside the Claude Platform model claude-haiku-5-5. Check your provider’s billing and access separately from a Claude app subscription. Pricing table and related change.

The migration needs more than a new name

Old token counts can mislead a budget. The migration guide says the newer tokenizer produces approximately 30% more input tokens for the same text, with the increase depending on content. Recount representative prompts using the new model. A previous output limit may also truncate a response. Token-count changes.

Thinking configuration changes too. Haiku 5.5 uses adaptive thinking by default; an old enabled setting with budget_tokens returns a 400 error. The guide also calls for removing temperature, top_p and top_k, and reading response blocks by type rather than assuming the first block is the answer. These are selected checks, not the entire migration. Request and response checklist.

Next action: choose ten familiar inputs and define what a usable result must preserve before changing a production default. For a research summary, check names, dates and source links, then compare the total cost including retries and corrections. Our AI-output evaluation guide helps set that standard; the Claude Code workflow guide covers repeatable checks for coding work.

Common questions

Questions people ask.

Is the lowest rate available for every request?
No. The launch lists one band for prompts up to 100,000 tokens and higher input/output rates above that threshold. Cache charges are separate.
Can I change only the model name in an old integration?
Check the migration guide first. Haiku 5.5 changes token counts and thinking settings, and removes several sampling parameters. A model-name replacement is not a complete migration.

Sources & freshness

This article was refreshed on 8 Oct 2026 using the sources below. A source check verifies published information, not output quality or checkout availability in every region.

What changed: New Haiku 5.5 launch coverage with prompt-length pricing, tokenizer and adaptive-thinking migration checks; includes the related Sonnet cache-price change.

Found a correction? Let us know.

Need help applying this? Explore a workflow audit or get future guides by email.