{"version":"2.1.268","anchor":"gateway-can-push-admin-configured-modelpricing-overrides-dow","canonical_anchor":"gateway-can-push-admin-configured-modelpricing-overrides-dow","heading":"Admin pricing overrides can now apply to managed policies","tier":"use","area":"Gateway","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268\/e\/gateway-can-push-admin-configured-modelpricing-overrides-dow","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268","markdown":"### Admin pricing overrides can now apply to managed policies\n\nAdmin-configured price overrides can now be validated for and pushed down to managed-policy clients\n\n**What**\n\n- The gateway config validator, which previously required an `admin:` block for pricing settings to take effect, now also accepts a `managed:` block containing at least one policy, since both the admin spend meter and the `modelPricing` sent to clients read the same pricing config.\n\n- The gateway can now compute a per-deployment `modelPricing` object (a price multiplier plus per-model overrides) from an `admin.pricing`-style config, and merges it into each managed policy's `cli` settings, but only for policies that don't already specify their own `modelPricing`. It logs how many policies received the pushed pricing.\n\n- The dead-code checker that warns about pricing overrides that can never take effect was updated for the case where there's no admin\/meter block: in that case, an override is only considered reachable if it sits on the first upstream that would actually serve that model.\n\n**Why** This lets pricing overrides configured under `admin.pricing` reach managed-policy clients automatically, and improves the accuracy of warnings about pricing overrides that would silently never apply.\n\n- Area: Gateway\n- Names: `modelPricing`\n- Tier: Use it now\n- Useful: 3\/5\n- Signal: 2\/5"}