{"version":"2.1.227","anchor":"gateway-config-accepts-per-upstream-pricing-overrides","canonical_anchor":"gateway-config-accepts-per-upstream-pricing-overrides","heading":"Gateway config accepts per-upstream pricing overrides","tier":"use","area":"Gateway","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227\/e\/gateway-config-accepts-per-upstream-pricing-overrides","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227","markdown":"### Gateway config accepts per-upstream pricing overrides\n\nGateway config takes a pricing block with a multiplier and per-model rate overrides.\n\n**What**\n\nGateway configuration gains a `pricing` block with a `multiplier` (greater than 0, at most 1) and an `overrides` array of `{upstream, model, input, output, cache_read, cache_write}`, applied by the spend meter.\n\n**Details**\n\n- Validation warns when `pricing` is set without an `admin:` block, since only the spend meter reads pricing and it only runs when admin is configured.\n- It also warns when an override names an unknown upstream, duplicates an earlier override, or can never apply to any model that could be requested.\n\n**Evidence**\n\n`only the spend meter reads pricing, and it only runs when admin is configured`\n\n- Area: Gateway\n- Names: `pricing`, `multiplier`, `overrides`\n- Tier: Use it now\n- Useful: 2\/5\n- Signal: 3\/5"}