@sureel/sdk 1.15.0-rc.9 → 1.15.1

package/models/put-asset-metadata-response.js

@@ -3,7 +3,7 @@
 /* eslint-disable */
 /**
  * Sureel API
- * ### 🔐 OAuth Authentication To access the Sureel API, the following set of variables will be necessary:      {       \"auth_url\": \"https://dev-p48agspfw4i7fkld.eu.auth0.com/oauth/token\",       \"client_id\": \"<Your-Client-Id>\",       \"client_secret\": \"<Your-Client-Secret>\",       \"audience\": \"https://api.dev.reelx.xyz/\"     }  Note: We provide the `client_id` and `client_secret` separately.  **Token Request Example:**      curl --request POST \\       --url https://dev-p48agspfw4i7fkld.eu.auth0.com/oauth/token \\       --header \'content-type: application/json\' \\       --data \'{         \"client_id\": \"<Your-Client-Id>\",         \"client_secret\": \"<Your-Client-Secret>\",         \"audience\": \"https://api.dev.reelx.xyz/\",         \"grant_type\": \"client_credentials\"       }\'  Include the token in your API requests:      Authorization: Bearer <your_token>  **Troubleshooting** - Ensure your token hasn’t expired - Check the Authorization header format - Confirm you\'re using the correct audience   ### 📥 Getting the Request Result You can retrieve processing results in two ways:  - **Polling**:   For audio requests, retrieve results from the <a href=\"#tag/audio-ai/paths/~1v1~1ai~1audio-ldm~1%7BrequestId%7D/get\">/v1/ai/audio-ldm/{requestId}</a> endpoint; for image requests, use the <a href=\"#tag/image-ai/operation/getResultByRequestId\">/v1/ai/ldm/{requestId}</a> endpoint. Make sure the `requestId` is obtained from the POST response. Processing time may vary.  - **Webhooks**: Include a `webhook_url` (and optional `webhook_key`) in your POST body to receive results asynchronously.  **Troubleshooting** - Verify the webhook URL is publicly accessible - Check that your server handles the webhook key - Ensure the request is fully processed   ### 📦 Using the SDK If you\'re building with Node.js or TypeScript, you can use our official SDK for easier integration: <a href=\"https://www.npmjs.com/package/@sureel/sdk\" target=\"_blank\">@sureel/sdk on npm</a>.  ### 🧠 Reading Temporal Attribution Results - `duration`: Length (in seconds) of each analysis window - `period`: Interval (in seconds) between segment starts  If `duration > period`, the analysis uses overlapping segments to improve accuracy. If both values are `-1`, the full song is analyzed in one pass.
+ * ### 🔐 OAuth Authentication To access the Sureel API, the following set of variables will be necessary:      {       \"auth_url\": \"https://sureel.eu.auth0.com/oauth/token\",       \"client_id\": \"<Your-Client-Id>\",       \"client_secret\": \"<Your-Client-Secret>\",       \"audience\": \"https://api.sureel.ai\"     }  Note: We provide the `client_id` and `client_secret` separately.  **Token Request Example:**      curl --request POST \\       --url https://sureel.eu.auth0.com/oauth/token \\       --header \'content-type: application/json\' \\       --data \'{         \"client_id\": \"<Your-Client-Id>\",         \"client_secret\": \"<Your-Client-Secret>\",         \"audience\": \"https://api.sureel.ai\",         \"grant_type\": \"client_credentials\"       }\'  Include the token in your API requests:      Authorization: Bearer <your_token>  **Troubleshooting** - Ensure your token hasn’t expired - Check the Authorization header format - Confirm you\'re using the correct audience   ### 📥 Getting the Request Result You can retrieve processing results in two ways:  - **Polling**:   For audio requests, retrieve results from the <a href=\"#tag/audio-ai/paths/~1v1~1ai~1audio-ldm~1%7BrequestId%7D/get\">/v1/ai/audio-ldm/{requestId}</a> endpoint; for image requests, use the <a href=\"#tag/image-ai/operation/getResultByRequestId\">/v1/ai/ldm/{requestId}</a> endpoint. Make sure the `requestId` is obtained from the POST response. Processing time may vary.  - **Webhooks**: Include a `webhook_url` (and optional `webhook_key`) in your POST body to receive results asynchronously.  **Troubleshooting** - Verify the webhook URL is publicly accessible - Check that your server handles the webhook key - Ensure the request is fully processed   ### 📦 Using the SDK If you\'re building with Node.js or TypeScript, you can use our official SDK for easier integration: <a href=\"https://www.npmjs.com/package/@sureel/sdk\" target=\"_blank\">@sureel/sdk on npm</a>.  ### 🧠 Reading Temporal Attribution Results - `duration`: Length (in seconds) of each analysis window - `period`: Interval (in seconds) between segment starts  If `duration > period`, the analysis uses overlapping segments to improve accuracy. If both values are `-1`, the full song is analyzed in one pass.
  *
  * The version of the OpenAPI document:
  *

package/models/recording-contributor.d.ts

@@ -1,6 +1,6 @@
 /**
  * Sureel API
- * ### 🔐 OAuth Authentication To access the Sureel API, the following set of variables will be necessary:      {       \"auth_url\": \"https://dev-p48agspfw4i7fkld.eu.auth0.com/oauth/token\",       \"client_id\": \"<Your-Client-Id>\",       \"client_secret\": \"<Your-Client-Secret>\",       \"audience\": \"https://api.dev.reelx.xyz/\"     }  Note: We provide the `client_id` and `client_secret` separately.  **Token Request Example:**      curl --request POST \\       --url https://dev-p48agspfw4i7fkld.eu.auth0.com/oauth/token \\       --header \'content-type: application/json\' \\       --data \'{         \"client_id\": \"<Your-Client-Id>\",         \"client_secret\": \"<Your-Client-Secret>\",         \"audience\": \"https://api.dev.reelx.xyz/\",         \"grant_type\": \"client_credentials\"       }\'  Include the token in your API requests:      Authorization: Bearer <your_token>  **Troubleshooting** - Ensure your token hasn’t expired - Check the Authorization header format - Confirm you\'re using the correct audience   ### 📥 Getting the Request Result You can retrieve processing results in two ways:  - **Polling**:   For audio requests, retrieve results from the <a href=\"#tag/audio-ai/paths/~1v1~1ai~1audio-ldm~1%7BrequestId%7D/get\">/v1/ai/audio-ldm/{requestId}</a> endpoint; for image requests, use the <a href=\"#tag/image-ai/operation/getResultByRequestId\">/v1/ai/ldm/{requestId}</a> endpoint. Make sure the `requestId` is obtained from the POST response. Processing time may vary.  - **Webhooks**: Include a `webhook_url` (and optional `webhook_key`) in your POST body to receive results asynchronously.  **Troubleshooting** - Verify the webhook URL is publicly accessible - Check that your server handles the webhook key - Ensure the request is fully processed   ### 📦 Using the SDK If you\'re building with Node.js or TypeScript, you can use our official SDK for easier integration: <a href=\"https://www.npmjs.com/package/@sureel/sdk\" target=\"_blank\">@sureel/sdk on npm</a>.  ### 🧠 Reading Temporal Attribution Results - `duration`: Length (in seconds) of each analysis window - `period`: Interval (in seconds) between segment starts  If `duration > period`, the analysis uses overlapping segments to improve accuracy. If both values are `-1`, the full song is analyzed in one pass.
+ * ### 🔐 OAuth Authentication To access the Sureel API, the following set of variables will be necessary:      {       \"auth_url\": \"https://sureel.eu.auth0.com/oauth/token\",       \"client_id\": \"<Your-Client-Id>\",       \"client_secret\": \"<Your-Client-Secret>\",       \"audience\": \"https://api.sureel.ai\"     }  Note: We provide the `client_id` and `client_secret` separately.  **Token Request Example:**      curl --request POST \\       --url https://sureel.eu.auth0.com/oauth/token \\       --header \'content-type: application/json\' \\       --data \'{         \"client_id\": \"<Your-Client-Id>\",         \"client_secret\": \"<Your-Client-Secret>\",         \"audience\": \"https://api.sureel.ai\",         \"grant_type\": \"client_credentials\"       }\'  Include the token in your API requests:      Authorization: Bearer <your_token>  **Troubleshooting** - Ensure your token hasn’t expired - Check the Authorization header format - Confirm you\'re using the correct audience   ### 📥 Getting the Request Result You can retrieve processing results in two ways:  - **Polling**:   For audio requests, retrieve results from the <a href=\"#tag/audio-ai/paths/~1v1~1ai~1audio-ldm~1%7BrequestId%7D/get\">/v1/ai/audio-ldm/{requestId}</a> endpoint; for image requests, use the <a href=\"#tag/image-ai/operation/getResultByRequestId\">/v1/ai/ldm/{requestId}</a> endpoint. Make sure the `requestId` is obtained from the POST response. Processing time may vary.  - **Webhooks**: Include a `webhook_url` (and optional `webhook_key`) in your POST body to receive results asynchronously.  **Troubleshooting** - Verify the webhook URL is publicly accessible - Check that your server handles the webhook key - Ensure the request is fully processed   ### 📦 Using the SDK If you\'re building with Node.js or TypeScript, you can use our official SDK for easier integration: <a href=\"https://www.npmjs.com/package/@sureel/sdk\" target=\"_blank\">@sureel/sdk on npm</a>.  ### 🧠 Reading Temporal Attribution Results - `duration`: Length (in seconds) of each analysis window - `period`: Interval (in seconds) between segment starts  If `duration > period`, the analysis uses overlapping segments to improve accuracy. If both values are `-1`, the full song is analyzed in one pass.
  *
  * The version of the OpenAPI document:
  *
@@ -10,18 +10,13 @@
  * Do not edit the class manually.
  */
 import type { ContributorRole } from "./contributor-role";
+import type { OptInRules } from "./opt-in-rules";
 /**
  *
  * @export
  * @interface RecordingContributor
  */
 export interface RecordingContributor {
-    /**
-     * Indicates whether to allow AI training on the recording data.
-     * @type {boolean}
-     * @memberof RecordingContributor
-     */
-    allow_ai_training?: boolean;
     /**
      * The contributor of the recording.
      * @type {string}
@@ -46,5 +41,23 @@ export interface RecordingContributor {
      * @memberof RecordingContributor
      */
     territory?: string;
+    /**
+     * Indicates whether to allow AI training on the recording data.
+     * @type {boolean}
+     * @memberof RecordingContributor
+     */
+    allow_ai_training?: boolean;
+    /**
+     *
+     * @type {OptInRules}
+     * @memberof RecordingContributor
+     */
+    opt_in_rules?: OptInRules;
+    /**
+     * Set to true to remove this contributor during a merge update.
+     * @type {boolean}
+     * @memberof RecordingContributor
+     */
+    _delete?: boolean;
 }
 //# sourceMappingURL=recording-contributor.d.ts.map

package/models/recording-contributor.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"recording-contributor.d.ts","sourceRoot":"","sources":["../../src/models/recording-contributor.ts"],"names":[],"mappings":"AAEA;;;;;;;;;;GAUG;AAIH,OAAO,KAAK,EAAE,eAAe,EAAE,MAAM,oBAAoB,CAAA;AAEzD;;;;GAIG;AACH,MAAM,WAAW,oBAAoB;IACjC;;;;OAIG;IACH,iBAAiB,CAAC,EAAE,OAAO,CAAA;IAC3B;;;;OAIG;IACH,WAAW,CAAC,EAAE,MAAM,CAAA;IACpB;;;;OAIG;IACH,gBAAgB,CAAC,EAAE,eAAe,CAAA;IAClC;;;;OAIG;IACH,gBAAgB,CAAC,EAAE,MAAM,CAAA;IACzB;;;;OAIG;IACH,SAAS,CAAC,EAAE,MAAM,CAAA;CACrB"}
+{"version":3,"file":"recording-contributor.d.ts","sourceRoot":"","sources":["../../src/models/recording-contributor.ts"],"names":[],"mappings":"AAEA;;;;;;;;;;GAUG;AAIH,OAAO,KAAK,EAAE,eAAe,EAAE,MAAM,oBAAoB,CAAA;AAGzD,OAAO,KAAK,EAAE,UAAU,EAAE,MAAM,gBAAgB,CAAA;AAEhD;;;;GAIG;AACH,MAAM,WAAW,oBAAoB;IACjC;;;;OAIG;IACH,WAAW,CAAC,EAAE,MAAM,CAAA;IACpB;;;;OAIG;IACH,gBAAgB,CAAC,EAAE,eAAe,CAAA;IAClC;;;;OAIG;IACH,gBAAgB,CAAC,EAAE,MAAM,CAAA;IACzB;;;;OAIG;IACH,SAAS,CAAC,EAAE,MAAM,CAAA;IAClB;;;;OAIG;IACH,iBAAiB,CAAC,EAAE,OAAO,CAAA;IAC3B;;;;OAIG;IACH,YAAY,CAAC,EAAE,UAAU,CAAA;IACzB;;;;OAIG;IACH,OAAO,CAAC,EAAE,OAAO,CAAA;CACpB"}

package/models/recording-contributor.js

@@ -3,7 +3,7 @@
 /* eslint-disable */
 /**
  * Sureel API
- * ### 🔐 OAuth Authentication To access the Sureel API, the following set of variables will be necessary:      {       \"auth_url\": \"https://dev-p48agspfw4i7fkld.eu.auth0.com/oauth/token\",       \"client_id\": \"<Your-Client-Id>\",       \"client_secret\": \"<Your-Client-Secret>\",       \"audience\": \"https://api.dev.reelx.xyz/\"     }  Note: We provide the `client_id` and `client_secret` separately.  **Token Request Example:**      curl --request POST \\       --url https://dev-p48agspfw4i7fkld.eu.auth0.com/oauth/token \\       --header \'content-type: application/json\' \\       --data \'{         \"client_id\": \"<Your-Client-Id>\",         \"client_secret\": \"<Your-Client-Secret>\",         \"audience\": \"https://api.dev.reelx.xyz/\",         \"grant_type\": \"client_credentials\"       }\'  Include the token in your API requests:      Authorization: Bearer <your_token>  **Troubleshooting** - Ensure your token hasn’t expired - Check the Authorization header format - Confirm you\'re using the correct audience   ### 📥 Getting the Request Result You can retrieve processing results in two ways:  - **Polling**:   For audio requests, retrieve results from the <a href=\"#tag/audio-ai/paths/~1v1~1ai~1audio-ldm~1%7BrequestId%7D/get\">/v1/ai/audio-ldm/{requestId}</a> endpoint; for image requests, use the <a href=\"#tag/image-ai/operation/getResultByRequestId\">/v1/ai/ldm/{requestId}</a> endpoint. Make sure the `requestId` is obtained from the POST response. Processing time may vary.  - **Webhooks**: Include a `webhook_url` (and optional `webhook_key`) in your POST body to receive results asynchronously.  **Troubleshooting** - Verify the webhook URL is publicly accessible - Check that your server handles the webhook key - Ensure the request is fully processed   ### 📦 Using the SDK If you\'re building with Node.js or TypeScript, you can use our official SDK for easier integration: <a href=\"https://www.npmjs.com/package/@sureel/sdk\" target=\"_blank\">@sureel/sdk on npm</a>.  ### 🧠 Reading Temporal Attribution Results - `duration`: Length (in seconds) of each analysis window - `period`: Interval (in seconds) between segment starts  If `duration > period`, the analysis uses overlapping segments to improve accuracy. If both values are `-1`, the full song is analyzed in one pass.
+ * ### 🔐 OAuth Authentication To access the Sureel API, the following set of variables will be necessary:      {       \"auth_url\": \"https://sureel.eu.auth0.com/oauth/token\",       \"client_id\": \"<Your-Client-Id>\",       \"client_secret\": \"<Your-Client-Secret>\",       \"audience\": \"https://api.sureel.ai\"     }  Note: We provide the `client_id` and `client_secret` separately.  **Token Request Example:**      curl --request POST \\       --url https://sureel.eu.auth0.com/oauth/token \\       --header \'content-type: application/json\' \\       --data \'{         \"client_id\": \"<Your-Client-Id>\",         \"client_secret\": \"<Your-Client-Secret>\",         \"audience\": \"https://api.sureel.ai\",         \"grant_type\": \"client_credentials\"       }\'  Include the token in your API requests:      Authorization: Bearer <your_token>  **Troubleshooting** - Ensure your token hasn’t expired - Check the Authorization header format - Confirm you\'re using the correct audience   ### 📥 Getting the Request Result You can retrieve processing results in two ways:  - **Polling**:   For audio requests, retrieve results from the <a href=\"#tag/audio-ai/paths/~1v1~1ai~1audio-ldm~1%7BrequestId%7D/get\">/v1/ai/audio-ldm/{requestId}</a> endpoint; for image requests, use the <a href=\"#tag/image-ai/operation/getResultByRequestId\">/v1/ai/ldm/{requestId}</a> endpoint. Make sure the `requestId` is obtained from the POST response. Processing time may vary.  - **Webhooks**: Include a `webhook_url` (and optional `webhook_key`) in your POST body to receive results asynchronously.  **Troubleshooting** - Verify the webhook URL is publicly accessible - Check that your server handles the webhook key - Ensure the request is fully processed   ### 📦 Using the SDK If you\'re building with Node.js or TypeScript, you can use our official SDK for easier integration: <a href=\"https://www.npmjs.com/package/@sureel/sdk\" target=\"_blank\">@sureel/sdk on npm</a>.  ### 🧠 Reading Temporal Attribution Results - `duration`: Length (in seconds) of each analysis window - `period`: Interval (in seconds) between segment starts  If `duration > period`, the analysis uses overlapping segments to improve accuracy. If both values are `-1`, the full song is analyzed in one pass.
  *
  * The version of the OpenAPI document:
  *

package/models/reimagine-request.d.ts

@@ -1,6 +1,6 @@
 /**
  * Sureel API
- * ### 🔐 OAuth Authentication To access the Sureel API, the following set of variables will be necessary:      {       \"auth_url\": \"https://dev-p48agspfw4i7fkld.eu.auth0.com/oauth/token\",       \"client_id\": \"<Your-Client-Id>\",       \"client_secret\": \"<Your-Client-Secret>\",       \"audience\": \"https://api.dev.reelx.xyz/\"     }  Note: We provide the `client_id` and `client_secret` separately.  **Token Request Example:**      curl --request POST \\       --url https://dev-p48agspfw4i7fkld.eu.auth0.com/oauth/token \\       --header \'content-type: application/json\' \\       --data \'{         \"client_id\": \"<Your-Client-Id>\",         \"client_secret\": \"<Your-Client-Secret>\",         \"audience\": \"https://api.dev.reelx.xyz/\",         \"grant_type\": \"client_credentials\"       }\'  Include the token in your API requests:      Authorization: Bearer <your_token>  **Troubleshooting** - Ensure your token hasn’t expired - Check the Authorization header format - Confirm you\'re using the correct audience   ### 📥 Getting the Request Result You can retrieve processing results in two ways:  - **Polling**:   For audio requests, retrieve results from the <a href=\"#tag/audio-ai/paths/~1v1~1ai~1audio-ldm~1%7BrequestId%7D/get\">/v1/ai/audio-ldm/{requestId}</a> endpoint; for image requests, use the <a href=\"#tag/image-ai/operation/getResultByRequestId\">/v1/ai/ldm/{requestId}</a> endpoint. Make sure the `requestId` is obtained from the POST response. Processing time may vary.  - **Webhooks**: Include a `webhook_url` (and optional `webhook_key`) in your POST body to receive results asynchronously.  **Troubleshooting** - Verify the webhook URL is publicly accessible - Check that your server handles the webhook key - Ensure the request is fully processed   ### 📦 Using the SDK If you\'re building with Node.js or TypeScript, you can use our official SDK for easier integration: <a href=\"https://www.npmjs.com/package/@sureel/sdk\" target=\"_blank\">@sureel/sdk on npm</a>.  ### 🧠 Reading Temporal Attribution Results - `duration`: Length (in seconds) of each analysis window - `period`: Interval (in seconds) between segment starts  If `duration > period`, the analysis uses overlapping segments to improve accuracy. If both values are `-1`, the full song is analyzed in one pass.
+ * ### 🔐 OAuth Authentication To access the Sureel API, the following set of variables will be necessary:      {       \"auth_url\": \"https://sureel.eu.auth0.com/oauth/token\",       \"client_id\": \"<Your-Client-Id>\",       \"client_secret\": \"<Your-Client-Secret>\",       \"audience\": \"https://api.sureel.ai\"     }  Note: We provide the `client_id` and `client_secret` separately.  **Token Request Example:**      curl --request POST \\       --url https://sureel.eu.auth0.com/oauth/token \\       --header \'content-type: application/json\' \\       --data \'{         \"client_id\": \"<Your-Client-Id>\",         \"client_secret\": \"<Your-Client-Secret>\",         \"audience\": \"https://api.sureel.ai\",         \"grant_type\": \"client_credentials\"       }\'  Include the token in your API requests:      Authorization: Bearer <your_token>  **Troubleshooting** - Ensure your token hasn’t expired - Check the Authorization header format - Confirm you\'re using the correct audience   ### 📥 Getting the Request Result You can retrieve processing results in two ways:  - **Polling**:   For audio requests, retrieve results from the <a href=\"#tag/audio-ai/paths/~1v1~1ai~1audio-ldm~1%7BrequestId%7D/get\">/v1/ai/audio-ldm/{requestId}</a> endpoint; for image requests, use the <a href=\"#tag/image-ai/operation/getResultByRequestId\">/v1/ai/ldm/{requestId}</a> endpoint. Make sure the `requestId` is obtained from the POST response. Processing time may vary.  - **Webhooks**: Include a `webhook_url` (and optional `webhook_key`) in your POST body to receive results asynchronously.  **Troubleshooting** - Verify the webhook URL is publicly accessible - Check that your server handles the webhook key - Ensure the request is fully processed   ### 📦 Using the SDK If you\'re building with Node.js or TypeScript, you can use our official SDK for easier integration: <a href=\"https://www.npmjs.com/package/@sureel/sdk\" target=\"_blank\">@sureel/sdk on npm</a>.  ### 🧠 Reading Temporal Attribution Results - `duration`: Length (in seconds) of each analysis window - `period`: Interval (in seconds) between segment starts  If `duration > period`, the analysis uses overlapping segments to improve accuracy. If both values are `-1`, the full song is analyzed in one pass.
  *
  * The version of the OpenAPI document:
  *

package/models/reimagine-request.js

@@ -3,7 +3,7 @@
 /* eslint-disable */
 /**
  * Sureel API
- * ### 🔐 OAuth Authentication To access the Sureel API, the following set of variables will be necessary:      {       \"auth_url\": \"https://dev-p48agspfw4i7fkld.eu.auth0.com/oauth/token\",       \"client_id\": \"<Your-Client-Id>\",       \"client_secret\": \"<Your-Client-Secret>\",       \"audience\": \"https://api.dev.reelx.xyz/\"     }  Note: We provide the `client_id` and `client_secret` separately.  **Token Request Example:**      curl --request POST \\       --url https://dev-p48agspfw4i7fkld.eu.auth0.com/oauth/token \\       --header \'content-type: application/json\' \\       --data \'{         \"client_id\": \"<Your-Client-Id>\",         \"client_secret\": \"<Your-Client-Secret>\",         \"audience\": \"https://api.dev.reelx.xyz/\",         \"grant_type\": \"client_credentials\"       }\'  Include the token in your API requests:      Authorization: Bearer <your_token>  **Troubleshooting** - Ensure your token hasn’t expired - Check the Authorization header format - Confirm you\'re using the correct audience   ### 📥 Getting the Request Result You can retrieve processing results in two ways:  - **Polling**:   For audio requests, retrieve results from the <a href=\"#tag/audio-ai/paths/~1v1~1ai~1audio-ldm~1%7BrequestId%7D/get\">/v1/ai/audio-ldm/{requestId}</a> endpoint; for image requests, use the <a href=\"#tag/image-ai/operation/getResultByRequestId\">/v1/ai/ldm/{requestId}</a> endpoint. Make sure the `requestId` is obtained from the POST response. Processing time may vary.  - **Webhooks**: Include a `webhook_url` (and optional `webhook_key`) in your POST body to receive results asynchronously.  **Troubleshooting** - Verify the webhook URL is publicly accessible - Check that your server handles the webhook key - Ensure the request is fully processed   ### 📦 Using the SDK If you\'re building with Node.js or TypeScript, you can use our official SDK for easier integration: <a href=\"https://www.npmjs.com/package/@sureel/sdk\" target=\"_blank\">@sureel/sdk on npm</a>.  ### 🧠 Reading Temporal Attribution Results - `duration`: Length (in seconds) of each analysis window - `period`: Interval (in seconds) between segment starts  If `duration > period`, the analysis uses overlapping segments to improve accuracy. If both values are `-1`, the full song is analyzed in one pass.
+ * ### 🔐 OAuth Authentication To access the Sureel API, the following set of variables will be necessary:      {       \"auth_url\": \"https://sureel.eu.auth0.com/oauth/token\",       \"client_id\": \"<Your-Client-Id>\",       \"client_secret\": \"<Your-Client-Secret>\",       \"audience\": \"https://api.sureel.ai\"     }  Note: We provide the `client_id` and `client_secret` separately.  **Token Request Example:**      curl --request POST \\       --url https://sureel.eu.auth0.com/oauth/token \\       --header \'content-type: application/json\' \\       --data \'{         \"client_id\": \"<Your-Client-Id>\",         \"client_secret\": \"<Your-Client-Secret>\",         \"audience\": \"https://api.sureel.ai\",         \"grant_type\": \"client_credentials\"       }\'  Include the token in your API requests:      Authorization: Bearer <your_token>  **Troubleshooting** - Ensure your token hasn’t expired - Check the Authorization header format - Confirm you\'re using the correct audience   ### 📥 Getting the Request Result You can retrieve processing results in two ways:  - **Polling**:   For audio requests, retrieve results from the <a href=\"#tag/audio-ai/paths/~1v1~1ai~1audio-ldm~1%7BrequestId%7D/get\">/v1/ai/audio-ldm/{requestId}</a> endpoint; for image requests, use the <a href=\"#tag/image-ai/operation/getResultByRequestId\">/v1/ai/ldm/{requestId}</a> endpoint. Make sure the `requestId` is obtained from the POST response. Processing time may vary.  - **Webhooks**: Include a `webhook_url` (and optional `webhook_key`) in your POST body to receive results asynchronously.  **Troubleshooting** - Verify the webhook URL is publicly accessible - Check that your server handles the webhook key - Ensure the request is fully processed   ### 📦 Using the SDK If you\'re building with Node.js or TypeScript, you can use our official SDK for easier integration: <a href=\"https://www.npmjs.com/package/@sureel/sdk\" target=\"_blank\">@sureel/sdk on npm</a>.  ### 🧠 Reading Temporal Attribution Results - `duration`: Length (in seconds) of each analysis window - `period`: Interval (in seconds) between segment starts  If `duration > period`, the analysis uses overlapping segments to improve accuracy. If both values are `-1`, the full song is analyzed in one pass.
  *
  * The version of the OpenAPI document:
  *

package/models/remove-background-request.d.ts

@@ -1,6 +1,6 @@
 /**
  * Sureel API
- * ### 🔐 OAuth Authentication To access the Sureel API, the following set of variables will be necessary:      {       \"auth_url\": \"https://dev-p48agspfw4i7fkld.eu.auth0.com/oauth/token\",       \"client_id\": \"<Your-Client-Id>\",       \"client_secret\": \"<Your-Client-Secret>\",       \"audience\": \"https://api.dev.reelx.xyz/\"     }  Note: We provide the `client_id` and `client_secret` separately.  **Token Request Example:**      curl --request POST \\       --url https://dev-p48agspfw4i7fkld.eu.auth0.com/oauth/token \\       --header \'content-type: application/json\' \\       --data \'{         \"client_id\": \"<Your-Client-Id>\",         \"client_secret\": \"<Your-Client-Secret>\",         \"audience\": \"https://api.dev.reelx.xyz/\",         \"grant_type\": \"client_credentials\"       }\'  Include the token in your API requests:      Authorization: Bearer <your_token>  **Troubleshooting** - Ensure your token hasn’t expired - Check the Authorization header format - Confirm you\'re using the correct audience   ### 📥 Getting the Request Result You can retrieve processing results in two ways:  - **Polling**:   For audio requests, retrieve results from the <a href=\"#tag/audio-ai/paths/~1v1~1ai~1audio-ldm~1%7BrequestId%7D/get\">/v1/ai/audio-ldm/{requestId}</a> endpoint; for image requests, use the <a href=\"#tag/image-ai/operation/getResultByRequestId\">/v1/ai/ldm/{requestId}</a> endpoint. Make sure the `requestId` is obtained from the POST response. Processing time may vary.  - **Webhooks**: Include a `webhook_url` (and optional `webhook_key`) in your POST body to receive results asynchronously.  **Troubleshooting** - Verify the webhook URL is publicly accessible - Check that your server handles the webhook key - Ensure the request is fully processed   ### 📦 Using the SDK If you\'re building with Node.js or TypeScript, you can use our official SDK for easier integration: <a href=\"https://www.npmjs.com/package/@sureel/sdk\" target=\"_blank\">@sureel/sdk on npm</a>.  ### 🧠 Reading Temporal Attribution Results - `duration`: Length (in seconds) of each analysis window - `period`: Interval (in seconds) between segment starts  If `duration > period`, the analysis uses overlapping segments to improve accuracy. If both values are `-1`, the full song is analyzed in one pass.
+ * ### 🔐 OAuth Authentication To access the Sureel API, the following set of variables will be necessary:      {       \"auth_url\": \"https://sureel.eu.auth0.com/oauth/token\",       \"client_id\": \"<Your-Client-Id>\",       \"client_secret\": \"<Your-Client-Secret>\",       \"audience\": \"https://api.sureel.ai\"     }  Note: We provide the `client_id` and `client_secret` separately.  **Token Request Example:**      curl --request POST \\       --url https://sureel.eu.auth0.com/oauth/token \\       --header \'content-type: application/json\' \\       --data \'{         \"client_id\": \"<Your-Client-Id>\",         \"client_secret\": \"<Your-Client-Secret>\",         \"audience\": \"https://api.sureel.ai\",         \"grant_type\": \"client_credentials\"       }\'  Include the token in your API requests:      Authorization: Bearer <your_token>  **Troubleshooting** - Ensure your token hasn’t expired - Check the Authorization header format - Confirm you\'re using the correct audience   ### 📥 Getting the Request Result You can retrieve processing results in two ways:  - **Polling**:   For audio requests, retrieve results from the <a href=\"#tag/audio-ai/paths/~1v1~1ai~1audio-ldm~1%7BrequestId%7D/get\">/v1/ai/audio-ldm/{requestId}</a> endpoint; for image requests, use the <a href=\"#tag/image-ai/operation/getResultByRequestId\">/v1/ai/ldm/{requestId}</a> endpoint. Make sure the `requestId` is obtained from the POST response. Processing time may vary.  - **Webhooks**: Include a `webhook_url` (and optional `webhook_key`) in your POST body to receive results asynchronously.  **Troubleshooting** - Verify the webhook URL is publicly accessible - Check that your server handles the webhook key - Ensure the request is fully processed   ### 📦 Using the SDK If you\'re building with Node.js or TypeScript, you can use our official SDK for easier integration: <a href=\"https://www.npmjs.com/package/@sureel/sdk\" target=\"_blank\">@sureel/sdk on npm</a>.  ### 🧠 Reading Temporal Attribution Results - `duration`: Length (in seconds) of each analysis window - `period`: Interval (in seconds) between segment starts  If `duration > period`, the analysis uses overlapping segments to improve accuracy. If both values are `-1`, the full song is analyzed in one pass.
  *
  * The version of the OpenAPI document:
  *

package/models/remove-background-request.js

@@ -3,7 +3,7 @@
 /* eslint-disable */
 /**
  * Sureel API
- * ### 🔐 OAuth Authentication To access the Sureel API, the following set of variables will be necessary:      {       \"auth_url\": \"https://dev-p48agspfw4i7fkld.eu.auth0.com/oauth/token\",       \"client_id\": \"<Your-Client-Id>\",       \"client_secret\": \"<Your-Client-Secret>\",       \"audience\": \"https://api.dev.reelx.xyz/\"     }  Note: We provide the `client_id` and `client_secret` separately.  **Token Request Example:**      curl --request POST \\       --url https://dev-p48agspfw4i7fkld.eu.auth0.com/oauth/token \\       --header \'content-type: application/json\' \\       --data \'{         \"client_id\": \"<Your-Client-Id>\",         \"client_secret\": \"<Your-Client-Secret>\",         \"audience\": \"https://api.dev.reelx.xyz/\",         \"grant_type\": \"client_credentials\"       }\'  Include the token in your API requests:      Authorization: Bearer <your_token>  **Troubleshooting** - Ensure your token hasn’t expired - Check the Authorization header format - Confirm you\'re using the correct audience   ### 📥 Getting the Request Result You can retrieve processing results in two ways:  - **Polling**:   For audio requests, retrieve results from the <a href=\"#tag/audio-ai/paths/~1v1~1ai~1audio-ldm~1%7BrequestId%7D/get\">/v1/ai/audio-ldm/{requestId}</a> endpoint; for image requests, use the <a href=\"#tag/image-ai/operation/getResultByRequestId\">/v1/ai/ldm/{requestId}</a> endpoint. Make sure the `requestId` is obtained from the POST response. Processing time may vary.  - **Webhooks**: Include a `webhook_url` (and optional `webhook_key`) in your POST body to receive results asynchronously.  **Troubleshooting** - Verify the webhook URL is publicly accessible - Check that your server handles the webhook key - Ensure the request is fully processed   ### 📦 Using the SDK If you\'re building with Node.js or TypeScript, you can use our official SDK for easier integration: <a href=\"https://www.npmjs.com/package/@sureel/sdk\" target=\"_blank\">@sureel/sdk on npm</a>.  ### 🧠 Reading Temporal Attribution Results - `duration`: Length (in seconds) of each analysis window - `period`: Interval (in seconds) between segment starts  If `duration > period`, the analysis uses overlapping segments to improve accuracy. If both values are `-1`, the full song is analyzed in one pass.
+ * ### 🔐 OAuth Authentication To access the Sureel API, the following set of variables will be necessary:      {       \"auth_url\": \"https://sureel.eu.auth0.com/oauth/token\",       \"client_id\": \"<Your-Client-Id>\",       \"client_secret\": \"<Your-Client-Secret>\",       \"audience\": \"https://api.sureel.ai\"     }  Note: We provide the `client_id` and `client_secret` separately.  **Token Request Example:**      curl --request POST \\       --url https://sureel.eu.auth0.com/oauth/token \\       --header \'content-type: application/json\' \\       --data \'{         \"client_id\": \"<Your-Client-Id>\",         \"client_secret\": \"<Your-Client-Secret>\",         \"audience\": \"https://api.sureel.ai\",         \"grant_type\": \"client_credentials\"       }\'  Include the token in your API requests:      Authorization: Bearer <your_token>  **Troubleshooting** - Ensure your token hasn’t expired - Check the Authorization header format - Confirm you\'re using the correct audience   ### 📥 Getting the Request Result You can retrieve processing results in two ways:  - **Polling**:   For audio requests, retrieve results from the <a href=\"#tag/audio-ai/paths/~1v1~1ai~1audio-ldm~1%7BrequestId%7D/get\">/v1/ai/audio-ldm/{requestId}</a> endpoint; for image requests, use the <a href=\"#tag/image-ai/operation/getResultByRequestId\">/v1/ai/ldm/{requestId}</a> endpoint. Make sure the `requestId` is obtained from the POST response. Processing time may vary.  - **Webhooks**: Include a `webhook_url` (and optional `webhook_key`) in your POST body to receive results asynchronously.  **Troubleshooting** - Verify the webhook URL is publicly accessible - Check that your server handles the webhook key - Ensure the request is fully processed   ### 📦 Using the SDK If you\'re building with Node.js or TypeScript, you can use our official SDK for easier integration: <a href=\"https://www.npmjs.com/package/@sureel/sdk\" target=\"_blank\">@sureel/sdk on npm</a>.  ### 🧠 Reading Temporal Attribution Results - `duration`: Length (in seconds) of each analysis window - `period`: Interval (in seconds) between segment starts  If `duration > period`, the analysis uses overlapping segments to improve accuracy. If both values are `-1`, the full song is analyzed in one pass.
  *
  * The version of the OpenAPI document:
  *

package/models/resolution.d.ts

@@ -1,6 +1,6 @@
 /**
  * Sureel API
- * ### 🔐 OAuth Authentication To access the Sureel API, the following set of variables will be necessary:      {       \"auth_url\": \"https://dev-p48agspfw4i7fkld.eu.auth0.com/oauth/token\",       \"client_id\": \"<Your-Client-Id>\",       \"client_secret\": \"<Your-Client-Secret>\",       \"audience\": \"https://api.dev.reelx.xyz/\"     }  Note: We provide the `client_id` and `client_secret` separately.  **Token Request Example:**      curl --request POST \\       --url https://dev-p48agspfw4i7fkld.eu.auth0.com/oauth/token \\       --header \'content-type: application/json\' \\       --data \'{         \"client_id\": \"<Your-Client-Id>\",         \"client_secret\": \"<Your-Client-Secret>\",         \"audience\": \"https://api.dev.reelx.xyz/\",         \"grant_type\": \"client_credentials\"       }\'  Include the token in your API requests:      Authorization: Bearer <your_token>  **Troubleshooting** - Ensure your token hasn’t expired - Check the Authorization header format - Confirm you\'re using the correct audience   ### 📥 Getting the Request Result You can retrieve processing results in two ways:  - **Polling**:   For audio requests, retrieve results from the <a href=\"#tag/audio-ai/paths/~1v1~1ai~1audio-ldm~1%7BrequestId%7D/get\">/v1/ai/audio-ldm/{requestId}</a> endpoint; for image requests, use the <a href=\"#tag/image-ai/operation/getResultByRequestId\">/v1/ai/ldm/{requestId}</a> endpoint. Make sure the `requestId` is obtained from the POST response. Processing time may vary.  - **Webhooks**: Include a `webhook_url` (and optional `webhook_key`) in your POST body to receive results asynchronously.  **Troubleshooting** - Verify the webhook URL is publicly accessible - Check that your server handles the webhook key - Ensure the request is fully processed   ### 📦 Using the SDK If you\'re building with Node.js or TypeScript, you can use our official SDK for easier integration: <a href=\"https://www.npmjs.com/package/@sureel/sdk\" target=\"_blank\">@sureel/sdk on npm</a>.  ### 🧠 Reading Temporal Attribution Results - `duration`: Length (in seconds) of each analysis window - `period`: Interval (in seconds) between segment starts  If `duration > period`, the analysis uses overlapping segments to improve accuracy. If both values are `-1`, the full song is analyzed in one pass.
+ * ### 🔐 OAuth Authentication To access the Sureel API, the following set of variables will be necessary:      {       \"auth_url\": \"https://sureel.eu.auth0.com/oauth/token\",       \"client_id\": \"<Your-Client-Id>\",       \"client_secret\": \"<Your-Client-Secret>\",       \"audience\": \"https://api.sureel.ai\"     }  Note: We provide the `client_id` and `client_secret` separately.  **Token Request Example:**      curl --request POST \\       --url https://sureel.eu.auth0.com/oauth/token \\       --header \'content-type: application/json\' \\       --data \'{         \"client_id\": \"<Your-Client-Id>\",         \"client_secret\": \"<Your-Client-Secret>\",         \"audience\": \"https://api.sureel.ai\",         \"grant_type\": \"client_credentials\"       }\'  Include the token in your API requests:      Authorization: Bearer <your_token>  **Troubleshooting** - Ensure your token hasn’t expired - Check the Authorization header format - Confirm you\'re using the correct audience   ### 📥 Getting the Request Result You can retrieve processing results in two ways:  - **Polling**:   For audio requests, retrieve results from the <a href=\"#tag/audio-ai/paths/~1v1~1ai~1audio-ldm~1%7BrequestId%7D/get\">/v1/ai/audio-ldm/{requestId}</a> endpoint; for image requests, use the <a href=\"#tag/image-ai/operation/getResultByRequestId\">/v1/ai/ldm/{requestId}</a> endpoint. Make sure the `requestId` is obtained from the POST response. Processing time may vary.  - **Webhooks**: Include a `webhook_url` (and optional `webhook_key`) in your POST body to receive results asynchronously.  **Troubleshooting** - Verify the webhook URL is publicly accessible - Check that your server handles the webhook key - Ensure the request is fully processed   ### 📦 Using the SDK If you\'re building with Node.js or TypeScript, you can use our official SDK for easier integration: <a href=\"https://www.npmjs.com/package/@sureel/sdk\" target=\"_blank\">@sureel/sdk on npm</a>.  ### 🧠 Reading Temporal Attribution Results - `duration`: Length (in seconds) of each analysis window - `period`: Interval (in seconds) between segment starts  If `duration > period`, the analysis uses overlapping segments to improve accuracy. If both values are `-1`, the full song is analyzed in one pass.
  *
  * The version of the OpenAPI document:
  *

package/models/resolution.js

@@ -3,7 +3,7 @@
 /* eslint-disable */
 /**
  * Sureel API
- * ### 🔐 OAuth Authentication To access the Sureel API, the following set of variables will be necessary:      {       \"auth_url\": \"https://dev-p48agspfw4i7fkld.eu.auth0.com/oauth/token\",       \"client_id\": \"<Your-Client-Id>\",       \"client_secret\": \"<Your-Client-Secret>\",       \"audience\": \"https://api.dev.reelx.xyz/\"     }  Note: We provide the `client_id` and `client_secret` separately.  **Token Request Example:**      curl --request POST \\       --url https://dev-p48agspfw4i7fkld.eu.auth0.com/oauth/token \\       --header \'content-type: application/json\' \\       --data \'{         \"client_id\": \"<Your-Client-Id>\",         \"client_secret\": \"<Your-Client-Secret>\",         \"audience\": \"https://api.dev.reelx.xyz/\",         \"grant_type\": \"client_credentials\"       }\'  Include the token in your API requests:      Authorization: Bearer <your_token>  **Troubleshooting** - Ensure your token hasn’t expired - Check the Authorization header format - Confirm you\'re using the correct audience   ### 📥 Getting the Request Result You can retrieve processing results in two ways:  - **Polling**:   For audio requests, retrieve results from the <a href=\"#tag/audio-ai/paths/~1v1~1ai~1audio-ldm~1%7BrequestId%7D/get\">/v1/ai/audio-ldm/{requestId}</a> endpoint; for image requests, use the <a href=\"#tag/image-ai/operation/getResultByRequestId\">/v1/ai/ldm/{requestId}</a> endpoint. Make sure the `requestId` is obtained from the POST response. Processing time may vary.  - **Webhooks**: Include a `webhook_url` (and optional `webhook_key`) in your POST body to receive results asynchronously.  **Troubleshooting** - Verify the webhook URL is publicly accessible - Check that your server handles the webhook key - Ensure the request is fully processed   ### 📦 Using the SDK If you\'re building with Node.js or TypeScript, you can use our official SDK for easier integration: <a href=\"https://www.npmjs.com/package/@sureel/sdk\" target=\"_blank\">@sureel/sdk on npm</a>.  ### 🧠 Reading Temporal Attribution Results - `duration`: Length (in seconds) of each analysis window - `period`: Interval (in seconds) between segment starts  If `duration > period`, the analysis uses overlapping segments to improve accuracy. If both values are `-1`, the full song is analyzed in one pass.
+ * ### 🔐 OAuth Authentication To access the Sureel API, the following set of variables will be necessary:      {       \"auth_url\": \"https://sureel.eu.auth0.com/oauth/token\",       \"client_id\": \"<Your-Client-Id>\",       \"client_secret\": \"<Your-Client-Secret>\",       \"audience\": \"https://api.sureel.ai\"     }  Note: We provide the `client_id` and `client_secret` separately.  **Token Request Example:**      curl --request POST \\       --url https://sureel.eu.auth0.com/oauth/token \\       --header \'content-type: application/json\' \\       --data \'{         \"client_id\": \"<Your-Client-Id>\",         \"client_secret\": \"<Your-Client-Secret>\",         \"audience\": \"https://api.sureel.ai\",         \"grant_type\": \"client_credentials\"       }\'  Include the token in your API requests:      Authorization: Bearer <your_token>  **Troubleshooting** - Ensure your token hasn’t expired - Check the Authorization header format - Confirm you\'re using the correct audience   ### 📥 Getting the Request Result You can retrieve processing results in two ways:  - **Polling**:   For audio requests, retrieve results from the <a href=\"#tag/audio-ai/paths/~1v1~1ai~1audio-ldm~1%7BrequestId%7D/get\">/v1/ai/audio-ldm/{requestId}</a> endpoint; for image requests, use the <a href=\"#tag/image-ai/operation/getResultByRequestId\">/v1/ai/ldm/{requestId}</a> endpoint. Make sure the `requestId` is obtained from the POST response. Processing time may vary.  - **Webhooks**: Include a `webhook_url` (and optional `webhook_key`) in your POST body to receive results asynchronously.  **Troubleshooting** - Verify the webhook URL is publicly accessible - Check that your server handles the webhook key - Ensure the request is fully processed   ### 📦 Using the SDK If you\'re building with Node.js or TypeScript, you can use our official SDK for easier integration: <a href=\"https://www.npmjs.com/package/@sureel/sdk\" target=\"_blank\">@sureel/sdk on npm</a>.  ### 🧠 Reading Temporal Attribution Results - `duration`: Length (in seconds) of each analysis window - `period`: Interval (in seconds) between segment starts  If `duration > period`, the analysis uses overlapping segments to improve accuracy. If both values are `-1`, the full song is analyzed in one pass.
  *
  * The version of the OpenAPI document:
  *

package/models/set-filepath-file.d.ts

@@ -1,6 +1,6 @@
 /**
  * Sureel API
- * ### 🔐 OAuth Authentication To access the Sureel API, the following set of variables will be necessary:      {       \"auth_url\": \"https://dev-p48agspfw4i7fkld.eu.auth0.com/oauth/token\",       \"client_id\": \"<Your-Client-Id>\",       \"client_secret\": \"<Your-Client-Secret>\",       \"audience\": \"https://api.dev.reelx.xyz/\"     }  Note: We provide the `client_id` and `client_secret` separately.  **Token Request Example:**      curl --request POST \\       --url https://dev-p48agspfw4i7fkld.eu.auth0.com/oauth/token \\       --header \'content-type: application/json\' \\       --data \'{         \"client_id\": \"<Your-Client-Id>\",         \"client_secret\": \"<Your-Client-Secret>\",         \"audience\": \"https://api.dev.reelx.xyz/\",         \"grant_type\": \"client_credentials\"       }\'  Include the token in your API requests:      Authorization: Bearer <your_token>  **Troubleshooting** - Ensure your token hasn’t expired - Check the Authorization header format - Confirm you\'re using the correct audience   ### 📥 Getting the Request Result You can retrieve processing results in two ways:  - **Polling**:   For audio requests, retrieve results from the <a href=\"#tag/audio-ai/paths/~1v1~1ai~1audio-ldm~1%7BrequestId%7D/get\">/v1/ai/audio-ldm/{requestId}</a> endpoint; for image requests, use the <a href=\"#tag/image-ai/operation/getResultByRequestId\">/v1/ai/ldm/{requestId}</a> endpoint. Make sure the `requestId` is obtained from the POST response. Processing time may vary.  - **Webhooks**: Include a `webhook_url` (and optional `webhook_key`) in your POST body to receive results asynchronously.  **Troubleshooting** - Verify the webhook URL is publicly accessible - Check that your server handles the webhook key - Ensure the request is fully processed   ### 📦 Using the SDK If you\'re building with Node.js or TypeScript, you can use our official SDK for easier integration: <a href=\"https://www.npmjs.com/package/@sureel/sdk\" target=\"_blank\">@sureel/sdk on npm</a>.  ### 🧠 Reading Temporal Attribution Results - `duration`: Length (in seconds) of each analysis window - `period`: Interval (in seconds) between segment starts  If `duration > period`, the analysis uses overlapping segments to improve accuracy. If both values are `-1`, the full song is analyzed in one pass.
+ * ### 🔐 OAuth Authentication To access the Sureel API, the following set of variables will be necessary:      {       \"auth_url\": \"https://sureel.eu.auth0.com/oauth/token\",       \"client_id\": \"<Your-Client-Id>\",       \"client_secret\": \"<Your-Client-Secret>\",       \"audience\": \"https://api.sureel.ai\"     }  Note: We provide the `client_id` and `client_secret` separately.  **Token Request Example:**      curl --request POST \\       --url https://sureel.eu.auth0.com/oauth/token \\       --header \'content-type: application/json\' \\       --data \'{         \"client_id\": \"<Your-Client-Id>\",         \"client_secret\": \"<Your-Client-Secret>\",         \"audience\": \"https://api.sureel.ai\",         \"grant_type\": \"client_credentials\"       }\'  Include the token in your API requests:      Authorization: Bearer <your_token>  **Troubleshooting** - Ensure your token hasn’t expired - Check the Authorization header format - Confirm you\'re using the correct audience   ### 📥 Getting the Request Result You can retrieve processing results in two ways:  - **Polling**:   For audio requests, retrieve results from the <a href=\"#tag/audio-ai/paths/~1v1~1ai~1audio-ldm~1%7BrequestId%7D/get\">/v1/ai/audio-ldm/{requestId}</a> endpoint; for image requests, use the <a href=\"#tag/image-ai/operation/getResultByRequestId\">/v1/ai/ldm/{requestId}</a> endpoint. Make sure the `requestId` is obtained from the POST response. Processing time may vary.  - **Webhooks**: Include a `webhook_url` (and optional `webhook_key`) in your POST body to receive results asynchronously.  **Troubleshooting** - Verify the webhook URL is publicly accessible - Check that your server handles the webhook key - Ensure the request is fully processed   ### 📦 Using the SDK If you\'re building with Node.js or TypeScript, you can use our official SDK for easier integration: <a href=\"https://www.npmjs.com/package/@sureel/sdk\" target=\"_blank\">@sureel/sdk on npm</a>.  ### 🧠 Reading Temporal Attribution Results - `duration`: Length (in seconds) of each analysis window - `period`: Interval (in seconds) between segment starts  If `duration > period`, the analysis uses overlapping segments to improve accuracy. If both values are `-1`, the full song is analyzed in one pass.
  *
  * The version of the OpenAPI document:
  *

package/models/set-filepath-file.js

@@ -3,7 +3,7 @@
 /* eslint-disable */
 /**
  * Sureel API
- * ### 🔐 OAuth Authentication To access the Sureel API, the following set of variables will be necessary:      {       \"auth_url\": \"https://dev-p48agspfw4i7fkld.eu.auth0.com/oauth/token\",       \"client_id\": \"<Your-Client-Id>\",       \"client_secret\": \"<Your-Client-Secret>\",       \"audience\": \"https://api.dev.reelx.xyz/\"     }  Note: We provide the `client_id` and `client_secret` separately.  **Token Request Example:**      curl --request POST \\       --url https://dev-p48agspfw4i7fkld.eu.auth0.com/oauth/token \\       --header \'content-type: application/json\' \\       --data \'{         \"client_id\": \"<Your-Client-Id>\",         \"client_secret\": \"<Your-Client-Secret>\",         \"audience\": \"https://api.dev.reelx.xyz/\",         \"grant_type\": \"client_credentials\"       }\'  Include the token in your API requests:      Authorization: Bearer <your_token>  **Troubleshooting** - Ensure your token hasn’t expired - Check the Authorization header format - Confirm you\'re using the correct audience   ### 📥 Getting the Request Result You can retrieve processing results in two ways:  - **Polling**:   For audio requests, retrieve results from the <a href=\"#tag/audio-ai/paths/~1v1~1ai~1audio-ldm~1%7BrequestId%7D/get\">/v1/ai/audio-ldm/{requestId}</a> endpoint; for image requests, use the <a href=\"#tag/image-ai/operation/getResultByRequestId\">/v1/ai/ldm/{requestId}</a> endpoint. Make sure the `requestId` is obtained from the POST response. Processing time may vary.  - **Webhooks**: Include a `webhook_url` (and optional `webhook_key`) in your POST body to receive results asynchronously.  **Troubleshooting** - Verify the webhook URL is publicly accessible - Check that your server handles the webhook key - Ensure the request is fully processed   ### 📦 Using the SDK If you\'re building with Node.js or TypeScript, you can use our official SDK for easier integration: <a href=\"https://www.npmjs.com/package/@sureel/sdk\" target=\"_blank\">@sureel/sdk on npm</a>.  ### 🧠 Reading Temporal Attribution Results - `duration`: Length (in seconds) of each analysis window - `period`: Interval (in seconds) between segment starts  If `duration > period`, the analysis uses overlapping segments to improve accuracy. If both values are `-1`, the full song is analyzed in one pass.
+ * ### 🔐 OAuth Authentication To access the Sureel API, the following set of variables will be necessary:      {       \"auth_url\": \"https://sureel.eu.auth0.com/oauth/token\",       \"client_id\": \"<Your-Client-Id>\",       \"client_secret\": \"<Your-Client-Secret>\",       \"audience\": \"https://api.sureel.ai\"     }  Note: We provide the `client_id` and `client_secret` separately.  **Token Request Example:**      curl --request POST \\       --url https://sureel.eu.auth0.com/oauth/token \\       --header \'content-type: application/json\' \\       --data \'{         \"client_id\": \"<Your-Client-Id>\",         \"client_secret\": \"<Your-Client-Secret>\",         \"audience\": \"https://api.sureel.ai\",         \"grant_type\": \"client_credentials\"       }\'  Include the token in your API requests:      Authorization: Bearer <your_token>  **Troubleshooting** - Ensure your token hasn’t expired - Check the Authorization header format - Confirm you\'re using the correct audience   ### 📥 Getting the Request Result You can retrieve processing results in two ways:  - **Polling**:   For audio requests, retrieve results from the <a href=\"#tag/audio-ai/paths/~1v1~1ai~1audio-ldm~1%7BrequestId%7D/get\">/v1/ai/audio-ldm/{requestId}</a> endpoint; for image requests, use the <a href=\"#tag/image-ai/operation/getResultByRequestId\">/v1/ai/ldm/{requestId}</a> endpoint. Make sure the `requestId` is obtained from the POST response. Processing time may vary.  - **Webhooks**: Include a `webhook_url` (and optional `webhook_key`) in your POST body to receive results asynchronously.  **Troubleshooting** - Verify the webhook URL is publicly accessible - Check that your server handles the webhook key - Ensure the request is fully processed   ### 📦 Using the SDK If you\'re building with Node.js or TypeScript, you can use our official SDK for easier integration: <a href=\"https://www.npmjs.com/package/@sureel/sdk\" target=\"_blank\">@sureel/sdk on npm</a>.  ### 🧠 Reading Temporal Attribution Results - `duration`: Length (in seconds) of each analysis window - `period`: Interval (in seconds) between segment starts  If `duration > period`, the analysis uses overlapping segments to improve accuracy. If both values are `-1`, the full song is analyzed in one pass.
  *
  * The version of the OpenAPI document:
  *

package/models/set-filepaths-request-files-inner.d.ts

@@ -1,6 +1,6 @@
 /**
  * Sureel API
- * ### 🔐 OAuth Authentication To access the Sureel API, the following set of variables will be necessary:      {       \"auth_url\": \"https://dev-p48agspfw4i7fkld.eu.auth0.com/oauth/token\",       \"client_id\": \"<Your-Client-Id>\",       \"client_secret\": \"<Your-Client-Secret>\",       \"audience\": \"https://api.dev.reelx.xyz/\"     }  Note: We provide the `client_id` and `client_secret` separately.  **Token Request Example:**      curl --request POST \\       --url https://dev-p48agspfw4i7fkld.eu.auth0.com/oauth/token \\       --header \'content-type: application/json\' \\       --data \'{         \"client_id\": \"<Your-Client-Id>\",         \"client_secret\": \"<Your-Client-Secret>\",         \"audience\": \"https://api.dev.reelx.xyz/\",         \"grant_type\": \"client_credentials\"       }\'  Include the token in your API requests:      Authorization: Bearer <your_token>  **Troubleshooting** - Ensure your token hasn’t expired - Check the Authorization header format - Confirm you\'re using the correct audience   ### 📥 Getting the Request Result You can retrieve processing results in two ways:  - **Polling**:   For audio requests, retrieve results from the <a href=\"#tag/audio-ai/paths/~1v1~1ai~1audio-ldm~1%7BrequestId%7D/get\">/v1/ai/audio-ldm/{requestId}</a> endpoint; for image requests, use the <a href=\"#tag/image-ai/operation/getResultByRequestId\">/v1/ai/ldm/{requestId}</a> endpoint. Make sure the `requestId` is obtained from the POST response. Processing time may vary.  - **Webhooks**: Include a `webhook_url` (and optional `webhook_key`) in your POST body to receive results asynchronously.  **Troubleshooting** - Verify the webhook URL is publicly accessible - Check that your server handles the webhook key - Ensure the request is fully processed   ### 📦 Using the SDK If you\'re building with Node.js or TypeScript, you can use our official SDK for easier integration: <a href=\"https://www.npmjs.com/package/@sureel/sdk\" target=\"_blank\">@sureel/sdk on npm</a>.  ### 🧠 Reading Temporal Attribution Results - `duration`: Length (in seconds) of each analysis window - `period`: Interval (in seconds) between segment starts  If `duration > period`, the analysis uses overlapping segments to improve accuracy. If both values are `-1`, the full song is analyzed in one pass.
+ * ### 🔐 OAuth Authentication To access the Sureel API, the following set of variables will be necessary:      {       \"auth_url\": \"https://sureel.eu.auth0.com/oauth/token\",       \"client_id\": \"<Your-Client-Id>\",       \"client_secret\": \"<Your-Client-Secret>\",       \"audience\": \"https://api.sureel.ai\"     }  Note: We provide the `client_id` and `client_secret` separately.  **Token Request Example:**      curl --request POST \\       --url https://sureel.eu.auth0.com/oauth/token \\       --header \'content-type: application/json\' \\       --data \'{         \"client_id\": \"<Your-Client-Id>\",         \"client_secret\": \"<Your-Client-Secret>\",         \"audience\": \"https://api.sureel.ai\",         \"grant_type\": \"client_credentials\"       }\'  Include the token in your API requests:      Authorization: Bearer <your_token>  **Troubleshooting** - Ensure your token hasn’t expired - Check the Authorization header format - Confirm you\'re using the correct audience   ### 📥 Getting the Request Result You can retrieve processing results in two ways:  - **Polling**:   For audio requests, retrieve results from the <a href=\"#tag/audio-ai/paths/~1v1~1ai~1audio-ldm~1%7BrequestId%7D/get\">/v1/ai/audio-ldm/{requestId}</a> endpoint; for image requests, use the <a href=\"#tag/image-ai/operation/getResultByRequestId\">/v1/ai/ldm/{requestId}</a> endpoint. Make sure the `requestId` is obtained from the POST response. Processing time may vary.  - **Webhooks**: Include a `webhook_url` (and optional `webhook_key`) in your POST body to receive results asynchronously.  **Troubleshooting** - Verify the webhook URL is publicly accessible - Check that your server handles the webhook key - Ensure the request is fully processed   ### 📦 Using the SDK If you\'re building with Node.js or TypeScript, you can use our official SDK for easier integration: <a href=\"https://www.npmjs.com/package/@sureel/sdk\" target=\"_blank\">@sureel/sdk on npm</a>.  ### 🧠 Reading Temporal Attribution Results - `duration`: Length (in seconds) of each analysis window - `period`: Interval (in seconds) between segment starts  If `duration > period`, the analysis uses overlapping segments to improve accuracy. If both values are `-1`, the full song is analyzed in one pass.
  *
  * The version of the OpenAPI document:
  *

package/models/set-filepaths-request-files-inner.js

@@ -3,7 +3,7 @@
 /* eslint-disable */
 /**
  * Sureel API
- * ### 🔐 OAuth Authentication To access the Sureel API, the following set of variables will be necessary:      {       \"auth_url\": \"https://dev-p48agspfw4i7fkld.eu.auth0.com/oauth/token\",       \"client_id\": \"<Your-Client-Id>\",       \"client_secret\": \"<Your-Client-Secret>\",       \"audience\": \"https://api.dev.reelx.xyz/\"     }  Note: We provide the `client_id` and `client_secret` separately.  **Token Request Example:**      curl --request POST \\       --url https://dev-p48agspfw4i7fkld.eu.auth0.com/oauth/token \\       --header \'content-type: application/json\' \\       --data \'{         \"client_id\": \"<Your-Client-Id>\",         \"client_secret\": \"<Your-Client-Secret>\",         \"audience\": \"https://api.dev.reelx.xyz/\",         \"grant_type\": \"client_credentials\"       }\'  Include the token in your API requests:      Authorization: Bearer <your_token>  **Troubleshooting** - Ensure your token hasn’t expired - Check the Authorization header format - Confirm you\'re using the correct audience   ### 📥 Getting the Request Result You can retrieve processing results in two ways:  - **Polling**:   For audio requests, retrieve results from the <a href=\"#tag/audio-ai/paths/~1v1~1ai~1audio-ldm~1%7BrequestId%7D/get\">/v1/ai/audio-ldm/{requestId}</a> endpoint; for image requests, use the <a href=\"#tag/image-ai/operation/getResultByRequestId\">/v1/ai/ldm/{requestId}</a> endpoint. Make sure the `requestId` is obtained from the POST response. Processing time may vary.  - **Webhooks**: Include a `webhook_url` (and optional `webhook_key`) in your POST body to receive results asynchronously.  **Troubleshooting** - Verify the webhook URL is publicly accessible - Check that your server handles the webhook key - Ensure the request is fully processed   ### 📦 Using the SDK If you\'re building with Node.js or TypeScript, you can use our official SDK for easier integration: <a href=\"https://www.npmjs.com/package/@sureel/sdk\" target=\"_blank\">@sureel/sdk on npm</a>.  ### 🧠 Reading Temporal Attribution Results - `duration`: Length (in seconds) of each analysis window - `period`: Interval (in seconds) between segment starts  If `duration > period`, the analysis uses overlapping segments to improve accuracy. If both values are `-1`, the full song is analyzed in one pass.
+ * ### 🔐 OAuth Authentication To access the Sureel API, the following set of variables will be necessary:      {       \"auth_url\": \"https://sureel.eu.auth0.com/oauth/token\",       \"client_id\": \"<Your-Client-Id>\",       \"client_secret\": \"<Your-Client-Secret>\",       \"audience\": \"https://api.sureel.ai\"     }  Note: We provide the `client_id` and `client_secret` separately.  **Token Request Example:**      curl --request POST \\       --url https://sureel.eu.auth0.com/oauth/token \\       --header \'content-type: application/json\' \\       --data \'{         \"client_id\": \"<Your-Client-Id>\",         \"client_secret\": \"<Your-Client-Secret>\",         \"audience\": \"https://api.sureel.ai\",         \"grant_type\": \"client_credentials\"       }\'  Include the token in your API requests:      Authorization: Bearer <your_token>  **Troubleshooting** - Ensure your token hasn’t expired - Check the Authorization header format - Confirm you\'re using the correct audience   ### 📥 Getting the Request Result You can retrieve processing results in two ways:  - **Polling**:   For audio requests, retrieve results from the <a href=\"#tag/audio-ai/paths/~1v1~1ai~1audio-ldm~1%7BrequestId%7D/get\">/v1/ai/audio-ldm/{requestId}</a> endpoint; for image requests, use the <a href=\"#tag/image-ai/operation/getResultByRequestId\">/v1/ai/ldm/{requestId}</a> endpoint. Make sure the `requestId` is obtained from the POST response. Processing time may vary.  - **Webhooks**: Include a `webhook_url` (and optional `webhook_key`) in your POST body to receive results asynchronously.  **Troubleshooting** - Verify the webhook URL is publicly accessible - Check that your server handles the webhook key - Ensure the request is fully processed   ### 📦 Using the SDK If you\'re building with Node.js or TypeScript, you can use our official SDK for easier integration: <a href=\"https://www.npmjs.com/package/@sureel/sdk\" target=\"_blank\">@sureel/sdk on npm</a>.  ### 🧠 Reading Temporal Attribution Results - `duration`: Length (in seconds) of each analysis window - `period`: Interval (in seconds) between segment starts  If `duration > period`, the analysis uses overlapping segments to improve accuracy. If both values are `-1`, the full song is analyzed in one pass.
  *
  * The version of the OpenAPI document:
  *

package/models/set-filepaths-request.d.ts

@@ -1,6 +1,6 @@
 /**
  * Sureel API
- * ### 🔐 OAuth Authentication To access the Sureel API, the following set of variables will be necessary:      {       \"auth_url\": \"https://dev-p48agspfw4i7fkld.eu.auth0.com/oauth/token\",       \"client_id\": \"<Your-Client-Id>\",       \"client_secret\": \"<Your-Client-Secret>\",       \"audience\": \"https://api.dev.reelx.xyz/\"     }  Note: We provide the `client_id` and `client_secret` separately.  **Token Request Example:**      curl --request POST \\       --url https://dev-p48agspfw4i7fkld.eu.auth0.com/oauth/token \\       --header \'content-type: application/json\' \\       --data \'{         \"client_id\": \"<Your-Client-Id>\",         \"client_secret\": \"<Your-Client-Secret>\",         \"audience\": \"https://api.dev.reelx.xyz/\",         \"grant_type\": \"client_credentials\"       }\'  Include the token in your API requests:      Authorization: Bearer <your_token>  **Troubleshooting** - Ensure your token hasn’t expired - Check the Authorization header format - Confirm you\'re using the correct audience   ### 📥 Getting the Request Result You can retrieve processing results in two ways:  - **Polling**:   For audio requests, retrieve results from the <a href=\"#tag/audio-ai/paths/~1v1~1ai~1audio-ldm~1%7BrequestId%7D/get\">/v1/ai/audio-ldm/{requestId}</a> endpoint; for image requests, use the <a href=\"#tag/image-ai/operation/getResultByRequestId\">/v1/ai/ldm/{requestId}</a> endpoint. Make sure the `requestId` is obtained from the POST response. Processing time may vary.  - **Webhooks**: Include a `webhook_url` (and optional `webhook_key`) in your POST body to receive results asynchronously.  **Troubleshooting** - Verify the webhook URL is publicly accessible - Check that your server handles the webhook key - Ensure the request is fully processed   ### 📦 Using the SDK If you\'re building with Node.js or TypeScript, you can use our official SDK for easier integration: <a href=\"https://www.npmjs.com/package/@sureel/sdk\" target=\"_blank\">@sureel/sdk on npm</a>.  ### 🧠 Reading Temporal Attribution Results - `duration`: Length (in seconds) of each analysis window - `period`: Interval (in seconds) between segment starts  If `duration > period`, the analysis uses overlapping segments to improve accuracy. If both values are `-1`, the full song is analyzed in one pass.
+ * ### 🔐 OAuth Authentication To access the Sureel API, the following set of variables will be necessary:      {       \"auth_url\": \"https://sureel.eu.auth0.com/oauth/token\",       \"client_id\": \"<Your-Client-Id>\",       \"client_secret\": \"<Your-Client-Secret>\",       \"audience\": \"https://api.sureel.ai\"     }  Note: We provide the `client_id` and `client_secret` separately.  **Token Request Example:**      curl --request POST \\       --url https://sureel.eu.auth0.com/oauth/token \\       --header \'content-type: application/json\' \\       --data \'{         \"client_id\": \"<Your-Client-Id>\",         \"client_secret\": \"<Your-Client-Secret>\",         \"audience\": \"https://api.sureel.ai\",         \"grant_type\": \"client_credentials\"       }\'  Include the token in your API requests:      Authorization: Bearer <your_token>  **Troubleshooting** - Ensure your token hasn’t expired - Check the Authorization header format - Confirm you\'re using the correct audience   ### 📥 Getting the Request Result You can retrieve processing results in two ways:  - **Polling**:   For audio requests, retrieve results from the <a href=\"#tag/audio-ai/paths/~1v1~1ai~1audio-ldm~1%7BrequestId%7D/get\">/v1/ai/audio-ldm/{requestId}</a> endpoint; for image requests, use the <a href=\"#tag/image-ai/operation/getResultByRequestId\">/v1/ai/ldm/{requestId}</a> endpoint. Make sure the `requestId` is obtained from the POST response. Processing time may vary.  - **Webhooks**: Include a `webhook_url` (and optional `webhook_key`) in your POST body to receive results asynchronously.  **Troubleshooting** - Verify the webhook URL is publicly accessible - Check that your server handles the webhook key - Ensure the request is fully processed   ### 📦 Using the SDK If you\'re building with Node.js or TypeScript, you can use our official SDK for easier integration: <a href=\"https://www.npmjs.com/package/@sureel/sdk\" target=\"_blank\">@sureel/sdk on npm</a>.  ### 🧠 Reading Temporal Attribution Results - `duration`: Length (in seconds) of each analysis window - `period`: Interval (in seconds) between segment starts  If `duration > period`, the analysis uses overlapping segments to improve accuracy. If both values are `-1`, the full song is analyzed in one pass.
  *
  * The version of the OpenAPI document:
  *

package/models/set-filepaths-request.js

@@ -3,7 +3,7 @@
 /* eslint-disable */
 /**
  * Sureel API
- * ### 🔐 OAuth Authentication To access the Sureel API, the following set of variables will be necessary:      {       \"auth_url\": \"https://dev-p48agspfw4i7fkld.eu.auth0.com/oauth/token\",       \"client_id\": \"<Your-Client-Id>\",       \"client_secret\": \"<Your-Client-Secret>\",       \"audience\": \"https://api.dev.reelx.xyz/\"     }  Note: We provide the `client_id` and `client_secret` separately.  **Token Request Example:**      curl --request POST \\       --url https://dev-p48agspfw4i7fkld.eu.auth0.com/oauth/token \\       --header \'content-type: application/json\' \\       --data \'{         \"client_id\": \"<Your-Client-Id>\",         \"client_secret\": \"<Your-Client-Secret>\",         \"audience\": \"https://api.dev.reelx.xyz/\",         \"grant_type\": \"client_credentials\"       }\'  Include the token in your API requests:      Authorization: Bearer <your_token>  **Troubleshooting** - Ensure your token hasn’t expired - Check the Authorization header format - Confirm you\'re using the correct audience   ### 📥 Getting the Request Result You can retrieve processing results in two ways:  - **Polling**:   For audio requests, retrieve results from the <a href=\"#tag/audio-ai/paths/~1v1~1ai~1audio-ldm~1%7BrequestId%7D/get\">/v1/ai/audio-ldm/{requestId}</a> endpoint; for image requests, use the <a href=\"#tag/image-ai/operation/getResultByRequestId\">/v1/ai/ldm/{requestId}</a> endpoint. Make sure the `requestId` is obtained from the POST response. Processing time may vary.  - **Webhooks**: Include a `webhook_url` (and optional `webhook_key`) in your POST body to receive results asynchronously.  **Troubleshooting** - Verify the webhook URL is publicly accessible - Check that your server handles the webhook key - Ensure the request is fully processed   ### 📦 Using the SDK If you\'re building with Node.js or TypeScript, you can use our official SDK for easier integration: <a href=\"https://www.npmjs.com/package/@sureel/sdk\" target=\"_blank\">@sureel/sdk on npm</a>.  ### 🧠 Reading Temporal Attribution Results - `duration`: Length (in seconds) of each analysis window - `period`: Interval (in seconds) between segment starts  If `duration > period`, the analysis uses overlapping segments to improve accuracy. If both values are `-1`, the full song is analyzed in one pass.
+ * ### 🔐 OAuth Authentication To access the Sureel API, the following set of variables will be necessary:      {       \"auth_url\": \"https://sureel.eu.auth0.com/oauth/token\",       \"client_id\": \"<Your-Client-Id>\",       \"client_secret\": \"<Your-Client-Secret>\",       \"audience\": \"https://api.sureel.ai\"     }  Note: We provide the `client_id` and `client_secret` separately.  **Token Request Example:**      curl --request POST \\       --url https://sureel.eu.auth0.com/oauth/token \\       --header \'content-type: application/json\' \\       --data \'{         \"client_id\": \"<Your-Client-Id>\",         \"client_secret\": \"<Your-Client-Secret>\",         \"audience\": \"https://api.sureel.ai\",         \"grant_type\": \"client_credentials\"       }\'  Include the token in your API requests:      Authorization: Bearer <your_token>  **Troubleshooting** - Ensure your token hasn’t expired - Check the Authorization header format - Confirm you\'re using the correct audience   ### 📥 Getting the Request Result You can retrieve processing results in two ways:  - **Polling**:   For audio requests, retrieve results from the <a href=\"#tag/audio-ai/paths/~1v1~1ai~1audio-ldm~1%7BrequestId%7D/get\">/v1/ai/audio-ldm/{requestId}</a> endpoint; for image requests, use the <a href=\"#tag/image-ai/operation/getResultByRequestId\">/v1/ai/ldm/{requestId}</a> endpoint. Make sure the `requestId` is obtained from the POST response. Processing time may vary.  - **Webhooks**: Include a `webhook_url` (and optional `webhook_key`) in your POST body to receive results asynchronously.  **Troubleshooting** - Verify the webhook URL is publicly accessible - Check that your server handles the webhook key - Ensure the request is fully processed   ### 📦 Using the SDK If you\'re building with Node.js or TypeScript, you can use our official SDK for easier integration: <a href=\"https://www.npmjs.com/package/@sureel/sdk\" target=\"_blank\">@sureel/sdk on npm</a>.  ### 🧠 Reading Temporal Attribution Results - `duration`: Length (in seconds) of each analysis window - `period`: Interval (in seconds) between segment starts  If `duration > period`, the analysis uses overlapping segments to improve accuracy. If both values are `-1`, the full song is analyzed in one pass.
  *
  * The version of the OpenAPI document:
  *

package/models/signed-url-or-null.d.ts

@@ -1,6 +1,6 @@
 /**
  * Sureel API
- * ### 🔐 OAuth Authentication To access the Sureel API, the following set of variables will be necessary:      {       \"auth_url\": \"https://dev-p48agspfw4i7fkld.eu.auth0.com/oauth/token\",       \"client_id\": \"<Your-Client-Id>\",       \"client_secret\": \"<Your-Client-Secret>\",       \"audience\": \"https://api.dev.reelx.xyz/\"     }  Note: We provide the `client_id` and `client_secret` separately.  **Token Request Example:**      curl --request POST \\       --url https://dev-p48agspfw4i7fkld.eu.auth0.com/oauth/token \\       --header \'content-type: application/json\' \\       --data \'{         \"client_id\": \"<Your-Client-Id>\",         \"client_secret\": \"<Your-Client-Secret>\",         \"audience\": \"https://api.dev.reelx.xyz/\",         \"grant_type\": \"client_credentials\"       }\'  Include the token in your API requests:      Authorization: Bearer <your_token>  **Troubleshooting** - Ensure your token hasn’t expired - Check the Authorization header format - Confirm you\'re using the correct audience   ### 📥 Getting the Request Result You can retrieve processing results in two ways:  - **Polling**:   For audio requests, retrieve results from the <a href=\"#tag/audio-ai/paths/~1v1~1ai~1audio-ldm~1%7BrequestId%7D/get\">/v1/ai/audio-ldm/{requestId}</a> endpoint; for image requests, use the <a href=\"#tag/image-ai/operation/getResultByRequestId\">/v1/ai/ldm/{requestId}</a> endpoint. Make sure the `requestId` is obtained from the POST response. Processing time may vary.  - **Webhooks**: Include a `webhook_url` (and optional `webhook_key`) in your POST body to receive results asynchronously.  **Troubleshooting** - Verify the webhook URL is publicly accessible - Check that your server handles the webhook key - Ensure the request is fully processed   ### 📦 Using the SDK If you\'re building with Node.js or TypeScript, you can use our official SDK for easier integration: <a href=\"https://www.npmjs.com/package/@sureel/sdk\" target=\"_blank\">@sureel/sdk on npm</a>.  ### 🧠 Reading Temporal Attribution Results - `duration`: Length (in seconds) of each analysis window - `period`: Interval (in seconds) between segment starts  If `duration > period`, the analysis uses overlapping segments to improve accuracy. If both values are `-1`, the full song is analyzed in one pass.
+ * ### 🔐 OAuth Authentication To access the Sureel API, the following set of variables will be necessary:      {       \"auth_url\": \"https://sureel.eu.auth0.com/oauth/token\",       \"client_id\": \"<Your-Client-Id>\",       \"client_secret\": \"<Your-Client-Secret>\",       \"audience\": \"https://api.sureel.ai\"     }  Note: We provide the `client_id` and `client_secret` separately.  **Token Request Example:**      curl --request POST \\       --url https://sureel.eu.auth0.com/oauth/token \\       --header \'content-type: application/json\' \\       --data \'{         \"client_id\": \"<Your-Client-Id>\",         \"client_secret\": \"<Your-Client-Secret>\",         \"audience\": \"https://api.sureel.ai\",         \"grant_type\": \"client_credentials\"       }\'  Include the token in your API requests:      Authorization: Bearer <your_token>  **Troubleshooting** - Ensure your token hasn’t expired - Check the Authorization header format - Confirm you\'re using the correct audience   ### 📥 Getting the Request Result You can retrieve processing results in two ways:  - **Polling**:   For audio requests, retrieve results from the <a href=\"#tag/audio-ai/paths/~1v1~1ai~1audio-ldm~1%7BrequestId%7D/get\">/v1/ai/audio-ldm/{requestId}</a> endpoint; for image requests, use the <a href=\"#tag/image-ai/operation/getResultByRequestId\">/v1/ai/ldm/{requestId}</a> endpoint. Make sure the `requestId` is obtained from the POST response. Processing time may vary.  - **Webhooks**: Include a `webhook_url` (and optional `webhook_key`) in your POST body to receive results asynchronously.  **Troubleshooting** - Verify the webhook URL is publicly accessible - Check that your server handles the webhook key - Ensure the request is fully processed   ### 📦 Using the SDK If you\'re building with Node.js or TypeScript, you can use our official SDK for easier integration: <a href=\"https://www.npmjs.com/package/@sureel/sdk\" target=\"_blank\">@sureel/sdk on npm</a>.  ### 🧠 Reading Temporal Attribution Results - `duration`: Length (in seconds) of each analysis window - `period`: Interval (in seconds) between segment starts  If `duration > period`, the analysis uses overlapping segments to improve accuracy. If both values are `-1`, the full song is analyzed in one pass.
  *
  * The version of the OpenAPI document:
  *

package/models/signed-url-or-null.js

@@ -3,7 +3,7 @@
 /* eslint-disable */
 /**
  * Sureel API
- * ### 🔐 OAuth Authentication To access the Sureel API, the following set of variables will be necessary:      {       \"auth_url\": \"https://dev-p48agspfw4i7fkld.eu.auth0.com/oauth/token\",       \"client_id\": \"<Your-Client-Id>\",       \"client_secret\": \"<Your-Client-Secret>\",       \"audience\": \"https://api.dev.reelx.xyz/\"     }  Note: We provide the `client_id` and `client_secret` separately.  **Token Request Example:**      curl --request POST \\       --url https://dev-p48agspfw4i7fkld.eu.auth0.com/oauth/token \\       --header \'content-type: application/json\' \\       --data \'{         \"client_id\": \"<Your-Client-Id>\",         \"client_secret\": \"<Your-Client-Secret>\",         \"audience\": \"https://api.dev.reelx.xyz/\",         \"grant_type\": \"client_credentials\"       }\'  Include the token in your API requests:      Authorization: Bearer <your_token>  **Troubleshooting** - Ensure your token hasn’t expired - Check the Authorization header format - Confirm you\'re using the correct audience   ### 📥 Getting the Request Result You can retrieve processing results in two ways:  - **Polling**:   For audio requests, retrieve results from the <a href=\"#tag/audio-ai/paths/~1v1~1ai~1audio-ldm~1%7BrequestId%7D/get\">/v1/ai/audio-ldm/{requestId}</a> endpoint; for image requests, use the <a href=\"#tag/image-ai/operation/getResultByRequestId\">/v1/ai/ldm/{requestId}</a> endpoint. Make sure the `requestId` is obtained from the POST response. Processing time may vary.  - **Webhooks**: Include a `webhook_url` (and optional `webhook_key`) in your POST body to receive results asynchronously.  **Troubleshooting** - Verify the webhook URL is publicly accessible - Check that your server handles the webhook key - Ensure the request is fully processed   ### 📦 Using the SDK If you\'re building with Node.js or TypeScript, you can use our official SDK for easier integration: <a href=\"https://www.npmjs.com/package/@sureel/sdk\" target=\"_blank\">@sureel/sdk on npm</a>.  ### 🧠 Reading Temporal Attribution Results - `duration`: Length (in seconds) of each analysis window - `period`: Interval (in seconds) between segment starts  If `duration > period`, the analysis uses overlapping segments to improve accuracy. If both values are `-1`, the full song is analyzed in one pass.
+ * ### 🔐 OAuth Authentication To access the Sureel API, the following set of variables will be necessary:      {       \"auth_url\": \"https://sureel.eu.auth0.com/oauth/token\",       \"client_id\": \"<Your-Client-Id>\",       \"client_secret\": \"<Your-Client-Secret>\",       \"audience\": \"https://api.sureel.ai\"     }  Note: We provide the `client_id` and `client_secret` separately.  **Token Request Example:**      curl --request POST \\       --url https://sureel.eu.auth0.com/oauth/token \\       --header \'content-type: application/json\' \\       --data \'{         \"client_id\": \"<Your-Client-Id>\",         \"client_secret\": \"<Your-Client-Secret>\",         \"audience\": \"https://api.sureel.ai\",         \"grant_type\": \"client_credentials\"       }\'  Include the token in your API requests:      Authorization: Bearer <your_token>  **Troubleshooting** - Ensure your token hasn’t expired - Check the Authorization header format - Confirm you\'re using the correct audience   ### 📥 Getting the Request Result You can retrieve processing results in two ways:  - **Polling**:   For audio requests, retrieve results from the <a href=\"#tag/audio-ai/paths/~1v1~1ai~1audio-ldm~1%7BrequestId%7D/get\">/v1/ai/audio-ldm/{requestId}</a> endpoint; for image requests, use the <a href=\"#tag/image-ai/operation/getResultByRequestId\">/v1/ai/ldm/{requestId}</a> endpoint. Make sure the `requestId` is obtained from the POST response. Processing time may vary.  - **Webhooks**: Include a `webhook_url` (and optional `webhook_key`) in your POST body to receive results asynchronously.  **Troubleshooting** - Verify the webhook URL is publicly accessible - Check that your server handles the webhook key - Ensure the request is fully processed   ### 📦 Using the SDK If you\'re building with Node.js or TypeScript, you can use our official SDK for easier integration: <a href=\"https://www.npmjs.com/package/@sureel/sdk\" target=\"_blank\">@sureel/sdk on npm</a>.  ### 🧠 Reading Temporal Attribution Results - `duration`: Length (in seconds) of each analysis window - `period`: Interval (in seconds) between segment starts  If `duration > period`, the analysis uses overlapping segments to improve accuracy. If both values are `-1`, the full song is analyzed in one pass.
  *
  * The version of the OpenAPI document:
  *

package/models/similar-audio-file-with-metrics.d.ts

@@ -1,6 +1,6 @@
 /**
  * Sureel API
- * ### 🔐 OAuth Authentication To access the Sureel API, the following set of variables will be necessary:      {       \"auth_url\": \"https://dev-p48agspfw4i7fkld.eu.auth0.com/oauth/token\",       \"client_id\": \"<Your-Client-Id>\",       \"client_secret\": \"<Your-Client-Secret>\",       \"audience\": \"https://api.dev.reelx.xyz/\"     }  Note: We provide the `client_id` and `client_secret` separately.  **Token Request Example:**      curl --request POST \\       --url https://dev-p48agspfw4i7fkld.eu.auth0.com/oauth/token \\       --header \'content-type: application/json\' \\       --data \'{         \"client_id\": \"<Your-Client-Id>\",         \"client_secret\": \"<Your-Client-Secret>\",         \"audience\": \"https://api.dev.reelx.xyz/\",         \"grant_type\": \"client_credentials\"       }\'  Include the token in your API requests:      Authorization: Bearer <your_token>  **Troubleshooting** - Ensure your token hasn’t expired - Check the Authorization header format - Confirm you\'re using the correct audience   ### 📥 Getting the Request Result You can retrieve processing results in two ways:  - **Polling**:   For audio requests, retrieve results from the <a href=\"#tag/audio-ai/paths/~1v1~1ai~1audio-ldm~1%7BrequestId%7D/get\">/v1/ai/audio-ldm/{requestId}</a> endpoint; for image requests, use the <a href=\"#tag/image-ai/operation/getResultByRequestId\">/v1/ai/ldm/{requestId}</a> endpoint. Make sure the `requestId` is obtained from the POST response. Processing time may vary.  - **Webhooks**: Include a `webhook_url` (and optional `webhook_key`) in your POST body to receive results asynchronously.  **Troubleshooting** - Verify the webhook URL is publicly accessible - Check that your server handles the webhook key - Ensure the request is fully processed   ### 📦 Using the SDK If you\'re building with Node.js or TypeScript, you can use our official SDK for easier integration: <a href=\"https://www.npmjs.com/package/@sureel/sdk\" target=\"_blank\">@sureel/sdk on npm</a>.  ### 🧠 Reading Temporal Attribution Results - `duration`: Length (in seconds) of each analysis window - `period`: Interval (in seconds) between segment starts  If `duration > period`, the analysis uses overlapping segments to improve accuracy. If both values are `-1`, the full song is analyzed in one pass.
+ * ### 🔐 OAuth Authentication To access the Sureel API, the following set of variables will be necessary:      {       \"auth_url\": \"https://sureel.eu.auth0.com/oauth/token\",       \"client_id\": \"<Your-Client-Id>\",       \"client_secret\": \"<Your-Client-Secret>\",       \"audience\": \"https://api.sureel.ai\"     }  Note: We provide the `client_id` and `client_secret` separately.  **Token Request Example:**      curl --request POST \\       --url https://sureel.eu.auth0.com/oauth/token \\       --header \'content-type: application/json\' \\       --data \'{         \"client_id\": \"<Your-Client-Id>\",         \"client_secret\": \"<Your-Client-Secret>\",         \"audience\": \"https://api.sureel.ai\",         \"grant_type\": \"client_credentials\"       }\'  Include the token in your API requests:      Authorization: Bearer <your_token>  **Troubleshooting** - Ensure your token hasn’t expired - Check the Authorization header format - Confirm you\'re using the correct audience   ### 📥 Getting the Request Result You can retrieve processing results in two ways:  - **Polling**:   For audio requests, retrieve results from the <a href=\"#tag/audio-ai/paths/~1v1~1ai~1audio-ldm~1%7BrequestId%7D/get\">/v1/ai/audio-ldm/{requestId}</a> endpoint; for image requests, use the <a href=\"#tag/image-ai/operation/getResultByRequestId\">/v1/ai/ldm/{requestId}</a> endpoint. Make sure the `requestId` is obtained from the POST response. Processing time may vary.  - **Webhooks**: Include a `webhook_url` (and optional `webhook_key`) in your POST body to receive results asynchronously.  **Troubleshooting** - Verify the webhook URL is publicly accessible - Check that your server handles the webhook key - Ensure the request is fully processed   ### 📦 Using the SDK If you\'re building with Node.js or TypeScript, you can use our official SDK for easier integration: <a href=\"https://www.npmjs.com/package/@sureel/sdk\" target=\"_blank\">@sureel/sdk on npm</a>.  ### 🧠 Reading Temporal Attribution Results - `duration`: Length (in seconds) of each analysis window - `period`: Interval (in seconds) between segment starts  If `duration > period`, the analysis uses overlapping segments to improve accuracy. If both values are `-1`, the full song is analyzed in one pass.
  *
  * The version of the OpenAPI document:
  *
@@ -87,5 +87,11 @@ export interface SimilarAudioFileWithMetrics {
      * @memberof SimilarAudioFileWithMetrics
      */
     track_name?: string;
+    /**
+     *
+     * @type {string}
+     * @memberof SimilarAudioFileWithMetrics
+     */
+    label_name?: string;
 }
 //# sourceMappingURL=similar-audio-file-with-metrics.d.ts.map

package/models/similar-audio-file-with-metrics.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"similar-audio-file-with-metrics.d.ts","sourceRoot":"","sources":["../../src/models/similar-audio-file-with-metrics.ts"],"names":[],"mappings":"AAEA;;;;;;;;;;GAUG;AAEH;;;;GAIG;AACH,MAAM,WAAW,2BAA2B;IACxC;;;;OAIG;IACH,sBAAsB,EAAE,KAAK,CAAC,MAAM,CAAC,CAAA;IACrC;;;;OAIG;IACH,iBAAiB,CAAC,EAAE,KAAK,CAAC,MAAM,CAAC,CAAA;IACjC;;;;OAIG;IACH,eAAe,EAAE,KAAK,CAAC,MAAM,CAAC,CAAA;IAC9B;;;;OAIG;IACH,mBAAmB,EAAE,KAAK,CAAC,MAAM,CAAC,CAAA;IAClC;;;;OAIG;IACH,KAAK,CAAC,EAAE,MAAM,CAAA;IACd;;;;OAIG;IACH,QAAQ,CAAC,EAAE,MAAM,CAAA;IACjB;;;;OAIG;IACH,UAAU,CAAC,EAAE,MAAM,CAAA;IACnB;;;;OAIG;IACH,cAAc,EAAE,OAAO,CAAA;IACvB;;;;OAIG;IACH,QAAQ,CAAC,EAAE,MAAM,CAAA;IACjB;;;;OAIG;IACH,eAAe,CAAC,EAAE,MAAM,CAAA;IACxB;;;;OAIG;IACH,eAAe,CAAC,EAAE,MAAM,CAAA;IACxB;;;;OAIG;IACH,UAAU,CAAC,EAAE,MAAM,CAAA;CACtB"}
+{"version":3,"file":"similar-audio-file-with-metrics.d.ts","sourceRoot":"","sources":["../../src/models/similar-audio-file-with-metrics.ts"],"names":[],"mappings":"AAEA;;;;;;;;;;GAUG;AAEH;;;;GAIG;AACH,MAAM,WAAW,2BAA2B;IACxC;;;;OAIG;IACH,sBAAsB,EAAE,KAAK,CAAC,MAAM,CAAC,CAAA;IACrC;;;;OAIG;IACH,iBAAiB,CAAC,EAAE,KAAK,CAAC,MAAM,CAAC,CAAA;IACjC;;;;OAIG;IACH,eAAe,EAAE,KAAK,CAAC,MAAM,CAAC,CAAA;IAC9B;;;;OAIG;IACH,mBAAmB,EAAE,KAAK,CAAC,MAAM,CAAC,CAAA;IAClC;;;;OAIG;IACH,KAAK,CAAC,EAAE,MAAM,CAAA;IACd;;;;OAIG;IACH,QAAQ,CAAC,EAAE,MAAM,CAAA;IACjB;;;;OAIG;IACH,UAAU,CAAC,EAAE,MAAM,CAAA;IACnB;;;;OAIG;IACH,cAAc,EAAE,OAAO,CAAA;IACvB;;;;OAIG;IACH,QAAQ,CAAC,EAAE,MAAM,CAAA;IACjB;;;;OAIG;IACH,eAAe,CAAC,EAAE,MAAM,CAAA;IACxB;;;;OAIG;IACH,eAAe,CAAC,EAAE,MAAM,CAAA;IACxB;;;;OAIG;IACH,UAAU,CAAC,EAAE,MAAM,CAAA;IACnB;;;;OAIG;IACH,UAAU,CAAC,EAAE,MAAM,CAAA;CACtB"}

package/models/similar-audio-file-with-metrics.js

@@ -3,7 +3,7 @@
 /* eslint-disable */
 /**
  * Sureel API
- * ### 🔐 OAuth Authentication To access the Sureel API, the following set of variables will be necessary:      {       \"auth_url\": \"https://dev-p48agspfw4i7fkld.eu.auth0.com/oauth/token\",       \"client_id\": \"<Your-Client-Id>\",       \"client_secret\": \"<Your-Client-Secret>\",       \"audience\": \"https://api.dev.reelx.xyz/\"     }  Note: We provide the `client_id` and `client_secret` separately.  **Token Request Example:**      curl --request POST \\       --url https://dev-p48agspfw4i7fkld.eu.auth0.com/oauth/token \\       --header \'content-type: application/json\' \\       --data \'{         \"client_id\": \"<Your-Client-Id>\",         \"client_secret\": \"<Your-Client-Secret>\",         \"audience\": \"https://api.dev.reelx.xyz/\",         \"grant_type\": \"client_credentials\"       }\'  Include the token in your API requests:      Authorization: Bearer <your_token>  **Troubleshooting** - Ensure your token hasn’t expired - Check the Authorization header format - Confirm you\'re using the correct audience   ### 📥 Getting the Request Result You can retrieve processing results in two ways:  - **Polling**:   For audio requests, retrieve results from the <a href=\"#tag/audio-ai/paths/~1v1~1ai~1audio-ldm~1%7BrequestId%7D/get\">/v1/ai/audio-ldm/{requestId}</a> endpoint; for image requests, use the <a href=\"#tag/image-ai/operation/getResultByRequestId\">/v1/ai/ldm/{requestId}</a> endpoint. Make sure the `requestId` is obtained from the POST response. Processing time may vary.  - **Webhooks**: Include a `webhook_url` (and optional `webhook_key`) in your POST body to receive results asynchronously.  **Troubleshooting** - Verify the webhook URL is publicly accessible - Check that your server handles the webhook key - Ensure the request is fully processed   ### 📦 Using the SDK If you\'re building with Node.js or TypeScript, you can use our official SDK for easier integration: <a href=\"https://www.npmjs.com/package/@sureel/sdk\" target=\"_blank\">@sureel/sdk on npm</a>.  ### 🧠 Reading Temporal Attribution Results - `duration`: Length (in seconds) of each analysis window - `period`: Interval (in seconds) between segment starts  If `duration > period`, the analysis uses overlapping segments to improve accuracy. If both values are `-1`, the full song is analyzed in one pass.
+ * ### 🔐 OAuth Authentication To access the Sureel API, the following set of variables will be necessary:      {       \"auth_url\": \"https://sureel.eu.auth0.com/oauth/token\",       \"client_id\": \"<Your-Client-Id>\",       \"client_secret\": \"<Your-Client-Secret>\",       \"audience\": \"https://api.sureel.ai\"     }  Note: We provide the `client_id` and `client_secret` separately.  **Token Request Example:**      curl --request POST \\       --url https://sureel.eu.auth0.com/oauth/token \\       --header \'content-type: application/json\' \\       --data \'{         \"client_id\": \"<Your-Client-Id>\",         \"client_secret\": \"<Your-Client-Secret>\",         \"audience\": \"https://api.sureel.ai\",         \"grant_type\": \"client_credentials\"       }\'  Include the token in your API requests:      Authorization: Bearer <your_token>  **Troubleshooting** - Ensure your token hasn’t expired - Check the Authorization header format - Confirm you\'re using the correct audience   ### 📥 Getting the Request Result You can retrieve processing results in two ways:  - **Polling**:   For audio requests, retrieve results from the <a href=\"#tag/audio-ai/paths/~1v1~1ai~1audio-ldm~1%7BrequestId%7D/get\">/v1/ai/audio-ldm/{requestId}</a> endpoint; for image requests, use the <a href=\"#tag/image-ai/operation/getResultByRequestId\">/v1/ai/ldm/{requestId}</a> endpoint. Make sure the `requestId` is obtained from the POST response. Processing time may vary.  - **Webhooks**: Include a `webhook_url` (and optional `webhook_key`) in your POST body to receive results asynchronously.  **Troubleshooting** - Verify the webhook URL is publicly accessible - Check that your server handles the webhook key - Ensure the request is fully processed   ### 📦 Using the SDK If you\'re building with Node.js or TypeScript, you can use our official SDK for easier integration: <a href=\"https://www.npmjs.com/package/@sureel/sdk\" target=\"_blank\">@sureel/sdk on npm</a>.  ### 🧠 Reading Temporal Attribution Results - `duration`: Length (in seconds) of each analysis window - `period`: Interval (in seconds) between segment starts  If `duration > period`, the analysis uses overlapping segments to improve accuracy. If both values are `-1`, the full song is analyzed in one pass.
  *
  * The version of the OpenAPI document:
  *

package/models/similar-audio-files-per-duration-inner-values-inner.d.ts

@@ -1,6 +1,6 @@
 /**
  * Sureel API
- * ### 🔐 OAuth Authentication To access the Sureel API, the following set of variables will be necessary:      {       \"auth_url\": \"https://dev-p48agspfw4i7fkld.eu.auth0.com/oauth/token\",       \"client_id\": \"<Your-Client-Id>\",       \"client_secret\": \"<Your-Client-Secret>\",       \"audience\": \"https://api.dev.reelx.xyz/\"     }  Note: We provide the `client_id` and `client_secret` separately.  **Token Request Example:**      curl --request POST \\       --url https://dev-p48agspfw4i7fkld.eu.auth0.com/oauth/token \\       --header \'content-type: application/json\' \\       --data \'{         \"client_id\": \"<Your-Client-Id>\",         \"client_secret\": \"<Your-Client-Secret>\",         \"audience\": \"https://api.dev.reelx.xyz/\",         \"grant_type\": \"client_credentials\"       }\'  Include the token in your API requests:      Authorization: Bearer <your_token>  **Troubleshooting** - Ensure your token hasn’t expired - Check the Authorization header format - Confirm you\'re using the correct audience   ### 📥 Getting the Request Result You can retrieve processing results in two ways:  - **Polling**:   For audio requests, retrieve results from the <a href=\"#tag/audio-ai/paths/~1v1~1ai~1audio-ldm~1%7BrequestId%7D/get\">/v1/ai/audio-ldm/{requestId}</a> endpoint; for image requests, use the <a href=\"#tag/image-ai/operation/getResultByRequestId\">/v1/ai/ldm/{requestId}</a> endpoint. Make sure the `requestId` is obtained from the POST response. Processing time may vary.  - **Webhooks**: Include a `webhook_url` (and optional `webhook_key`) in your POST body to receive results asynchronously.  **Troubleshooting** - Verify the webhook URL is publicly accessible - Check that your server handles the webhook key - Ensure the request is fully processed   ### 📦 Using the SDK If you\'re building with Node.js or TypeScript, you can use our official SDK for easier integration: <a href=\"https://www.npmjs.com/package/@sureel/sdk\" target=\"_blank\">@sureel/sdk on npm</a>.  ### 🧠 Reading Temporal Attribution Results - `duration`: Length (in seconds) of each analysis window - `period`: Interval (in seconds) between segment starts  If `duration > period`, the analysis uses overlapping segments to improve accuracy. If both values are `-1`, the full song is analyzed in one pass.
+ * ### 🔐 OAuth Authentication To access the Sureel API, the following set of variables will be necessary:      {       \"auth_url\": \"https://sureel.eu.auth0.com/oauth/token\",       \"client_id\": \"<Your-Client-Id>\",       \"client_secret\": \"<Your-Client-Secret>\",       \"audience\": \"https://api.sureel.ai\"     }  Note: We provide the `client_id` and `client_secret` separately.  **Token Request Example:**      curl --request POST \\       --url https://sureel.eu.auth0.com/oauth/token \\       --header \'content-type: application/json\' \\       --data \'{         \"client_id\": \"<Your-Client-Id>\",         \"client_secret\": \"<Your-Client-Secret>\",         \"audience\": \"https://api.sureel.ai\",         \"grant_type\": \"client_credentials\"       }\'  Include the token in your API requests:      Authorization: Bearer <your_token>  **Troubleshooting** - Ensure your token hasn’t expired - Check the Authorization header format - Confirm you\'re using the correct audience   ### 📥 Getting the Request Result You can retrieve processing results in two ways:  - **Polling**:   For audio requests, retrieve results from the <a href=\"#tag/audio-ai/paths/~1v1~1ai~1audio-ldm~1%7BrequestId%7D/get\">/v1/ai/audio-ldm/{requestId}</a> endpoint; for image requests, use the <a href=\"#tag/image-ai/operation/getResultByRequestId\">/v1/ai/ldm/{requestId}</a> endpoint. Make sure the `requestId` is obtained from the POST response. Processing time may vary.  - **Webhooks**: Include a `webhook_url` (and optional `webhook_key`) in your POST body to receive results asynchronously.  **Troubleshooting** - Verify the webhook URL is publicly accessible - Check that your server handles the webhook key - Ensure the request is fully processed   ### 📦 Using the SDK If you\'re building with Node.js or TypeScript, you can use our official SDK for easier integration: <a href=\"https://www.npmjs.com/package/@sureel/sdk\" target=\"_blank\">@sureel/sdk on npm</a>.  ### 🧠 Reading Temporal Attribution Results - `duration`: Length (in seconds) of each analysis window - `period`: Interval (in seconds) between segment starts  If `duration > period`, the analysis uses overlapping segments to improve accuracy. If both values are `-1`, the full song is analyzed in one pass.
  *
  * The version of the OpenAPI document:
  *

package/models/similar-audio-files-per-duration-inner-values-inner.js

@@ -3,7 +3,7 @@
 /* eslint-disable */
 /**
  * Sureel API
- * ### 🔐 OAuth Authentication To access the Sureel API, the following set of variables will be necessary:      {       \"auth_url\": \"https://dev-p48agspfw4i7fkld.eu.auth0.com/oauth/token\",       \"client_id\": \"<Your-Client-Id>\",       \"client_secret\": \"<Your-Client-Secret>\",       \"audience\": \"https://api.dev.reelx.xyz/\"     }  Note: We provide the `client_id` and `client_secret` separately.  **Token Request Example:**      curl --request POST \\       --url https://dev-p48agspfw4i7fkld.eu.auth0.com/oauth/token \\       --header \'content-type: application/json\' \\       --data \'{         \"client_id\": \"<Your-Client-Id>\",         \"client_secret\": \"<Your-Client-Secret>\",         \"audience\": \"https://api.dev.reelx.xyz/\",         \"grant_type\": \"client_credentials\"       }\'  Include the token in your API requests:      Authorization: Bearer <your_token>  **Troubleshooting** - Ensure your token hasn’t expired - Check the Authorization header format - Confirm you\'re using the correct audience   ### 📥 Getting the Request Result You can retrieve processing results in two ways:  - **Polling**:   For audio requests, retrieve results from the <a href=\"#tag/audio-ai/paths/~1v1~1ai~1audio-ldm~1%7BrequestId%7D/get\">/v1/ai/audio-ldm/{requestId}</a> endpoint; for image requests, use the <a href=\"#tag/image-ai/operation/getResultByRequestId\">/v1/ai/ldm/{requestId}</a> endpoint. Make sure the `requestId` is obtained from the POST response. Processing time may vary.  - **Webhooks**: Include a `webhook_url` (and optional `webhook_key`) in your POST body to receive results asynchronously.  **Troubleshooting** - Verify the webhook URL is publicly accessible - Check that your server handles the webhook key - Ensure the request is fully processed   ### 📦 Using the SDK If you\'re building with Node.js or TypeScript, you can use our official SDK for easier integration: <a href=\"https://www.npmjs.com/package/@sureel/sdk\" target=\"_blank\">@sureel/sdk on npm</a>.  ### 🧠 Reading Temporal Attribution Results - `duration`: Length (in seconds) of each analysis window - `period`: Interval (in seconds) between segment starts  If `duration > period`, the analysis uses overlapping segments to improve accuracy. If both values are `-1`, the full song is analyzed in one pass.
+ * ### 🔐 OAuth Authentication To access the Sureel API, the following set of variables will be necessary:      {       \"auth_url\": \"https://sureel.eu.auth0.com/oauth/token\",       \"client_id\": \"<Your-Client-Id>\",       \"client_secret\": \"<Your-Client-Secret>\",       \"audience\": \"https://api.sureel.ai\"     }  Note: We provide the `client_id` and `client_secret` separately.  **Token Request Example:**      curl --request POST \\       --url https://sureel.eu.auth0.com/oauth/token \\       --header \'content-type: application/json\' \\       --data \'{         \"client_id\": \"<Your-Client-Id>\",         \"client_secret\": \"<Your-Client-Secret>\",         \"audience\": \"https://api.sureel.ai\",         \"grant_type\": \"client_credentials\"       }\'  Include the token in your API requests:      Authorization: Bearer <your_token>  **Troubleshooting** - Ensure your token hasn’t expired - Check the Authorization header format - Confirm you\'re using the correct audience   ### 📥 Getting the Request Result You can retrieve processing results in two ways:  - **Polling**:   For audio requests, retrieve results from the <a href=\"#tag/audio-ai/paths/~1v1~1ai~1audio-ldm~1%7BrequestId%7D/get\">/v1/ai/audio-ldm/{requestId}</a> endpoint; for image requests, use the <a href=\"#tag/image-ai/operation/getResultByRequestId\">/v1/ai/ldm/{requestId}</a> endpoint. Make sure the `requestId` is obtained from the POST response. Processing time may vary.  - **Webhooks**: Include a `webhook_url` (and optional `webhook_key`) in your POST body to receive results asynchronously.  **Troubleshooting** - Verify the webhook URL is publicly accessible - Check that your server handles the webhook key - Ensure the request is fully processed   ### 📦 Using the SDK If you\'re building with Node.js or TypeScript, you can use our official SDK for easier integration: <a href=\"https://www.npmjs.com/package/@sureel/sdk\" target=\"_blank\">@sureel/sdk on npm</a>.  ### 🧠 Reading Temporal Attribution Results - `duration`: Length (in seconds) of each analysis window - `period`: Interval (in seconds) between segment starts  If `duration > period`, the analysis uses overlapping segments to improve accuracy. If both values are `-1`, the full song is analyzed in one pass.
  *
  * The version of the OpenAPI document:
  *

package/models/similar-audio-files-per-duration-inner.d.ts

@@ -1,6 +1,6 @@
 /**
  * Sureel API
- * ### 🔐 OAuth Authentication To access the Sureel API, the following set of variables will be necessary:      {       \"auth_url\": \"https://dev-p48agspfw4i7fkld.eu.auth0.com/oauth/token\",       \"client_id\": \"<Your-Client-Id>\",       \"client_secret\": \"<Your-Client-Secret>\",       \"audience\": \"https://api.dev.reelx.xyz/\"     }  Note: We provide the `client_id` and `client_secret` separately.  **Token Request Example:**      curl --request POST \\       --url https://dev-p48agspfw4i7fkld.eu.auth0.com/oauth/token \\       --header \'content-type: application/json\' \\       --data \'{         \"client_id\": \"<Your-Client-Id>\",         \"client_secret\": \"<Your-Client-Secret>\",         \"audience\": \"https://api.dev.reelx.xyz/\",         \"grant_type\": \"client_credentials\"       }\'  Include the token in your API requests:      Authorization: Bearer <your_token>  **Troubleshooting** - Ensure your token hasn’t expired - Check the Authorization header format - Confirm you\'re using the correct audience   ### 📥 Getting the Request Result You can retrieve processing results in two ways:  - **Polling**:   For audio requests, retrieve results from the <a href=\"#tag/audio-ai/paths/~1v1~1ai~1audio-ldm~1%7BrequestId%7D/get\">/v1/ai/audio-ldm/{requestId}</a> endpoint; for image requests, use the <a href=\"#tag/image-ai/operation/getResultByRequestId\">/v1/ai/ldm/{requestId}</a> endpoint. Make sure the `requestId` is obtained from the POST response. Processing time may vary.  - **Webhooks**: Include a `webhook_url` (and optional `webhook_key`) in your POST body to receive results asynchronously.  **Troubleshooting** - Verify the webhook URL is publicly accessible - Check that your server handles the webhook key - Ensure the request is fully processed   ### 📦 Using the SDK If you\'re building with Node.js or TypeScript, you can use our official SDK for easier integration: <a href=\"https://www.npmjs.com/package/@sureel/sdk\" target=\"_blank\">@sureel/sdk on npm</a>.  ### 🧠 Reading Temporal Attribution Results - `duration`: Length (in seconds) of each analysis window - `period`: Interval (in seconds) between segment starts  If `duration > period`, the analysis uses overlapping segments to improve accuracy. If both values are `-1`, the full song is analyzed in one pass.
+ * ### 🔐 OAuth Authentication To access the Sureel API, the following set of variables will be necessary:      {       \"auth_url\": \"https://sureel.eu.auth0.com/oauth/token\",       \"client_id\": \"<Your-Client-Id>\",       \"client_secret\": \"<Your-Client-Secret>\",       \"audience\": \"https://api.sureel.ai\"     }  Note: We provide the `client_id` and `client_secret` separately.  **Token Request Example:**      curl --request POST \\       --url https://sureel.eu.auth0.com/oauth/token \\       --header \'content-type: application/json\' \\       --data \'{         \"client_id\": \"<Your-Client-Id>\",         \"client_secret\": \"<Your-Client-Secret>\",         \"audience\": \"https://api.sureel.ai\",         \"grant_type\": \"client_credentials\"       }\'  Include the token in your API requests:      Authorization: Bearer <your_token>  **Troubleshooting** - Ensure your token hasn’t expired - Check the Authorization header format - Confirm you\'re using the correct audience   ### 📥 Getting the Request Result You can retrieve processing results in two ways:  - **Polling**:   For audio requests, retrieve results from the <a href=\"#tag/audio-ai/paths/~1v1~1ai~1audio-ldm~1%7BrequestId%7D/get\">/v1/ai/audio-ldm/{requestId}</a> endpoint; for image requests, use the <a href=\"#tag/image-ai/operation/getResultByRequestId\">/v1/ai/ldm/{requestId}</a> endpoint. Make sure the `requestId` is obtained from the POST response. Processing time may vary.  - **Webhooks**: Include a `webhook_url` (and optional `webhook_key`) in your POST body to receive results asynchronously.  **Troubleshooting** - Verify the webhook URL is publicly accessible - Check that your server handles the webhook key - Ensure the request is fully processed   ### 📦 Using the SDK If you\'re building with Node.js or TypeScript, you can use our official SDK for easier integration: <a href=\"https://www.npmjs.com/package/@sureel/sdk\" target=\"_blank\">@sureel/sdk on npm</a>.  ### 🧠 Reading Temporal Attribution Results - `duration`: Length (in seconds) of each analysis window - `period`: Interval (in seconds) between segment starts  If `duration > period`, the analysis uses overlapping segments to improve accuracy. If both values are `-1`, the full song is analyzed in one pass.
  *
  * The version of the OpenAPI document:
  *

package/models/similar-audio-files-per-duration-inner.js

@@ -3,7 +3,7 @@
 /* eslint-disable */
 /**
  * Sureel API
- * ### 🔐 OAuth Authentication To access the Sureel API, the following set of variables will be necessary:      {       \"auth_url\": \"https://dev-p48agspfw4i7fkld.eu.auth0.com/oauth/token\",       \"client_id\": \"<Your-Client-Id>\",       \"client_secret\": \"<Your-Client-Secret>\",       \"audience\": \"https://api.dev.reelx.xyz/\"     }  Note: We provide the `client_id` and `client_secret` separately.  **Token Request Example:**      curl --request POST \\       --url https://dev-p48agspfw4i7fkld.eu.auth0.com/oauth/token \\       --header \'content-type: application/json\' \\       --data \'{         \"client_id\": \"<Your-Client-Id>\",         \"client_secret\": \"<Your-Client-Secret>\",         \"audience\": \"https://api.dev.reelx.xyz/\",         \"grant_type\": \"client_credentials\"       }\'  Include the token in your API requests:      Authorization: Bearer <your_token>  **Troubleshooting** - Ensure your token hasn’t expired - Check the Authorization header format - Confirm you\'re using the correct audience   ### 📥 Getting the Request Result You can retrieve processing results in two ways:  - **Polling**:   For audio requests, retrieve results from the <a href=\"#tag/audio-ai/paths/~1v1~1ai~1audio-ldm~1%7BrequestId%7D/get\">/v1/ai/audio-ldm/{requestId}</a> endpoint; for image requests, use the <a href=\"#tag/image-ai/operation/getResultByRequestId\">/v1/ai/ldm/{requestId}</a> endpoint. Make sure the `requestId` is obtained from the POST response. Processing time may vary.  - **Webhooks**: Include a `webhook_url` (and optional `webhook_key`) in your POST body to receive results asynchronously.  **Troubleshooting** - Verify the webhook URL is publicly accessible - Check that your server handles the webhook key - Ensure the request is fully processed   ### 📦 Using the SDK If you\'re building with Node.js or TypeScript, you can use our official SDK for easier integration: <a href=\"https://www.npmjs.com/package/@sureel/sdk\" target=\"_blank\">@sureel/sdk on npm</a>.  ### 🧠 Reading Temporal Attribution Results - `duration`: Length (in seconds) of each analysis window - `period`: Interval (in seconds) between segment starts  If `duration > period`, the analysis uses overlapping segments to improve accuracy. If both values are `-1`, the full song is analyzed in one pass.
+ * ### 🔐 OAuth Authentication To access the Sureel API, the following set of variables will be necessary:      {       \"auth_url\": \"https://sureel.eu.auth0.com/oauth/token\",       \"client_id\": \"<Your-Client-Id>\",       \"client_secret\": \"<Your-Client-Secret>\",       \"audience\": \"https://api.sureel.ai\"     }  Note: We provide the `client_id` and `client_secret` separately.  **Token Request Example:**      curl --request POST \\       --url https://sureel.eu.auth0.com/oauth/token \\       --header \'content-type: application/json\' \\       --data \'{         \"client_id\": \"<Your-Client-Id>\",         \"client_secret\": \"<Your-Client-Secret>\",         \"audience\": \"https://api.sureel.ai\",         \"grant_type\": \"client_credentials\"       }\'  Include the token in your API requests:      Authorization: Bearer <your_token>  **Troubleshooting** - Ensure your token hasn’t expired - Check the Authorization header format - Confirm you\'re using the correct audience   ### 📥 Getting the Request Result You can retrieve processing results in two ways:  - **Polling**:   For audio requests, retrieve results from the <a href=\"#tag/audio-ai/paths/~1v1~1ai~1audio-ldm~1%7BrequestId%7D/get\">/v1/ai/audio-ldm/{requestId}</a> endpoint; for image requests, use the <a href=\"#tag/image-ai/operation/getResultByRequestId\">/v1/ai/ldm/{requestId}</a> endpoint. Make sure the `requestId` is obtained from the POST response. Processing time may vary.  - **Webhooks**: Include a `webhook_url` (and optional `webhook_key`) in your POST body to receive results asynchronously.  **Troubleshooting** - Verify the webhook URL is publicly accessible - Check that your server handles the webhook key - Ensure the request is fully processed   ### 📦 Using the SDK If you\'re building with Node.js or TypeScript, you can use our official SDK for easier integration: <a href=\"https://www.npmjs.com/package/@sureel/sdk\" target=\"_blank\">@sureel/sdk on npm</a>.  ### 🧠 Reading Temporal Attribution Results - `duration`: Length (in seconds) of each analysis window - `period`: Interval (in seconds) between segment starts  If `duration > period`, the analysis uses overlapping segments to improve accuracy. If both values are `-1`, the full song is analyzed in one pass.
  *
  * The version of the OpenAPI document:
  *

package/models/similar-audio-files-per-stem.d.ts

@@ -1,6 +1,6 @@
 /**
  * Sureel API
- * ### 🔐 OAuth Authentication To access the Sureel API, the following set of variables will be necessary:      {       \"auth_url\": \"https://dev-p48agspfw4i7fkld.eu.auth0.com/oauth/token\",       \"client_id\": \"<Your-Client-Id>\",       \"client_secret\": \"<Your-Client-Secret>\",       \"audience\": \"https://api.dev.reelx.xyz/\"     }  Note: We provide the `client_id` and `client_secret` separately.  **Token Request Example:**      curl --request POST \\       --url https://dev-p48agspfw4i7fkld.eu.auth0.com/oauth/token \\       --header \'content-type: application/json\' \\       --data \'{         \"client_id\": \"<Your-Client-Id>\",         \"client_secret\": \"<Your-Client-Secret>\",         \"audience\": \"https://api.dev.reelx.xyz/\",         \"grant_type\": \"client_credentials\"       }\'  Include the token in your API requests:      Authorization: Bearer <your_token>  **Troubleshooting** - Ensure your token hasn’t expired - Check the Authorization header format - Confirm you\'re using the correct audience   ### 📥 Getting the Request Result You can retrieve processing results in two ways:  - **Polling**:   For audio requests, retrieve results from the <a href=\"#tag/audio-ai/paths/~1v1~1ai~1audio-ldm~1%7BrequestId%7D/get\">/v1/ai/audio-ldm/{requestId}</a> endpoint; for image requests, use the <a href=\"#tag/image-ai/operation/getResultByRequestId\">/v1/ai/ldm/{requestId}</a> endpoint. Make sure the `requestId` is obtained from the POST response. Processing time may vary.  - **Webhooks**: Include a `webhook_url` (and optional `webhook_key`) in your POST body to receive results asynchronously.  **Troubleshooting** - Verify the webhook URL is publicly accessible - Check that your server handles the webhook key - Ensure the request is fully processed   ### 📦 Using the SDK If you\'re building with Node.js or TypeScript, you can use our official SDK for easier integration: <a href=\"https://www.npmjs.com/package/@sureel/sdk\" target=\"_blank\">@sureel/sdk on npm</a>.  ### 🧠 Reading Temporal Attribution Results - `duration`: Length (in seconds) of each analysis window - `period`: Interval (in seconds) between segment starts  If `duration > period`, the analysis uses overlapping segments to improve accuracy. If both values are `-1`, the full song is analyzed in one pass.
+ * ### 🔐 OAuth Authentication To access the Sureel API, the following set of variables will be necessary:      {       \"auth_url\": \"https://sureel.eu.auth0.com/oauth/token\",       \"client_id\": \"<Your-Client-Id>\",       \"client_secret\": \"<Your-Client-Secret>\",       \"audience\": \"https://api.sureel.ai\"     }  Note: We provide the `client_id` and `client_secret` separately.  **Token Request Example:**      curl --request POST \\       --url https://sureel.eu.auth0.com/oauth/token \\       --header \'content-type: application/json\' \\       --data \'{         \"client_id\": \"<Your-Client-Id>\",         \"client_secret\": \"<Your-Client-Secret>\",         \"audience\": \"https://api.sureel.ai\",         \"grant_type\": \"client_credentials\"       }\'  Include the token in your API requests:      Authorization: Bearer <your_token>  **Troubleshooting** - Ensure your token hasn’t expired - Check the Authorization header format - Confirm you\'re using the correct audience   ### 📥 Getting the Request Result You can retrieve processing results in two ways:  - **Polling**:   For audio requests, retrieve results from the <a href=\"#tag/audio-ai/paths/~1v1~1ai~1audio-ldm~1%7BrequestId%7D/get\">/v1/ai/audio-ldm/{requestId}</a> endpoint; for image requests, use the <a href=\"#tag/image-ai/operation/getResultByRequestId\">/v1/ai/ldm/{requestId}</a> endpoint. Make sure the `requestId` is obtained from the POST response. Processing time may vary.  - **Webhooks**: Include a `webhook_url` (and optional `webhook_key`) in your POST body to receive results asynchronously.  **Troubleshooting** - Verify the webhook URL is publicly accessible - Check that your server handles the webhook key - Ensure the request is fully processed   ### 📦 Using the SDK If you\'re building with Node.js or TypeScript, you can use our official SDK for easier integration: <a href=\"https://www.npmjs.com/package/@sureel/sdk\" target=\"_blank\">@sureel/sdk on npm</a>.  ### 🧠 Reading Temporal Attribution Results - `duration`: Length (in seconds) of each analysis window - `period`: Interval (in seconds) between segment starts  If `duration > period`, the analysis uses overlapping segments to improve accuracy. If both values are `-1`, the full song is analyzed in one pass.
  *
  * The version of the OpenAPI document:
  *