Product & Strategy

The Product Desk

The Signal

Claude Haiku 5.5 costs a tenth as much per token and more per test than Haiku 4.5.

The price sheet sells a per-token discount, and about 3.5x more reasoning steps eat it before the invoice arrives. The new tokenizer also counts the same text as 25–30% more tokens, and past 100K tokens the rate jumps 5x. Whether a migration saves money or raises it comes down to one measurement: which side of that cliff your production prompts actually sit on.

In Play

  1. The Cheap Tier Ties on Price, Not on Cost

    Anthropic priced Claude Haiku 5.5 at $0.10/$0.50 per million tokens, the same as OpenAI's GPT-6 Luna. Vals still found it costs more per test than Haiku 4.5 on every shared benchmark, per AINews. Three things drive that: about 3.5x more reasoning steps, a tokenizer that counts roughly 25–30% more tokens, and a 5x rate above 100K tokens. How long your prompts run decides whether a migration saves money.

  2. Routers Pick the Model, Clones Copy the UI

    Microsoft and SpaceX made the same move within 48 hours, The Information reports. Microsoft said Copilot will send some tasks to its local MAI-Code-1.1 model. SpaceX said Grok Bot will send requests to Claude Opus 5.5, Midjourney and Suno. Google's Gemini agent also picks a model for each job. ChatGPT's new Intelligent UI was reportedly reverse-engineered in under 24 hours. Neither the model nor the rendering layer protects your product now.

  3. Agents Arrive as Your Customers

    Meta and Sierra launched the Personal Agent Protocol, an open standard for how personal AI agents sign in to and deal with businesses. Shopify, Stripe, Walmart, Genesys, Instinct and Rocket backed it. Cloudflare says agents drove 48% of usage of its Wrangler command-line tool last week, and it now lets agents pay per request. Your funnel, pricing and API are serving a non-human customer that your dashboards probably don't separate out.

  4. AI Value Claims Face an Audit

    The FT reports OpenAI's annualized revenue was near $50B at end-September, not the widely reported $70B. The gap came from multiplying one month's revenue by 12. Separately, a survey by The Information found a third of tech-forward subscribers say AI returns are a multiple of spend. Another 47% are unconvinced, and Copilot usage is falling even as seat counts rise. Expect renewals to turn on value your product can prove from inside its own usage data.

Deep Dives

Haiku 5.5's Rate Card Hides Three Multipliers, and Your Prompt Lengths Decide the Bill

The cheapest model tier now ties on list price. Whether you save depends on reasoning effort, tokenizer inflation and how many prompts cross one cliff.

Three multipliers sit between the list price and the bill

Anthropic discloses each of these in its own fine print. The finance partner usually sees them for the first time on the invoice.

  • Tokenizer inflation. Haiku 5.5 counts the same text as roughly 1.25x to 1.3x more tokens than Haiku 4.5. Net of that, Anthropic's own estimate of typical savings is about 75%, not 90%.
  • The 100K cliff. Above 100,000 tokens, rates rise to $0.50/$2.50. As the tier is described, the higher rate covers the whole prompt, so a 101K prompt costs about 5.1x a 99K prompt. Because of the tokenizer, the cutoff lands at roughly 80K old Haiku 4.5 tokens.
  • Reasoning that can't be switched off. Effort defaults to medium and can't be fully disabled. In Vals' testing, Haiku 5.5 took 59 reasoning steps on a legal research task. Haiku 4.5 took 17.

Anthropic says about 90% of Haiku 4.5 requests fit under 100K tokens. That is a count of requests, not dollars, and the pitch version of the number blurs the two. Take an illustration in which 90 of every 100 requests average 5K tokens and 10 average 200K. The long ones carry about 82% of input tokens and about 96% of input spend at the higher rate.

The cheapest vendor depends on prompt length

Prompt profileHaiku 5.5GPT-6 LunaGemini 3.5 Flash-Lite
Under 100K tokens$0.10 / $0.50, plus tokenizer and reasoning overhead$0.10 / $0.50; tokenizer not disclosed$0.30 / $2.50, flat
Around 150K tokens$0.50 / $2.50Still base rate; premium starts only above 272K, at $0.20 / $0.75$0.30 / $2.50, flat
Batch jobsFurther 50% offNot reportedNot reported

MarkTechPost calculated that Luna is cheaper on list price for a 150K-token prompt. Two details complicate that. Roboflow found Haiku 5.5 cheaper than Luna at high effort on vision tasks. Sonnet 5.5's halved cache-read price of $0.10 per million also equals Haiku 5.5's uncached input price. For input-heavy agent loops with a stable prompt prefix, moving up a tier can cost far less than the 20x list gap implies. Output is still 20x more expensive, so the answer turns on each workload's input-to-output ratio.

Cheap models only lower cost inside a cascade

In a cascade, a cheap model answers first and hands its uncertain cases to an expensive one. Log10's clinical tests have the cleanest public numbers. A low-cost model answered every question and sent its least-confident 20% to Claude Opus. Accuracy rose from 80.0% to 87.9%. Escalating a random 20% reached only 83.0%. The cascade cost $5.46 per 1,000 questions. Opus alone cost $25.33 and scored 94.9%. Closing that last gap works out to about $0.28 per avoided error. In any flow where a mistake costs more than that, escalation is the better buy.

Log10 also tested the cheap model as a judge of other models' answers, and it did worse than simply labeling every answer correct. Haiku 5.5's vendor-reported jump on computer-use tasks, from 15.7% to 72.4%, makes it a usable sub-agent, but the judging result rules it out as a verifier.

Graded as a judge, the cheap model lost to a baseline that marks every answer correct.

The move

Decide feature by feature from real traffic, not with a company-wide switch. Sort each flow on two axes, prompt length and the cost of a wrong answer. Short prompts at high volume where errors are cheap, such as classification, triage and support drafts, are where Haiku 5.5 or Luna win. Long-context and high-stakes flows need cost per completed task measured before anything moves.

What to do

  1. Replay 1–2 weeks of production prompts this sprint through Haiku 4.5, Haiku 5.5 at low and medium effort, and GPT-6 Luna. Report cost per completed task, reasoning tokens, and the share of requests over 100K tokens for each feature.

  2. Set a context budget of about 90–95K Haiku tokens per feature, with alerts, and write retrieval and chunking requirements into the PRD before any traffic moves.

  3. Prototype a confidence cascade on your highest-volume, lowest-stakes flow this sprint. Escalate the least-confident 20% and compare it against three alternatives: the cheap model alone, a random 20% escalated, and the frontier model alone.

Routers Now Pick the Model and Clones Copy the UI. Here Is What You Still Own.

Two layers that looked defensible a month ago lost that status in one week. That leaves governance, callability and domain judgment as the ground you can hold.

Look at what each router hides from the user

RouterWho picks the modelNamed back endsGovernanceWhere results land
Grok Bot (SpaceX)Grok Bot; no model pickerClaude Opus 5.5, Midjourney, SunoTeam allowlist honored by default, but Grok Bot warns it may not follow itInside Grok Bot
Copilot (Microsoft)A router moves some tasks to the PCMAI-Code-1.1 on Nvidia-powered PCsWindows 11 agent file-access controls arrive later in OctoberWindows
Gemini agent (Google Cloud)The agent, per jobNot disclosed; TestingCatalog reports Claude Opus 5 and Sonnet 5.5 coming to Gemini Business (unconfirmed)Sold on cost controls, security and adminDocs, inboxes and developer tools

Two things stand out. First, frontier models are becoming ingredients inside rivals' products. Anthropic now supplies the reasoning back end for SpaceX's flagship agent. Musk's stated logic was "whatever is most likely to give you the best outcome," though he offered no tests showing that routing improves results. Second, the routers deliver finished work where employees already are. If an orchestrator can't call your product, it will route around it.

The labs are also moving into the application layer underneath you. A September survey by The Information found Claude Code now leads coding tools. OpenAI's Codex surged in 2026, Cursor is close behind, and the early Copilot/Cursor duopoly has vanished. So your product sits between routers above it, which choose the model, and labs below it, which can ship your feature natively.

The interface layer went generic just as fast

GPT-6's Intelligent UI decides per question whether to answer with an interactive diagram, a side-by-side comparison, a calculator or plain text. It assembles streamable components progressively while the model writes. The rollout went first to Plus, Pro, Business and Enterprise, with Free and Go users a day later, in the Chat tab only. Your users' expectations will reset within weeks. A comparison question should come back as a comparison.

The rendering itself is no moat, though. A write-up claims the system was reverse-engineered in under 24 hours from public artifacts. Open-source equivalents already exist: openui, open-intelligent-ui, Vercel json-render and a2ui. One early user found real-world use less impressive than the demos. Sources agree on the direction. They differ on whether to build or buy, and the clone evidence favors buying.

When anyone can render the widget and a router chooses the model, the defensible product is the judgment about what to show, the rules about what may run, and an interface agents can call.

What you still own

  • Enforceable governance. Grok Bot's admission that it may not honor allowlists is the objection regulated buyers will raise. A hard-enforced allowlist with the model ID logged on every request is a competitive answer you can ship.
  • Callability. Connectors, APIs and tool definitions let the Gemini agent deliver your output inside a customer's docs instead of replacing you.
  • Domain components. The render-or-text decision for your top query types, built from your design system, is the part a generic clone can't copy.

What to do

  1. Stand up a model gateway this sprint with provider-agnostic routing, the model ID on every request in logs and billing, hard-enforced allowlists, and per-tenant cost caps.

  2. Add 'hard-enforced model allowlist plus per-request model audit trail' to your security questionnaire answers and to battlecards against Grok Bot and the Gemini agent this week.

  3. Prototype generative UI for your top three query types on an open-source renderer (json-render, a2ui or openui) and A/B it against text answers this sprint.

The Next Customer in Your Checkout Is an Agent You Can't See Yet

Protocols, payment rails and usage data all point the same way, but no one has a loss baseline. Whoever defines safe agent purchasing first sets the category's terms.

The protocol coalition maps onto your funnel

Meta brings the consumer side of the Personal Agent Protocol. Sierra and Genesys bring customer service, Shopify and Walmart bring storefronts, and Stripe brings payments. That covers discovery, checkout and support in one announcement. The protocol explicitly includes company agents, which means the counterparty to your support or sales bot will increasingly be another bot.

Note what PAP standardizes first: authentication. Andrew Chen argues that identity, trust and reputation are where agent network effects come from. An open protocol co-authored by a consumer platform is still a strategic position. Also note who was missing from the reported launch coalition: Amazon, Google, OpenAI, Apple, Anthropic and Microsoft. Adoption beyond the launch partners decides whether this becomes a default or one standard among several.

Agents already show up in the logs

Cloudflare's 48% figure is its own measurement for a single week, and it hasn't disclosed how it defines agent usage. Its product response is the clearer signal. Its new cf CLI exposes more than 3,000 API operations with JSON output by default, plus command search in plain language. Its Issues product sends grouped failures straight to a coding agent instead of a dashboard. GitHub rebuilt Git for concurrent agent reads and writes and claims up to 35x higher write throughput, a self-reported figure. Agent traffic is a new load class. A seat-based price misreads it, because one customer's agents can generate far more activity than its people.

Agents now arrive with wallets

Stripe co-founder John Collison says agents replacing humans as buyers is forcing Stripe to redesign its APIs. Stripe lists four building blocks for agent commerce: Bridge for stablecoins, Privy for wallets, Metronome for usage billing and OpenRouter for model routing. Cloudflare now lets agents pay at request time instead of subscribing. A subscription-only price list leaves that demand unpriced.

The risk side is empty. The Agent Payment Risk Index 2026 found that none of its indexed sources establishes a confirmed production-loss total for agents paying the wrong party. Without a baseline, your risk team will default to saying no. That gap is also an opening: the first product that logs payee verification, spend caps and wrong-payee incidents gets to define what safe means.

Permissions are the missing piece

Charlie Guo notes that granular agent permissions, such as "read all email, send only to whitelisted recipients," don't exist yet. He favors giving agents their own accounts over letting them impersonate users for about 90% of tasks. OpenAI's new MCP Events let connected apps trigger agent work, so the events your product exposes become a distribution surface too.

If a machine can't find, price, buy and act inside your product, the agent will pick a product it can.

What to do

  1. Add an agent-vs-human dimension to your funnel, checkout and API dashboards this sprint, counting agent sessions that hit a subscription wall, login gate or abandoned checkout.

  2. Run an agent-as-customer walkthrough of signup, checkout, account changes and support against PAP within two sprints. End it with a recommendation: adopt, wait, or counter-position.

  3. Spec agent-payment guardrails this quarter: payee verification, per-transaction and per-period spend caps, allowlists, human approval above a threshold, and wrong-payee logging. Do this before you pilot a per-request pricing lane.

The bottom line

These developments pulled the model out of the center of the product. The budget tier priced itself into sameness, orchestrators took the choice away from users, and machines started showing up as the users. The assumption that breaks is that choosing the right model is a strategy. What you own now is how you measure each task, the rules for which system may do what, and the surfaces other software can call. Instrument cost per completed task and machine-versus-human traffic in one shared view this week, and let it decide your routing, your pricing and what you expose next.