{"version":"2.1.242","anchor":"new-modelpricing-managed-setting-bills-usage-at-contracted-r","canonical_anchor":"new-modelpricing-managed-setting-bills-usage-at-contracted-r","heading":"New modelPricing managed setting bills usage at contracted rates","tier":"use","area":"Managed Settings","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242\/e\/new-modelpricing-managed-setting-bills-usage-at-contracted-r","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242","markdown":"### New `modelPricing` managed setting bills usage at contracted rates\n\nOrganizations can bill your reported spend at contracted rates everywhere costs appear.\n\n**What**\n\nAn 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.\n\n**Details**\n\n- 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.\"\n- The pricing table is compiled once per session; duplicate model rows produce a warning.\n- Emits telemetry `settings_model_pricing` carrying `rows` and `multiplier`.\n- When the config came from an untrusted origin the telemetry records a reason of `untrusted_origin` or `unverified_remote_cache`; a compile failure records `compile_threw` and list pricing is used instead.\n- Neither the key nor its telemetry exists in v2.1.241. No remote flag is involved.\n\n**Evidence**\n\n`Price usage at your organization's contracted rates instead of list price. `\n\n- Area: Managed Settings\n- Names: `modelPricing`\n- Tier: Use it now\n- Useful: 3\/5\n- Signal: 4\/5"}