From b4f8d206b89f52c33b392bc0618753fc920de44b Mon Sep 17 00:00:00 2001
From: pgrzesik <17499590+pgrzesik@users.noreply.github.com>
Date: Tue, 13 Oct 2026 17:05:29 +0000
Subject: [PATCH] chore: update OpenAPI specs from 0x-labs

---
 fern/openapi-cross-chain.json | 32 ++++++++++++++++++++++++++------
 1 file changed, 26 insertions(+), 6 deletions(-)

diff --git a/fern/openapi-cross-chain.json b/fern/openapi-cross-chain.json
index 9adfb0db..3a50c400 100644
--- a/fern/openapi-cross-chain.json
+++ b/fern/openapi-cross-chain.json
@@ -163,7 +163,17 @@
                             "type": "string",
                             "default": ""
                         },
-                        "description": "The trading fee amounts in basis points to charge on the origin chain (supports single or comma-separated values). Must be used together with feeRecipient. When multiple values are provided, must match the length of feeRecipient. Note: integrator fee collection is not yet supported for Tron-originated routes."
+                        "description": "The trading fee amounts in basis points to charge on the origin chain (supports single or comma-separated values). Mutually exclusive with `feePpm`. Must be used together with feeRecipient. When multiple values are provided, must match the length of feeRecipient. Note: integrator fee collection is not yet supported for Tron-originated routes."
+                    },
+                    {
+                        "name": "feePpm",
+                        "in": "query",
+                        "required": false,
+                        "schema": {
+                            "type": "string",
+                            "default": ""
+                        },
+                        "description": "The trading fee amounts in parts-per-million (PPM) to charge on the origin chain (supports single or comma-separated values). Mutually exclusive with `feeBps`. Must be used together with feeRecipient. Each value must be an integer from 0 to 1000000. When multiple values are provided, must match the length of feeRecipient. e.g. 5000 PPM = 50 BPS = 0.5%. Note: integrator fee collection is not yet supported for Tron-originated routes."
                     },
                     {
                         "name": "feeRecipient",
@@ -173,7 +183,7 @@
                             "type": "string",
                             "default": ""
                         },
-                        "description": "The wallet addresses to receive trading fees on the origin chain (supports single or comma-separated values). Must be used together with feeBps. When multiple values are provided, must match the length of feeBps. Note: integrator fee collection is not yet supported for Tron-originated routes."
+                        "description": "The wallet addresses to receive trading fees on the origin chain (supports single or comma-separated values). Must be used together with feeBps or feePpm. When multiple values are provided, must match the length of feeBps or feePpm. Note: integrator fee collection is not yet supported for Tron-originated routes."
                     },
                     {
                         "name": "feeToken",
@@ -183,7 +193,7 @@
                             "type": "string",
                             "default": ""
                         },
-                        "description": "The token addresses for fee collection on the origin chain (supports single or comma-separated values). Must be the same as sellToken. When multiple values are provided, must match the length of feeBps. If omitted, defaults to sellToken. Some routes collect the integrator fee through the bridge provider instead of on-chain; the fee still goes to feeRecipient, but it comes out of the token entering the bridge, which is not sellToken when the route swaps before bridging. Read fees.integratorFee.token for the token actually charged. Note: integrator fee collection is not yet supported for Tron-originated routes."
+                        "description": "The token addresses for fee collection on the origin chain (supports single or comma-separated values). Must be the same as sellToken. When multiple values are provided, must match the length of feeBps or feePpm. If omitted, defaults to sellToken. Some routes collect the integrator fee through the bridge provider instead of on-chain; the fee still goes to feeRecipient, but it comes out of the token entering the bridge, which is not sellToken when the route swaps before bridging. Read fees.integratorFee.token for the token actually charged. Note: integrator fee collection is not yet supported for Tron-originated routes."
                     },
                     {
                         "name": "sortQuotesBy",
@@ -3036,7 +3046,17 @@
                             "type": "string",
                             "default": ""
                         },
-                        "description": "The trading fee amounts in basis points to charge on the origin chain (supports single or comma-separated values). Must be used together with feeRecipient. When multiple values are provided, must match the length of feeRecipient. Note: integrator fee collection is not yet supported for Tron-originated routes."
+                        "description": "The trading fee amounts in basis points to charge on the origin chain (supports single or comma-separated values). Mutually exclusive with `feePpm`. Must be used together with feeRecipient. When multiple values are provided, must match the length of feeRecipient. Note: integrator fee collection is not yet supported for Tron-originated routes."
+                    },
+                    {
+                        "name": "feePpm",
+                        "in": "query",
+                        "required": false,
+                        "schema": {
+                            "type": "string",
+                            "default": ""
+                        },
+                        "description": "The trading fee amounts in parts-per-million (PPM) to charge on the origin chain (supports single or comma-separated values). Mutually exclusive with `feeBps`. Must be used together with feeRecipient. Each value must be an integer from 0 to 1000000. When multiple values are provided, must match the length of feeRecipient. e.g. 5000 PPM = 50 BPS = 0.5%. Note: integrator fee collection is not yet supported for Tron-originated routes."
                     },
                     {
                         "name": "feeRecipient",
@@ -3046,7 +3066,7 @@
                             "type": "string",
                             "default": ""
                         },
-                        "description": "The wallet addresses to receive trading fees on the origin chain (supports single or comma-separated values). Must be used together with feeBps. When multiple values are provided, must match the length of feeBps. Note: integrator fee collection is not yet supported for Tron-originated routes."
+                        "description": "The wallet addresses to receive trading fees on the origin chain (supports single or comma-separated values). Must be used together with feeBps or feePpm. When multiple values are provided, must match the length of feeBps or feePpm. Note: integrator fee collection is not yet supported for Tron-originated routes."
                     },
                     {
                         "name": "feeToken",
@@ -3056,7 +3076,7 @@
                             "type": "string",
                             "default": ""
                         },
-                        "description": "The token addresses for fee collection on the origin chain (supports single or comma-separated values). Must be the same as sellToken. When multiple values are provided, must match the length of feeBps. If omitted, defaults to sellToken. Some routes collect the integrator fee through the bridge provider instead of on-chain; the fee still goes to feeRecipient, but it comes out of the token entering the bridge, which is not sellToken when the route swaps before bridging. Read fees.integratorFee.token for the token actually charged. Note: integrator fee collection is not yet supported for Tron-originated routes."
+                        "description": "The token addresses for fee collection on the origin chain (supports single or comma-separated values). Must be the same as sellToken. When multiple values are provided, must match the length of feeBps or feePpm. If omitted, defaults to sellToken. Some routes collect the integrator fee through the bridge provider instead of on-chain; the fee still goes to feeRecipient, but it comes out of the token entering the bridge, which is not sellToken when the route swaps before bridging. Read fees.integratorFee.token for the token actually charged. Note: integrator fee collection is not yet supported for Tron-originated routes."
                     },
                     {
                         "name": "maxNumQuotes",