@orq-ai/node 4.10.0-rc.2 → 4.10.0-rc.20

package/src/models/operations/createeval.ts

@@ -74,13 +74,13 @@ export type Python = {
   code: string;
   type: CreateEvalRequestBodyType;
   /**
-   * Entity storage path in the format: `project/folder/subfolder/...`
+   * Entity storage path.
    *
    * @remarks
    *
-   * The first element identifies the project, followed by nested folders (auto-created as needed).
+   * With workspace-level API keys, use the format `project/folder/subfolder/...`. The first element identifies the project, followed by nested folders (auto-created as needed). Example: `Default/agents`.
    *
-   * With project-based API keys, the first element is treated as a folder name, as the project is predetermined by the API key.
+   * With project-level API keys, the project is predetermined by the API key, so the path is relative to that project. Example: `agents`. For backward compatibility, a leading project name is ignored when it matches the scoped project.
    */
   path: string;
   description?: string | undefined;
@@ -170,13 +170,13 @@ export type RequestBodyHTTP = {
   headers: { [k: string]: string };
   payload: { [k: string]: any };
   /**
-   * Entity storage path in the format: `project/folder/subfolder/...`
+   * Entity storage path.
    *
    * @remarks
    *
-   * The first element identifies the project, followed by nested folders (auto-created as needed).
+   * With workspace-level API keys, use the format `project/folder/subfolder/...`. The first element identifies the project, followed by nested folders (auto-created as needed). Example: `Default/agents`.
    *
-   * With project-based API keys, the first element is treated as a folder name, as the project is predetermined by the API key.
+   * With project-level API keys, the project is predetermined by the API key, so the path is relative to that project. Example: `agents`. For backward compatibility, a leading project name is ignored when it matches the scoped project.
    */
   path: string;
   description?: string | undefined;
@@ -245,13 +245,13 @@ export type Json = {
   type: CreateEvalRequestBodyEvalsType;
   schema: string;
   /**
-   * Entity storage path in the format: `project/folder/subfolder/...`
+   * Entity storage path.
    *
    * @remarks
    *
-   * The first element identifies the project, followed by nested folders (auto-created as needed).
+   * With workspace-level API keys, use the format `project/folder/subfolder/...`. The first element identifies the project, followed by nested folders (auto-created as needed). Example: `Default/agents`.
    *
-   * With project-based API keys, the first element is treated as a folder name, as the project is predetermined by the API key.
+   * With project-level API keys, the project is predetermined by the API key, so the path is relative to that project. Example: `agents`. For backward compatibility, a leading project name is ignored when it matches the scoped project.
    */
   path: string;
   description?: string | undefined;
@@ -378,14 +378,15 @@ export type Llm2 = {
   prompt: string;
   categories?: Array<string> | undefined;
   categoricalLabels?: Array<LLMCategoricalLabels> | undefined;
+  datasetId?: string | undefined;
   /**
-   * Entity storage path in the format: `project/folder/subfolder/...`
+   * Entity storage path.
    *
    * @remarks
    *
-   * The first element identifies the project, followed by nested folders (auto-created as needed).
+   * With workspace-level API keys, use the format `project/folder/subfolder/...`. The first element identifies the project, followed by nested folders (auto-created as needed). Example: `Default/agents`.
    *
-   * With project-based API keys, the first element is treated as a folder name, as the project is predetermined by the API key.
+   * With project-level API keys, the project is predetermined by the API key, so the path is relative to that project. Example: `agents`. For backward compatibility, a leading project name is ignored when it matches the scoped project.
    */
   path: string;
   description?: string | undefined;
@@ -475,14 +476,15 @@ export type Llm1 = {
   prompt: string;
   categories?: Array<string> | undefined;
   categoricalLabels?: Array<CreateEvalLLMCategoricalLabels> | undefined;
+  datasetId?: string | undefined;
   /**
-   * Entity storage path in the format: `project/folder/subfolder/...`
+   * Entity storage path.
    *
    * @remarks
    *
-   * The first element identifies the project, followed by nested folders (auto-created as needed).
+   * With workspace-level API keys, use the format `project/folder/subfolder/...`. The first element identifies the project, followed by nested folders (auto-created as needed). Example: `Default/agents`.
    *
-   * With project-based API keys, the first element is treated as a folder name, as the project is predetermined by the API key.
+   * With project-level API keys, the project is predetermined by the API key, so the path is relative to that project. Example: `agents`. For backward compatibility, a leading project name is ignored when it matches the scoped project.
    */
   path: string;
   description?: string | undefined;
@@ -1237,6 +1239,7 @@ export type CreateEvalLlm2 = {
   prompt: string;
   categories?: Array<string> | undefined;
   categoricalLabels?: Array<CreateEvalLLMEvalsCategoricalLabels> | undefined;
+  datasetId?: string | undefined;
   key: string;
   mode: "jury";
   jury: CreateEvalLLMJury;
@@ -1315,6 +1318,7 @@ export type CreateEvalLlm1 = {
   categoricalLabels?:
     | Array<CreateEvalLLMEvalsResponseCategoricalLabels>
     | undefined;
+  datasetId?: string | undefined;
   key: string;
   mode: "single";
   model: string;
@@ -2288,6 +2292,7 @@ export type Llm2$Outbound = {
   prompt: string;
   categories?: Array<string> | undefined;
   categorical_labels?: Array<LLMCategoricalLabels$Outbound> | undefined;
+  dataset_id?: string | undefined;
   path: string;
   description: string;
   key: string;
@@ -2319,6 +2324,7 @@ export const Llm2$outboundSchema: z.ZodType<Llm2$Outbound, z.ZodTypeDef, Llm2> =
     categoricalLabels: z.array(
       z.lazy(() => LLMCategoricalLabels$outboundSchema),
     ).optional(),
+    datasetId: z.string().optional(),
     path: z.string(),
     description: z.string().default(""),
     key: z.string(),
@@ -2329,6 +2335,7 @@ export const Llm2$outboundSchema: z.ZodType<Llm2$Outbound, z.ZodTypeDef, Llm2> =
       guardrailConfig: "guardrail_config",
       outputType: "output_type",
       categoricalLabels: "categorical_labels",
+      datasetId: "dataset_id",
     });
   });
 
@@ -2530,6 +2537,7 @@ export type Llm1$Outbound = {
   categorical_labels?:
     | Array<CreateEvalLLMCategoricalLabels$Outbound>
     | undefined;
+  dataset_id?: string | undefined;
   path: string;
   description: string;
   key: string;
@@ -2561,6 +2569,7 @@ export const Llm1$outboundSchema: z.ZodType<Llm1$Outbound, z.ZodTypeDef, Llm1> =
     categoricalLabels: z.array(
       z.lazy(() => CreateEvalLLMCategoricalLabels$outboundSchema),
     ).optional(),
+    datasetId: z.string().optional(),
     path: z.string(),
     description: z.string().default(""),
     key: z.string(),
@@ -2571,6 +2580,7 @@ export const Llm1$outboundSchema: z.ZodType<Llm1$Outbound, z.ZodTypeDef, Llm1> =
       guardrailConfig: "guardrail_config",
       outputType: "output_type",
       categoricalLabels: "categorical_labels",
+      datasetId: "dataset_id",
     });
   });
 
@@ -2776,8 +2786,8 @@ export const Typescript$inboundSchema: z.ZodType<
 > = z.object({
   _id: z.string(),
   description: z.string(),
-  created: z.string().default("2026-05-13T12:08:29.916Z"),
-  updated: z.string().default("2026-05-13T12:08:29.917Z"),
+  created: z.string().default("2026-05-20T07:16:36.761Z"),
+  updated: z.string().default("2026-05-20T07:16:36.761Z"),
   guardrail_config: z.nullable(
     z.union([
       z.lazy(() =>
@@ -2965,8 +2975,8 @@ export const Ragas$inboundSchema: z.ZodType<Ragas, z.ZodTypeDef, unknown> = z
   .object({
     _id: z.string(),
     description: z.string(),
-    created: z.string().default("2026-05-13T12:08:29.916Z"),
-    updated: z.string().default("2026-05-13T12:08:29.917Z"),
+    created: z.string().default("2026-05-20T07:16:36.761Z"),
+    updated: z.string().default("2026-05-20T07:16:36.761Z"),
     guardrail_config: z.nullable(
       z.union([
         z.lazy(() =>
@@ -3789,8 +3799,8 @@ export const CreateEvalResponseBodyFunction$inboundSchema: z.ZodType<
 > = z.object({
   _id: z.string(),
   description: z.string(),
-  created: z.string().default("2026-05-13T12:08:29.916Z"),
-  updated: z.string().default("2026-05-13T12:08:29.917Z"),
+  created: z.string().default("2026-05-20T07:16:36.761Z"),
+  updated: z.string().default("2026-05-20T07:16:36.761Z"),
   guardrail_config: z.nullable(
     z.union([
       z.lazy(() =>
@@ -4008,8 +4018,8 @@ export const ResponseBodyPython$inboundSchema: z.ZodType<
 > = z.object({
   _id: z.string(),
   description: z.string(),
-  created: z.string().default("2026-05-13T12:08:29.916Z"),
-  updated: z.string().default("2026-05-13T12:08:29.917Z"),
+  created: z.string().default("2026-05-20T07:16:36.761Z"),
+  updated: z.string().default("2026-05-20T07:16:36.761Z"),
   guardrail_config: z.nullable(
     z.union([
       z.lazy(() =>
@@ -4190,8 +4200,8 @@ export const ResponseBodyHTTP$inboundSchema: z.ZodType<
 > = z.object({
   _id: z.string(),
   description: z.string(),
-  created: z.string().default("2026-05-13T12:08:29.916Z"),
-  updated: z.string().default("2026-05-13T12:08:29.917Z"),
+  created: z.string().default("2026-05-20T07:16:36.761Z"),
+  updated: z.string().default("2026-05-20T07:16:36.761Z"),
   guardrail_config: z.nullable(
     z.union([
       z.lazy(() =>
@@ -4367,8 +4377,8 @@ export const ResponseBodyJSON$inboundSchema: z.ZodType<
 > = z.object({
   _id: z.string(),
   description: z.string(),
-  created: z.string().default("2026-05-13T12:08:29.916Z"),
-  updated: z.string().default("2026-05-13T12:08:29.917Z"),
+  created: z.string().default("2026-05-20T07:16:36.761Z"),
+  updated: z.string().default("2026-05-20T07:16:36.761Z"),
   guardrail_config: z.nullable(
     z.union([
       z.lazy(() => CreateEvalGuardrailConfigEvalsResponseBoolean$inboundSchema),
@@ -4738,8 +4748,8 @@ export const CreateEvalLlm2$inboundSchema: z.ZodType<
 > = z.object({
   _id: z.string(),
   description: z.string(),
-  created: z.string().default("2026-05-13T12:08:29.916Z"),
-  updated: z.string().default("2026-05-13T12:08:29.917Z"),
+  created: z.string().default("2026-05-20T07:16:36.761Z"),
+  updated: z.string().default("2026-05-20T07:16:36.761Z"),
   guardrail_config: z.nullable(
     z.union([
       z.lazy(() =>
@@ -4760,6 +4770,7 @@ export const CreateEvalLlm2$inboundSchema: z.ZodType<
   categorical_labels: z.array(
     z.lazy(() => CreateEvalLLMEvalsCategoricalLabels$inboundSchema),
   ).optional(),
+  dataset_id: z.string().optional(),
   key: z.string(),
   mode: z.literal("jury"),
   jury: z.lazy(() => CreateEvalLLMJury$inboundSchema),
@@ -4768,6 +4779,7 @@ export const CreateEvalLlm2$inboundSchema: z.ZodType<
     "_id": "id",
     "guardrail_config": "guardrailConfig",
     "categorical_labels": "categoricalLabels",
+    "dataset_id": "datasetId",
   });
 });
 
@@ -4954,8 +4966,8 @@ export const CreateEvalLlm1$inboundSchema: z.ZodType<
 > = z.object({
   _id: z.string(),
   description: z.string(),
-  created: z.string().default("2026-05-13T12:08:29.916Z"),
-  updated: z.string().default("2026-05-13T12:08:29.917Z"),
+  created: z.string().default("2026-05-20T07:16:36.761Z"),
+  updated: z.string().default("2026-05-20T07:16:36.761Z"),
   guardrail_config: z.nullable(
     z.union([
       z.lazy(() =>
@@ -4976,6 +4988,7 @@ export const CreateEvalLlm1$inboundSchema: z.ZodType<
   categorical_labels: z.array(
     z.lazy(() => CreateEvalLLMEvalsResponseCategoricalLabels$inboundSchema),
   ).optional(),
+  dataset_id: z.string().optional(),
   key: z.string(),
   mode: z.literal("single"),
   model: z.string(),
@@ -4984,6 +4997,7 @@ export const CreateEvalLlm1$inboundSchema: z.ZodType<
     "_id": "id",
     "guardrail_config": "guardrailConfig",
     "categorical_labels": "categoricalLabels",
+    "dataset_id": "datasetId",
   });
 });
 

package/src/models/operations/createknowledge.ts

@@ -128,13 +128,13 @@ export type CreateKnowledgeRequestBody1 = {
    */
   retrievalSettings?: RetrievalSettings | undefined;
   /**
-   * Entity storage path in the format: `project/folder/subfolder/...`
+   * Entity storage path.
    *
    * @remarks
    *
-   * The first element identifies the project, followed by nested folders (auto-created as needed).
+   * With workspace-level API keys, use the format `project/folder/subfolder/...`. The first element identifies the project, followed by nested folders (auto-created as needed). Example: `Default/agents`.
    *
-   * With project-based API keys, the first element is treated as a folder name, as the project is predetermined by the API key.
+   * With project-level API keys, the project is predetermined by the API key, so the path is relative to that project. Example: `agents`. For backward compatibility, a leading project name is ignored when it matches the scoped project.
    */
   path: string;
 };
@@ -236,13 +236,13 @@ export type ResponseBody2 = {
    */
   domainId: string;
   /**
-   * Entity storage path in the format: `project/folder/subfolder/...`
+   * Entity storage path.
    *
    * @remarks
    *
-   * The first element identifies the project, followed by nested folders (auto-created as needed).
+   * With workspace-level API keys, use the format `project/folder/subfolder/...`. The first element identifies the project, followed by nested folders (auto-created as needed). Example: `Default/agents`.
    *
-   * With project-based API keys, the first element is treated as a folder name, as the project is predetermined by the API key.
+   * With project-level API keys, the project is predetermined by the API key, so the path is relative to that project. Example: `agents`. For backward compatibility, a leading project name is ignored when it matches the scoped project.
    */
   path?: string | undefined;
   createdById?: string | null | undefined;
@@ -357,13 +357,13 @@ export type ResponseBody1 = {
    */
   domainId: string;
   /**
-   * Entity storage path in the format: `project/folder/subfolder/...`
+   * Entity storage path.
    *
    * @remarks
    *
-   * The first element identifies the project, followed by nested folders (auto-created as needed).
+   * With workspace-level API keys, use the format `project/folder/subfolder/...`. The first element identifies the project, followed by nested folders (auto-created as needed). Example: `Default/agents`.
    *
-   * With project-based API keys, the first element is treated as a folder name, as the project is predetermined by the API key.
+   * With project-level API keys, the project is predetermined by the API key, so the path is relative to that project. Example: `agents`. For backward compatibility, a leading project name is ignored when it matches the scoped project.
    */
   path?: string | undefined;
   createdById?: string | null | undefined;

package/src/models/operations/creatememorystore.ts

@@ -30,13 +30,13 @@ export type CreateMemoryStoreRequestBody = {
    */
   ttl?: number | undefined;
   /**
-   * Entity storage path in the format: `project/folder/subfolder/...`
+   * Entity storage path.
    *
    * @remarks
    *
-   * The first element identifies the project, followed by nested folders (auto-created as needed).
+   * With workspace-level API keys, use the format `project/folder/subfolder/...`. The first element identifies the project, followed by nested folders (auto-created as needed). Example: `Default/agents`.
    *
-   * With project-based API keys, the first element is treated as a folder name, as the project is predetermined by the API key.
+   * With project-level API keys, the project is predetermined by the API key, so the path is relative to that project. Example: `agents`. For backward compatibility, a leading project name is ignored when it matches the scoped project.
    */
   path: string;
 };

package/src/models/operations/createprompt.ts

@@ -871,13 +871,13 @@ export type CreatePromptRequestBody = {
    */
   prompt: PromptInput;
   /**
-   * Entity storage path in the format: `project/folder/subfolder/...`
+   * Entity storage path.
    *
    * @remarks
    *
-   * The first element identifies the project, followed by nested folders (auto-created as needed).
+   * With workspace-level API keys, use the format `project/folder/subfolder/...`. The first element identifies the project, followed by nested folders (auto-created as needed). Example: `Default/agents`.
    *
-   * With project-based API keys, the first element is treated as a folder name, as the project is predetermined by the API key.
+   * With project-level API keys, the project is predetermined by the API key, so the path is relative to that project. Example: `agents`. For backward compatibility, a leading project name is ignored when it matches the scoped project.
    */
   path: string;
 };

package/src/models/operations/createrouterresponse.ts

@@ -318,11 +318,6 @@ export type OrqAiTool = {
   type: CreateRouterResponseToolsType;
 };
 
-/**
- * The parameters the function accepts, as a JSON Schema object.
- */
-export type ToolsParameters = {};
-
 /**
  * A function tool the model can call.
  */
@@ -338,7 +333,7 @@ export type ToolsFunction = {
   /**
    * The parameters the function accepts, as a JSON Schema object.
    */
-  parameters?: ToolsParameters | undefined;
+  parameters?: { [k: string]: any } | undefined;
   /**
    * Whether to enforce strict parameter validation.
    */
@@ -1100,27 +1095,11 @@ export function orqAiToolToJSON(orqAiTool: OrqAiTool): string {
   return JSON.stringify(OrqAiTool$outboundSchema.parse(orqAiTool));
 }
 
-/** @internal */
-export type ToolsParameters$Outbound = {};
-
-/** @internal */
-export const ToolsParameters$outboundSchema: z.ZodType<
-  ToolsParameters$Outbound,
-  z.ZodTypeDef,
-  ToolsParameters
-> = z.object({});
-
-export function toolsParametersToJSON(
-  toolsParameters: ToolsParameters,
-): string {
-  return JSON.stringify(ToolsParameters$outboundSchema.parse(toolsParameters));
-}
-
 /** @internal */
 export type ToolsFunction$Outbound = {
   description?: string | undefined;
   name: string;
-  parameters?: ToolsParameters$Outbound | undefined;
+  parameters?: { [k: string]: any } | undefined;
   strict?: boolean | undefined;
   type: "function";
 };
@@ -1133,7 +1112,7 @@ export const ToolsFunction$outboundSchema: z.ZodType<
 > = z.object({
   description: z.string().optional(),
   name: z.string(),
-  parameters: z.lazy(() => ToolsParameters$outboundSchema).optional(),
+  parameters: z.record(z.any()).optional(),
   strict: z.boolean().optional(),
   type: z.literal("function"),
 });

package/src/models/operations/createtool.ts

@@ -82,13 +82,13 @@ export type RequestBodyCodeTool = {
  */
 export type RequestBodyCodeExecutionTool = {
   /**
-   * Entity storage path in the format: `project/folder/subfolder/...`
+   * Entity storage path.
    *
    * @remarks
    *
-   * The first element identifies the project, followed by nested folders (auto-created as needed).
+   * With workspace-level API keys, use the format `project/folder/subfolder/...`. The first element identifies the project, followed by nested folders (auto-created as needed). Example: `Default/agents`.
    *
-   * With project-based API keys, the first element is treated as a folder name, as the project is predetermined by the API key.
+   * With project-level API keys, the project is predetermined by the API key, so the path is relative to that project. Example: `agents`. For backward compatibility, a leading project name is ignored when it matches the scoped project.
    */
   path: string;
   /**
@@ -166,13 +166,13 @@ export type RequestBodyMcp = {
  */
 export type RequestBodyMCPTool = {
   /**
-   * Entity storage path in the format: `project/folder/subfolder/...`
+   * Entity storage path.
    *
    * @remarks
    *
-   * The first element identifies the project, followed by nested folders (auto-created as needed).
+   * With workspace-level API keys, use the format `project/folder/subfolder/...`. The first element identifies the project, followed by nested folders (auto-created as needed). Example: `Default/agents`.
    *
-   * With project-based API keys, the first element is treated as a folder name, as the project is predetermined by the API key.
+   * With project-level API keys, the project is predetermined by the API key, so the path is relative to that project. Example: `agents`. For backward compatibility, a leading project name is ignored when it matches the scoped project.
    */
   path: string;
   /**
@@ -312,13 +312,13 @@ export type CreateToolRequestBodyHttp = {
  */
 export type RequestBodyHTTPTool = {
   /**
-   * Entity storage path in the format: `project/folder/subfolder/...`
+   * Entity storage path.
    *
    * @remarks
    *
-   * The first element identifies the project, followed by nested folders (auto-created as needed).
+   * With workspace-level API keys, use the format `project/folder/subfolder/...`. The first element identifies the project, followed by nested folders (auto-created as needed). Example: `Default/agents`.
    *
-   * With project-based API keys, the first element is treated as a folder name, as the project is predetermined by the API key.
+   * With project-level API keys, the project is predetermined by the API key, so the path is relative to that project. Example: `agents`. For backward compatibility, a leading project name is ignored when it matches the scoped project.
    */
   path: string;
   /**
@@ -398,13 +398,13 @@ export type RequestBodyJsonSchema = {
  */
 export type RequestBodyJSONSchemaTool = {
   /**
-   * Entity storage path in the format: `project/folder/subfolder/...`
+   * Entity storage path.
    *
    * @remarks
    *
-   * The first element identifies the project, followed by nested folders (auto-created as needed).
+   * With workspace-level API keys, use the format `project/folder/subfolder/...`. The first element identifies the project, followed by nested folders (auto-created as needed). Example: `Default/agents`.
    *
-   * With project-based API keys, the first element is treated as a folder name, as the project is predetermined by the API key.
+   * With project-level API keys, the project is predetermined by the API key, so the path is relative to that project. Example: `agents`. For backward compatibility, a leading project name is ignored when it matches the scoped project.
    */
   path: string;
   /**
@@ -499,13 +499,13 @@ export type RequestBodyFunction = {
  */
 export type RequestBodyFunctionTool = {
   /**
-   * Entity storage path in the format: `project/folder/subfolder/...`
+   * Entity storage path.
    *
    * @remarks
    *
-   * The first element identifies the project, followed by nested folders (auto-created as needed).
+   * With workspace-level API keys, use the format `project/folder/subfolder/...`. The first element identifies the project, followed by nested folders (auto-created as needed). Example: `Default/agents`.
    *
-   * With project-based API keys, the first element is treated as a folder name, as the project is predetermined by the API key.
+   * With project-level API keys, the project is predetermined by the API key, so the path is relative to that project. Example: `agents`. For backward compatibility, a leading project name is ignored when it matches the scoped project.
    */
   path: string;
   /**
@@ -608,13 +608,13 @@ export type ResponseBodyCodeTool = {
 export type ResponseBodyCodeExecutionTool = {
   id: string;
   /**
-   * Entity storage path in the format: `project/folder/subfolder/...`
+   * Entity storage path.
    *
    * @remarks
    *
-   * The first element identifies the project, followed by nested folders (auto-created as needed).
+   * With workspace-level API keys, use the format `project/folder/subfolder/...`. The first element identifies the project, followed by nested folders (auto-created as needed). Example: `Default/agents`.
    *
-   * With project-based API keys, the first element is treated as a folder name, as the project is predetermined by the API key.
+   * With project-level API keys, the project is predetermined by the API key, so the path is relative to that project. Example: `agents`. For backward compatibility, a leading project name is ignored when it matches the scoped project.
    */
   path: string;
   /**
@@ -732,13 +732,13 @@ export type ResponseBodyMcp = {
 export type ResponseBodyMCPTool = {
   id: string;
   /**
-   * Entity storage path in the format: `project/folder/subfolder/...`
+   * Entity storage path.
    *
    * @remarks
    *
-   * The first element identifies the project, followed by nested folders (auto-created as needed).
+   * With workspace-level API keys, use the format `project/folder/subfolder/...`. The first element identifies the project, followed by nested folders (auto-created as needed). Example: `Default/agents`.
    *
-   * With project-based API keys, the first element is treated as a folder name, as the project is predetermined by the API key.
+   * With project-level API keys, the project is predetermined by the API key, so the path is relative to that project. Example: `agents`. For backward compatibility, a leading project name is ignored when it matches the scoped project.
    */
   path: string;
   /**
@@ -889,13 +889,13 @@ export type CreateToolResponseBodyHttp = {
 export type ResponseBodyHTTPTool = {
   id: string;
   /**
-   * Entity storage path in the format: `project/folder/subfolder/...`
+   * Entity storage path.
    *
    * @remarks
    *
-   * The first element identifies the project, followed by nested folders (auto-created as needed).
+   * With workspace-level API keys, use the format `project/folder/subfolder/...`. The first element identifies the project, followed by nested folders (auto-created as needed). Example: `Default/agents`.
    *
-   * With project-based API keys, the first element is treated as a folder name, as the project is predetermined by the API key.
+   * With project-level API keys, the project is predetermined by the API key, so the path is relative to that project. Example: `agents`. For backward compatibility, a leading project name is ignored when it matches the scoped project.
    */
   path: string;
   /**
@@ -990,13 +990,13 @@ export type ResponseBodyJsonSchema = {
 export type ResponseBodyJSONSchemaTool = {
   id: string;
   /**
-   * Entity storage path in the format: `project/folder/subfolder/...`
+   * Entity storage path.
    *
    * @remarks
    *
-   * The first element identifies the project, followed by nested folders (auto-created as needed).
+   * With workspace-level API keys, use the format `project/folder/subfolder/...`. The first element identifies the project, followed by nested folders (auto-created as needed). Example: `Default/agents`.
    *
-   * With project-based API keys, the first element is treated as a folder name, as the project is predetermined by the API key.
+   * With project-level API keys, the project is predetermined by the API key, so the path is relative to that project. Example: `agents`. For backward compatibility, a leading project name is ignored when it matches the scoped project.
    */
   path: string;
   /**
@@ -1101,13 +1101,13 @@ export type CreateToolResponseBodyFunction = {
 export type ResponseBodyFunctionTool = {
   id: string;
   /**
-   * Entity storage path in the format: `project/folder/subfolder/...`
+   * Entity storage path.
    *
    * @remarks
    *
-   * The first element identifies the project, followed by nested folders (auto-created as needed).
+   * With workspace-level API keys, use the format `project/folder/subfolder/...`. The first element identifies the project, followed by nested folders (auto-created as needed). Example: `Default/agents`.
    *
-   * With project-based API keys, the first element is treated as a folder name, as the project is predetermined by the API key.
+   * With project-level API keys, the project is predetermined by the API key, so the path is relative to that project. Example: `agents`. For backward compatibility, a leading project name is ignored when it matches the scoped project.
    */
   path: string;
   /**
@@ -1902,7 +1902,7 @@ export const ResponseBodyCodeExecutionTool$inboundSchema: z.ZodType<
   z.ZodTypeDef,
   unknown
 > = z.object({
-  _id: z.string().default("tool_01KRGKTFRQCNNSSKKHKV73MHMJ"),
+  _id: z.string().default("tool_01KS23X22SSDAN6SBNVN8TZN1G"),
   path: z.string(),
   key: z.string(),
   display_name: z.string().optional(),
@@ -1999,7 +1999,7 @@ export const ResponseBodyTools$inboundSchema: z.ZodType<
   z.ZodTypeDef,
   unknown
 > = z.object({
-  id: z.string().default("01KRGKTFRPGJAEYNXY903FX8TH"),
+  id: z.string().default("01KS23X22R1GG1CFXXKJT8QGAR"),
   name: z.string(),
   description: z.string().optional(),
   schema: z.lazy(() => CreateToolResponseBodySchema$inboundSchema),
@@ -2055,7 +2055,7 @@ export const ResponseBodyMCPTool$inboundSchema: z.ZodType<
   z.ZodTypeDef,
   unknown
 > = z.object({
-  _id: z.string().default("tool_01KRGKTFRNQ9320P04M2VCZTJD"),
+  _id: z.string().default("tool_01KS23X22QVRZ2XYPDZG9DD61P"),
   path: z.string(),
   key: z.string(),
   display_name: z.string().optional(),
@@ -2241,7 +2241,7 @@ export const ResponseBodyHTTPTool$inboundSchema: z.ZodType<
   z.ZodTypeDef,
   unknown
 > = z.object({
-  _id: z.string().default("tool_01KRGKTFRKTB59YNSGE9DS1XAQ"),
+  _id: z.string().default("tool_01KS23X22PAYX8C9SR3CV09D4A"),
   path: z.string(),
   key: z.string(),
   display_name: z.string().optional(),
@@ -2334,7 +2334,7 @@ export const ResponseBodyJSONSchemaTool$inboundSchema: z.ZodType<
   z.ZodTypeDef,
   unknown
 > = z.object({
-  _id: z.string().default("tool_01KRGKTFRJR6NWKQ0ZVY49NE21"),
+  _id: z.string().default("tool_01KS23X22NVDJY7BNHVN8P8A2S"),
   path: z.string(),
   key: z.string(),
   display_name: z.string().optional(),
@@ -2435,7 +2435,7 @@ export const ResponseBodyFunctionTool$inboundSchema: z.ZodType<
   z.ZodTypeDef,
   unknown
 > = z.object({
-  _id: z.string().default("tool_01KRGKTFRGSXFGQVAM16CPFJ3C"),
+  _id: z.string().default("tool_01KS23X22M1VQ4244MP11CPGGE"),
   path: z.string(),
   key: z.string(),
   display_name: z.string().optional(),

package/src/models/operations/deleteidentity.ts

@@ -5,9 +5,6 @@
 import * as z from "zod/v3";
 
 export type DeleteIdentityRequest = {
-  /**
-   * Identity ID or External ID
-   */
   id: string;
 };