diff --git a/aigw/product/model-catalog/custom-models.mdx b/aigw/product/model-catalog/custom-models.mdx
index 93199d1e..a7889644 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 6e6598da..4400bf65 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 adf58e1d..933d19c8 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 7e0a95f1..de370989 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.