Blog

Your AI feature has a gross margin. Who sets it?

Anoop Jawahar · 30 October 2026 · 7 minute read

The AI line in a vertical SaaS gross margin is a supplier's price list multiplied by your own usage, and in October 2026 one model's output price more than tripled in a night. You set that margin yourself only for the steps of each agent run you can price, running on models whose weights you hold.

What happened to model prices in October?

On 20 October 2026, Stork AI Daily's price monitoring caught Alibaba raising its list price for DeepSeek V4 Flash overnight, with no announcement. Input went from $0.20 to $0.44 per million tokens. Output went from $0.40 to $1.32, which is 3.3 times what it had been the day before.

The same month moved the other way at OpenAI. GPT-5.6 Terra launched in July at $2.50 per million input tokens and $15 per million output tokens; by 27 October apidog listed it at $2 and $12, and the newer GPT-6.1 Terra had arrived at $1 and $5.

  • 3.3x

    DeepSeek V4 Flash output price on Alibaba's price list, $0.40 to $1.32 per million tokens, changed overnight with no announcement, reported 20 October.

    Source: Stork AI Daily, 20 Oct 2026
  • $15 to $12

    GPT-5.6 Terra output price per million tokens, July launch to October. GPT-6.1 Terra launched at $5.

    Source: apidog, 27 Oct 2026

For a CFO the direction matters less than the variance. A company running an agent feature on any of these models had its gross margin move in October, and nobody in its finance team changed a number to make that happen.

How much of what you pay is the supplier's margin?

The Anthropic S-1, made public on 26 October 2026, lets anyone work this out. Tomasz Tunguz pulled the lines that matter. In the first half of 2026, revenue was $16,286 million and cost of revenue was $2,380 million, which gives a gross margin of about 85%. In fiscal 2025 the same lines were $4,585 million and $2,773 million, about 40%. Forrester's own calculation also lands at about 85% for the first half.

Both margins are derived from the filed revenue and cost of revenue. The filing does not disclose a gross margin, and the figures cover all of Anthropic's revenue, the API and everything else together.

Of each dollar Anthropic billed, what it cost to serve

Cost of revenue per $1 of revenue, US cents. Derived from S-1 figures as reported by Tomasz Tunguz.

  • FY2025Revenue $4,585M
    60.5¢
  • H1 2026Revenue $16,286M
    14.6¢
Derived: 1 minus cost of revenue over revenue, from the Anthropic S-1 (made public 26 Oct 2026) as reported by Tomasz Tunguz. Gross margin is not a disclosed figure. Forrester's own calculation also gives about 85% for H1 2026. Covers all Anthropic revenue. Scale 0 to 100 cents. Checked 30 October 2026.

An 85% gross margin is what a successful software supplier looks like. Read from your side of the invoice, it means that on these derived figures about 85 cents of each dollar Anthropic billed in the first half was margin rather than cost to serve. Every token in your agent run carries a share of that margin into your own cost of revenue, at a level the supplier sets. When its pricing changes, so does your gross margin.

What does one agent run cost you?

Suppliers bill per token, per month. You sell per seat, per customer or per contract. Between the two sits the unit that drives your cost: the run, meaning one agent completing one task for one customer. A run is several model calls and at least one tool call, plus the retries when a check fails. Its cost is the sum over its model calls of tokens in times the input price plus tokens out times the output price, times retries, plus the tool calls.

Forrester's first advice to buyers after the S-1, published on 27 October, was to budget on the cost of a finished task, expect that cost to fall, and retest it with each model release. It also told buyers to watch usage limits, which can change while the list price stays the same.

The figure below splits one run in a claims administration product into its steps. Four of the five call a model, and only the drafting step does the kind of reasoning that needs a frontier model. The other three read a document, sort it or check a draft. The policy lookup calls your own systems and uses no model tokens. When the check fails, the run goes back to drafting, and you pay for the most expensive step a second time.

One agent run, step by step, and who sets each step's price

One agent run in a claims administration product, in five stepsAn example run has five steps: read the claim (extraction), classify and route (classification), look up the policy (a tool call with no model tokens), decide and draft the reply (reasoning), and check the draft (classification), which can send the run back to drafting as a retry. The API supplier sets the price of the reasoning step; it also sets the price of the extraction and classification steps today, which you could set yourself; your own systems set the price of the lookup. Run cost is the sum over steps of tokens in times price in plus tokens out times price out, times retries, plus tool calls. Example run, for illustration An agent in a claims administration product handles one incoming claim One run: one agent, one task, one customer Step 1 Read the claim extraction Step 2 Classify and route classification Step 3 Look up the policy tool call, no tokens Step 4 Decide and draft the reply reasoning Step 5 Check the draft classification retry Price set by API supplier today could be you API supplier today could be you your systems API supplier API supplier today could be you needs a frontier model work a small model can do no model tokens Run cost = sum over steps of (tokens in × price in + tokens out × price out), times retries, plus tool calls One agent run in a claims administration product, in five stepsAn example run has five steps: read the claim (extraction), classify and route (classification), look up the policy (a tool call with no model tokens), decide and draft the reply (reasoning), and check the draft (classification), which can send the run back to drafting as a retry. The API supplier sets the price of the reasoning step; it also sets the price of the extraction and classification steps today, which you could set yourself; your own systems set the price of the lookup. Run cost is the sum over steps of tokens in times price in plus tokens out times price out, times retries, plus tool calls. Example run, for illustration An agent in a claims administration product handles one incoming claim One run: one agent, one task, one customer Step Price set by Step 1 · extraction Read the claim API supplier today could be you Step 2 · classification Classify and route API supplier today could be you Step 3 · tool call, no tokens Look up the policy your systems Step 4 · reasoning Decide and draft the reply API supplier Step 5 · classification Check the draft API supplier today could be you retry needs a frontier model work a small model can do no model tokens Run cost = sum over steps of (tokens in × price in + tokens out × price out), times retries, plus tool calls
Illustrative. Step names and kinds are an example; Forrester advises budgeting on the cost of a finished task (27 Oct 2026).

If you are the CFO

Ask for one number: the cost of a finished run of your most used AI feature, by model and by provider, per customer. It is the formula in the figure above, computed from your own traces rather than from the monthly invoice. Have it rerun at every model release and every price change, and track the supplier's usage limits beside its list prices.

What a run costs depends on your prompts, your traffic and your retry rate, so the number has to come from your own product.

Does every step need a frontier model?

Once a run is split into steps, extraction, routing and checking turn out to be work a small model can do. Cloudflare tested exactly this on a claims pipeline of its own, as Help Net Security reported on 20 October 2026. A cascade of small extraction and decision models cost $6,032 per million claims, against $11,740 for a pipeline that sent every step to a large language model, and each claim took 19.3 seconds instead of 61.7.

Those are Cloudflare's figures for its own Clairic models, from a vendor testing its own product, and no independent test has been reported. The shape is still worth testing on your own runs.

Cloudflare's own test: small models in the pipeline, half the cost and a third of the time

Cost per million claims, USD

  • All-LLM pipeline
    $11,740
  • CascadeSmall extraction and decision models
    $6,032

Time per claim, seconds

  • All-LLM pipeline
    61.7 s
  • CascadeSmall extraction and decision models
    19.3 s
Cloudflare's own claims-pipeline test of its Clairic models, as reported by Help Net Security, 20 Oct 2026. A vendor testing its own product; no independent test has been reported. Scales 0 to 12,000 USD and 0 to 80 seconds. Checked 30 October 2026.

Vercel's AI Gateway Production Index, published on 15 October 2026, shows a similar split in live traffic. In September 2026, open-weight models carried 71.5% of the tokens on its gateway and 23% of the spend, and DeepSeek models alone carried 58% of the tokens. Vercel estimates spend at list prices, counts only traffic through its own gateway, and defines open-weight more broadly than earlier reports did. Read it as a direction across many companies, and run the numbers for your own product before you rely on it.

Which steps can nobody else reprice?

A step served by an open-weight model on your own infrastructure has a cost you set: the compute you contract for, running weights you hold. If a supplier changes its price list overnight, that step costs what your compute contract says it costs.

Steps that stay on a frontier API keep their exposure, and after the exercise above you know how large it is, step by step. Some steps will stay there because the reasoning needs a frontier model and the price is worth paying. For the steps that read, sort and check, the question becomes which model to run and where to run it. Many vertical domains already have open-weight models trained for them, and we compared them in our survey of domain-trained open-weight models.

The steps you run on weights you hold are the only steps in the run that nobody else can reprice overnight.

The choice is made one step at a time, with the cost of the run in front of the CEO and the CFO together.

What should the CEO and CFO ask for this week?

  1. Price one run. The cost of one finished run of your most used AI feature, by model and by provider. Owner: the CFO.
  2. Split it into steps. That run broken into its steps, each marked as frontier reasoning or as extraction, routing or classification. Owner: the CEO, with the CPO.
  3. Move one step. One extraction or classification step moved to an open-weight model on your own infrastructure, with the cost of the run measured before and after. Owners: the CPO and the CFO.

SynOS runs inside your product and prices every run, per model and per provider, so the AI line in your gross margin has a number per feature and per customer. The runs it records stay on your own infrastructure in the shape a training set is built from, ready for the steps you decide to move to a model you own.

Can you say what one run of your most used AI feature costs today?

Anonymous. One vote per browser.

Questions

How do LLM price changes affect a SaaS company's gross margin?

Model tokens are part of a SaaS company's cost of revenue, so a supplier's price change moves its gross margin without anyone in finance changing a number. In October 2026, Stork AI Daily reported on 20 October that Alibaba raised the DeepSeek V4 Flash output price from $0.40 to $1.32 per million tokens overnight, and apidog listed OpenAI's GPT-5.6 Terra output price at $12 on 27 October, down from $15 at its July launch. Steps served by an open-weight model on your own infrastructure cost what your compute contract says.

How do you calculate the cost of one AI agent run?

Add up every model step in the run: tokens in times the input price, plus tokens out times the output price. Multiply the steps that repeat by the number of retries, then add the cost of any tool calls. Compute it from your own traces, per model and per provider, and rerun it at every model release and price change.

Why did DeepSeek V4 Flash prices change in October 2026?

Stork AI Daily reported on 20 October 2026 that Alibaba raised its list price for DeepSeek V4 Flash overnight, with no announcement: input from $0.20 to $0.44 per million tokens and output from $0.40 to $1.32. Stork found the change through its price monitoring and gave no reason for it.

What gross margin does Anthropic make on its API?

The S-1 does not state one. Derived from its revenue and cost of revenue, as reported by Tomasz Tunguz, Anthropic's gross margin was about 85% in the first half of 2026 and about 40% in fiscal 2025. Those figures cover all of Anthropic's revenue, so the API alone may differ.

Sources

Price every run before the next price change.

Bring your most used AI feature and we will show you how SynOS prices each of its runs, per model and per provider, inside your product.