From 49bd72122ea1a38d0a04630d7f21bacdd14f8059 Mon Sep 17 00:00:00 2001 From: "siva.durga" Date: Mon, 5 Oct 2026 10:14:35 +0530 Subject: [PATCH] docs: note that custom pricing overrides pricing adjustments MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Pricing Adjustments are skipped for any model that has its own custom pricing_config — the custom price is billed exactly as written. This is true for adjustments set at the model level and at the Integration level, but the docs read as if a multiplier always applies. Add a note to both the Portkey and AI Gateway pricing-adjustments pages, and cross-link it from the custom pricing field on the custom-models pages. Co-Authored-By: Claude Opus 5 (1M context) --- aigw/product/model-catalog/custom-models.mdx | 4 ++++ aigw/product/model-catalog/pricing-adjustments.mdx | 4 ++++ product/model-catalog/custom-models.mdx | 4 ++++ product/model-catalog/pricing-adjustments.mdx | 4 ++++ 4 files changed, 16 insertions(+) diff --git a/aigw/product/model-catalog/custom-models.mdx b/aigw/product/model-catalog/custom-models.mdx index 93199d1ec..a78896445 100644 --- a/aigw/product/model-catalog/custom-models.mdx +++ b/aigw/product/model-catalog/custom-models.mdx @@ -44,6 +44,10 @@ Here’s a breakdown of each field in the form: + +A model with custom pricing is billed at exactly that price — [pricing adjustments](/aigw/product/model-catalog/pricing-adjustments) set at the model level or the Integration level are ignored for it. Build any discount or markup into the custom price itself. + + ## Per-model custom host and headers Each integration model can carry its own routing config — useful when several custom models share one integration but hit different upstreams or need different headers. diff --git a/aigw/product/model-catalog/pricing-adjustments.mdx b/aigw/product/model-catalog/pricing-adjustments.mdx index 6e6598da2..4400bf650 100644 --- a/aigw/product/model-catalog/pricing-adjustments.mdx +++ b/aigw/product/model-catalog/pricing-adjustments.mdx @@ -112,6 +112,10 @@ Because the replacement is whole-object, an Integration-level 20% discount does Models without their own `pricing_adjustments` continue to use the Integration-level adjustment. + +If a model has its own custom pricing, that price is billed exactly as written — pricing adjustments set at the **model level or the Integration level are ignored** for that model. Other models in the same Integration are unaffected. To discount or mark up a custom-priced model, build the adjustment into the custom price itself. + + ## Setting Pricing Adjustments via the API You can also configure Pricing Adjustments programmatically through the [Integrations API](/aigw/api-reference/integrations/post-integrations). Pass `pricing_adjustments` when creating or updating an Integration. Send `null` to clear all adjustments. diff --git a/product/model-catalog/custom-models.mdx b/product/model-catalog/custom-models.mdx index adf58e1de..933d19c88 100644 --- a/product/model-catalog/custom-models.mdx +++ b/product/model-catalog/custom-models.mdx @@ -53,6 +53,10 @@ Here’s a breakdown of each field in the form: + +A model with custom pricing is billed at exactly that price — [pricing adjustments](/product/model-catalog/pricing-adjustments) set at the model level or the Integration level are ignored for it. Build any discount or markup into the custom price itself. + + ## Per-model custom host and headers Each integration model can carry its own routing config — useful when several custom models share one integration but hit different upstreams or need different headers. diff --git a/product/model-catalog/pricing-adjustments.mdx b/product/model-catalog/pricing-adjustments.mdx index 7e0a95f17..de370989c 100644 --- a/product/model-catalog/pricing-adjustments.mdx +++ b/product/model-catalog/pricing-adjustments.mdx @@ -118,6 +118,10 @@ Because the replacement is whole-object, an Integration-level 20% discount does Models without their own `pricing_adjustments` continue to use the Integration-level adjustment. + +If a model has its own custom pricing, that price is billed exactly as written — pricing adjustments set at the **model level or the Integration level are ignored** for that model. Other models in the same Integration are unaffected. To discount or mark up a custom-priced model, build the adjustment into the custom price itself. + + ## Setting Pricing Adjustments via the API You can also configure Pricing Adjustments programmatically through the [Integrations API](/api-reference/admin-api/control-plane/integrations/create-integration). Pass `pricing_adjustments` when creating or updating an Integration. Send `null` to clear all adjustments.