Organizations can bill your reported spend at contracted rates everywhere costs appear.
What's wrong with this entry?
An organization can replace list-price cost math everywhere Claude Code reports spend: /cost, the status line, the SDK's total_cost_usd, --max-budget-usd and the OpenTelemetry cost metrics. It takes per-model overrides giving input, output, cache-read and cache-write USD per million tokens, plus a global multiplier in the range (0, 1]. It is honored only from managed settings, and a compile failure falls back to list pricing.
- Per its own description: "Only honored from managed settings (server-managed, MDM / OS policy, or managed-settings.json); ignored in user, project, local and --settings sources."
- The pricing table is compiled once per session; duplicate model rows produce a warning.
- Emits telemetry
settings_model_pricingcarryingrowsandmultiplier. - When the config came from an untrusted origin the telemetry records a reason of
untrusted_originorunverified_remote_cache; a compile failure recordscompile_threwand list pricing is used instead. - Neither the key nor its telemetry exists in v2.1.241. No remote flag is involved.
Price usage at your organization's contracted rates instead of list price.
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.248
Pricing tables rewritten as plain objects
Both mention pricing