How AI vendors are
actually pricing.

The SPP read

A six-to-one output premium tells you where OpenAI expects the cost, and the margin, to sit: generation, not context. For application vendors pricing on top of the API, the asymmetry matters more than the headline rate, because features that read long and write short carry a different unit cost than features that write long. Blended per-request pricing built on an average mix breaks the day the mix shifts. Price the direction your workload actually spends.

The SPP read

One announcement, three named rungs: a small tier at a fraction of the mid, a mid at half the top, and the top holding the flagship rate. Model families used to ship as one price with a mini beside it; this ships as a designed ladder, and the design is the point. Named rungs give the meter a packaging layer: buyers self-sort by workload instead of negotiating, and the vendor gains rungs it can move independently later. The ledger shows that option getting exercised within weeks, when the bottom rung was cut by four fifths and the middle trimmed while the top held. A ladder is the set of places a future price change can land without touching the others, and this vendor built one on purpose.

The SPP read

An 80% cut on the reasoning model, announced the same day a pro variant arrived at ten times the new rate, is one decision wearing two prices. The cut moves the base model toward commodity territory and the simultaneous premium launch preserves somewhere for the spend to go. Vendors under capability deflation keep doing this: the price of last year's frontier falls fast, and a new rung appears above it so the falling floor never takes the ceiling down with it. Watch the gap between rungs rather than either price alone; the gap is the actual product strategy.

The SPP read

Two extensions in six days teach heavy users to treat every cutoff as provisional, and the rational response is to front-run each deadline: burn included allocation now, put off converting to credits. A migration from bundled access to a metered surrogate unit survives on the credibility of its dates. Set one window you can keep rather than defending a short one twice.

The SPP read

A five-day extension announced at the deadline says the migration was not ready, commercially or operationally. Each short reprieve protects goodwill that week and spends credibility the next, because buyers start pricing in the chance that the meter never arrives. A transition window works when it is set once, up front, with an end date the vendor treats as fixed.

The SPP read

An introductory rate with a published end date is a promise about a future price, and this one landed in the same season the vendor was extending a different dated promise rather than keeping it. The workhorse model gets a discount with a calendar attached while the flagship's own deadline keeps moving. Buyers read both signals together. A promotional price only teaches the market what the real price is if the reversion actually happens, and every extension elsewhere makes the reversion look negotiable. The mechanism here is ordinary. The credibility cost of running it in this particular window is not.

The SPP read

The return converts a goodwill problem into a metering transition: included access ends July 7, then Fable moves to usage credits priced near API rates. Credits are a surrogate unit, a vendor-controlled currency between the subscriber and the metered resource, and they let Anthropic reprice later without touching the visible list price. Under the relaunch label, this is the pricing model change of the arc.

The SPP read

Clearance restored the product, not the offer. Subscribers came back to a capped allocation and a dated meter in place of the unmetered window promised at launch. When an interruption forces a relaunch, the relaunch terms are a repricing decision, and the market reads them as one.

The SPP read

No pricing architecture plans for a regulator switching the product off three days into a launch window. The suspension turned a simple included-access promise into a public obligation, and every later move in this arc is Anthropic repricing that obligation. For your own launches, the design question is how much promotional promise remains outstanding if access is ever interrupted.

The SPP read

The API rate is the meter the credits translate to: ten dollars in, fifty out, the top of Anthropic's list and roughly twice the workhorse model's rate. Pricing the same tokens two ways, bundled and metered, makes the gap between those two prices the real product decision of this arc.

The SPP read

Launching the flagship inside existing subscriptions with an included no-extra-cost window is a sampling play: let the installed base build the habit before the meter arrives. The exposure is anchoring. Whatever buyers experience as included becomes the reference point they judge every later meter against.

The SPP read

A weekly limit with paid overage at published API rates bounds the vendor's exposure. It does not bound the buyer's. Anthropic ran that shape a year before the sequence that made it famous, and the asymmetry runs one direction: the ceiling is denominated in tokens, a unit no buyer can forecast from the work they actually intend to do, so the limit lands at a moment they cannot anticipate and the spend above it accrues at a rate they cannot plan. Pricing the overage at list rather than a marked-up surrogate does treat the heavy user squarely. What it cannot fix is a meter counting something the buyer has no way to see coming, which is a metric problem rather than a budgeting one. The same mechanism returns in mid 2026 behind a model at roughly twice the workhorse rate, with inclusion capped at half the weekly limit and everything above it metered.

The SPP read

Salesforce is describing outcomes in the general sense, but bills for action related items that aren’t necessarily tied to client outcomes. Many vendors are jumping on the marketing bandwagon and charging for “outcomes” more a resolved call and an updated customer record are two very different types of outcomes. One is a step in a workflow, the other is a business outcome.

The SPP read

Three purchase models for one product, available simultaneously with no forced migration: a consumption pool, per-profile SKUs, and the shared Flex Credit pool. Choice-of-meter is what ships when no single metric has won the argument internally.

The SPP read

The first modality-differentiated action rate to take effect: the same agent action costs fifty percent more when it is spoken. Cost-based rate differentiation inside a value-denominated currency tells you which way the meter is actually indexed.

The SPP read

The flat-fee unlimited agreement is the escape hatch from their own consumption model: when per-conversation and per-action pricing stalls enterprise commitment, a ceiling-priced multi-year restores it. The shared-risk framing concedes the metering objection rather than answering it.

The SPP read

For the installed base the renewal-transition date is the real effective date. AI moved from a paid add-on into the higher editions, the standalone add-on was retired from sale, and the edition price rose twenty percent: a feature-level meter absorbed back into the edition, and the edition repriced for it.

The SPP read

A list action carrying an AI story: six percent on the premium editions with AI named as the justification, plus an unmetered $125 per-user agent add-on landing alongside the consumption meter being sold elsewhere in the catalog. Unmetered per-user agents next to per-action credits is a pricing surface admitting the metric question is not settled.

The SPP read

Budgets and usage caps attach to the cost center giving more finely grained controls on variability. Rather than change the pricing architecture, GitHub is gearing more tools for customers to manage their own spend. Expect this trend to continue until a breakout vendor’s alternative model is to absorb the risk, ditch the tools (and the requirement for customers to have staff managing these tools) and make it easier for customers to handle variability.

The SPP read

The effective date is where the architecture sharpened: multipliers rose the same day billing went live, and code review began drawing on two meters at once, Actions minutes and AI Credits. Notice what is absent: a legacy conversion. The pattern that holds across our engagements runs new-logo pricing first, with the installed base following on a modeled schedule. GitHub instead repriced the installed base in place on a date, cushioned by promotional and flex credits that expire on a calendar. A flash-cut of the base is the most damaging path a repricing can take, and doubly so in a competitive market where the smallest customers carry the lowest switching costs. The cushions soften the first invoice, not the decision to leave.

The SPP read

The announcement did the heavy lifting a quarter early: plan prices held still while the unit underneath them changed from requests to AI Credits, and promotional credit cushions bought the installed base a quiet first quarter. Swapping the meter while the visible price stands still is the least-resistance path through a repricing, and the cushion is its anesthetic. The bill arrives when the promo expires, not when the announcement ships.

The SPP read

The budget lane closed the way few price increases are ever announced: as a migration. Eight models retired, and the retired endpoints redirect to a model priced several times higher, so a budget buyer's bill rose without any price on any page changing. Redirect-repricing is the meter's quietest lever, and it only works because API buyers bind to model names rather than to rates. Watch for it wherever a vendor prunes a model list: the retirement notice is also the price sheet.

The SPP read

Beside the token meter, a second meter appeared denominated in something new: successful tool invocations, billed per thousand calls that worked. Charging only on success moves a unit of risk from buyer to vendor, and it is the first step on this arc that prices what the model accomplished rather than what it consumed. Small in revenue terms, large in signal: a vendor experimenting with success-denominated metering has conceded that tokens measure effort, not value.

The SPP read

A budget lane opened an order of magnitude below the flagship, and the vendor's own framing priced intelligence rather than tokens: near-flagship benchmark performance at a small fraction of the rate. Two prices for the same tokens depending on context length made the meter itself tiered. And when the same benchmark performance sells at token rates an order of magnitude apart, the token has stopped being a consistent unit of the thing the buyer is buying. The vendor's framing prices intelligence while its meter still prices tokens, and the distance between those two is where this arc's later moves happen.

The SPP read

A late API entrant priced its flagship at the going flagship rate, three dollars in and fifteen out, matching the incumbent workhorse to the dollar. Entering at parity rather than under it says the vendor is selling capability membership, not a discount, and it marks the moment this arc joins the metered market it will spend the next year renegotiating.

The SPP read

Hours after the flagship model shipped, the subscription tier carrying it went from $22 to $40 a month. Pricing the carrier rather than the model kept the model's own price page clean while nearly doubling what access costs, and the same launch window brought a standalone Grok subscription, reported at the time rather than posted, which marks the start of Grok's commercial life outside the platform. When a model's access price lives in another product's tier, every model launch is a repricing option on that tier, and this vendor exercised it within hours.

The SPP read

The arc opens with a flip that looks like generosity and functions as instrumentation: a paid-only assistant went free for every user on the platform, with a bounded allowance metering how much free anyone gets and the paid tiers keeping the higher limits. A free tier with an explicit bound is pricing already at work. The bound converts free users into a measured population, and the allowance boundary becomes the upsell line that every later move on this arc renegotiates.

The SPP read

Handing the buyer the definition of qualified is the opposite of the resolution meter, and it is the more durable choice. A metric the customer defines is a metric the customer cannot dispute at renewal.

The SPP read

A metric migration inside the same product. Resolution was legible to a buyer, outcome is broader and vaguer, so watch who holds the definition. The party that defines the outcome is the party that controls the invoice.

The SPP read

The first credible outcome meter in software: a price that fires only when the work succeeds, with a documented zero-charge path when it does not. The free-when-it-fails half is what made it defensible, and it is the half most imitators leave out.

The SPP read

The enforcement date is its own move: the free window closed on schedule and the meter became mandatory, with one carve-out keeping early Prospecting activators free into 2026. That is staged conversion of an installed base, cohort by cohort, the same discipline GitHub skipped.

The SPP read

Once the currency exists, everything meterable migrates into it: five features began drawing on the same credit pool in a single announcement, each at its own exchange rate. Per-feature rates inside one shared unit is how a vendor tunes price without touching list, and the grandfather window is the rollout instrument, the meter arriving before the bill.

The SPP read

For the first time the included-credit allotment itself became the packaging differentiator: same hub list price, double the included credits at the platform tier. When the meter is the product, allotments start doing the work editions used to do.

The SPP read

The counter-move in the same keynote: the assistant and enrichment moved into the seat while agent work moved onto the meter. The boundary being drawn, assistance included and agent work metered, is the architecture decision here; the rates are secondary.

The SPP read

The mechanism is a currency migration of the installed base: new customers priced in credits from day one, the installed base following sixty days later with included allotments sized to the edition. The allotment is the cushion that lets a metering change land as packaging rather than a price increase.

The SPP read

A power-user rung above the team tier, which usually exists to stop the heaviest users from breaking the meter beneath it. The question is whether the rung holds its position or drifts into being the default.

The SPP read

The retreat from credits to quotas is the market's most repeated correction: a synthetic currency buyers could not translate, replaced by an allotment they can. Note that the seat did not disappear. It came back carrying a quota.