@orq-ai/node 4.10.0-rc.1 → 4.10.0-rc.11

package/src/models/operations/updateeval.ts

@@ -1541,8 +1541,8 @@ export const ResponseBodyTypescript$inboundSchema: z.ZodType<
 > = z.object({
   _id: z.string(),
   description: z.string(),
-  created: z.string().default("2026-05-13T09:57:01.760Z"),
-  updated: z.string().default("2026-05-13T09:57:01.760Z"),
+  created: z.string().default("2026-05-18T05:04:24.675Z"),
+  updated: z.string().default("2026-05-18T05:04:24.675Z"),
   guardrail_config: z.nullable(
     z.union([
       z.lazy(() =>
@@ -1735,8 +1735,8 @@ export const ResponseBodyRagas$inboundSchema: z.ZodType<
 > = z.object({
   _id: z.string(),
   description: z.string(),
-  created: z.string().default("2026-05-13T09:57:01.760Z"),
-  updated: z.string().default("2026-05-13T09:57:01.760Z"),
+  created: z.string().default("2026-05-18T05:04:24.675Z"),
+  updated: z.string().default("2026-05-18T05:04:24.675Z"),
   guardrail_config: z.nullable(
     z.union([
       z.lazy(() =>
@@ -2592,8 +2592,8 @@ export const ResponseBodyFunction$inboundSchema: z.ZodType<
 > = z.object({
   _id: z.string(),
   description: z.string(),
-  created: z.string().default("2026-05-13T09:57:01.760Z"),
-  updated: z.string().default("2026-05-13T09:57:01.760Z"),
+  created: z.string().default("2026-05-18T05:04:24.675Z"),
+  updated: z.string().default("2026-05-18T05:04:24.675Z"),
   guardrail_config: z.nullable(
     z.union([
       z.lazy(() =>
@@ -2809,8 +2809,8 @@ export const UpdateEvalResponseBodyPython$inboundSchema: z.ZodType<
 > = z.object({
   _id: z.string(),
   description: z.string(),
-  created: z.string().default("2026-05-13T09:57:01.760Z"),
-  updated: z.string().default("2026-05-13T09:57:01.760Z"),
+  created: z.string().default("2026-05-18T05:04:24.675Z"),
+  updated: z.string().default("2026-05-18T05:04:24.675Z"),
   guardrail_config: z.nullable(
     z.union([
       z.lazy(() => UpdateEvalGuardrailConfigEvalsResponseBoolean$inboundSchema),
@@ -2976,8 +2976,8 @@ export const UpdateEvalResponseBodyHTTP$inboundSchema: z.ZodType<
 > = z.object({
   _id: z.string(),
   description: z.string(),
-  created: z.string().default("2026-05-13T09:57:01.760Z"),
-  updated: z.string().default("2026-05-13T09:57:01.760Z"),
+  created: z.string().default("2026-05-18T05:04:24.675Z"),
+  updated: z.string().default("2026-05-18T05:04:24.675Z"),
   guardrail_config: z.nullable(
     z.union([
       z.lazy(() => UpdateEvalGuardrailConfigEvalsBoolean$inboundSchema),
@@ -3128,8 +3128,8 @@ export const UpdateEvalResponseBodyJSON$inboundSchema: z.ZodType<
 > = z.object({
   _id: z.string(),
   description: z.string(),
-  created: z.string().default("2026-05-13T09:57:01.760Z"),
-  updated: z.string().default("2026-05-13T09:57:01.760Z"),
+  created: z.string().default("2026-05-18T05:04:24.675Z"),
+  updated: z.string().default("2026-05-18T05:04:24.675Z"),
   guardrail_config: z.nullable(
     z.union([
       z.lazy(() => UpdateEvalGuardrailConfigBoolean$inboundSchema),
@@ -3489,8 +3489,8 @@ export const UpdateEvalLlm2$inboundSchema: z.ZodType<
 > = z.object({
   _id: z.string(),
   description: z.string(),
-  created: z.string().default("2026-05-13T09:57:01.760Z"),
-  updated: z.string().default("2026-05-13T09:57:01.760Z"),
+  created: z.string().default("2026-05-18T05:04:24.675Z"),
+  updated: z.string().default("2026-05-18T05:04:24.675Z"),
   guardrail_config: z.nullable(
     z.union([
       z.lazy(() =>
@@ -3698,8 +3698,8 @@ export const UpdateEvalLlm1$inboundSchema: z.ZodType<
 > = z.object({
   _id: z.string(),
   description: z.string(),
-  created: z.string().default("2026-05-13T09:57:01.760Z"),
-  updated: z.string().default("2026-05-13T09:57:01.760Z"),
+  created: z.string().default("2026-05-18T05:04:24.675Z"),
+  updated: z.string().default("2026-05-18T05:04:24.675Z"),
   guardrail_config: z.nullable(
     z.union([
       z.lazy(() =>

package/src/models/operations/updateidentity.ts

@@ -4,128 +4,17 @@
 
 import * as z from "zod/v3";
 import { remap as remap$ } from "../../lib/primitives.js";
-import { safeParse } from "../../lib/schemas.js";
-import { Result as SafeParseResult } from "../../types/fp.js";
-import { SDKValidationError } from "../errors/sdkvalidationerror.js";
-
-/**
- * Identity fields to update
- */
-export type UpdateIdentityRequestBody = {
-  /**
-   * Display name or nickname of the contact user. This is typically shown in user interfaces.
-   */
-  displayName?: string | null | undefined;
-  /**
-   * Email address of the contact user
-   */
-  email?: string | null | undefined;
-  /**
-   * URL linking to the contact user's avatar image
-   */
-  avatarUrl?: string | null | undefined;
-  /**
-   * Array of tags associated with the contact. Useful for organizing and filtering contacts by categories, departments, or custom classifications.
-   */
-  tags?: Array<string> | undefined;
-  /**
-   * Additional custom metadata associated with the contact as key-value pairs. Use this to store any extra information specific to your application.
-   */
-  metadata?: { [k: string]: any } | undefined;
-};
+import * as components from "../components/index.js";
 
 export type UpdateIdentityRequest = {
-  /**
-   * Unique identity id or external id
-   */
   id: string;
-  /**
-   * Identity fields to update
-   */
-  requestBody?: UpdateIdentityRequestBody | undefined;
+  updateIdentityRequest: components.UpdateIdentityRequest;
 };
 
-/**
- * Updated identity
- */
-export type UpdateIdentityResponseBody = {
-  /**
-   * Unique ULID (Universally Unique Lexicographically Sortable Identifier) for the contact
-   */
-  id: string;
-  /**
-   * Unique string value to identify the contact user in the customer's system. This should be the same ID you use in your system to reference this user.
-   */
-  externalId: string;
-  /**
-   * Display name or nickname of the contact user. This is typically shown in user interfaces.
-   */
-  displayName?: string | null | undefined;
-  /**
-   * Email address of the contact user
-   */
-  email?: string | null | undefined;
-  /**
-   * URL linking to the contact user's avatar image
-   */
-  avatarUrl?: string | null | undefined;
-  /**
-   * Array of tags associated with the contact. Useful for organizing and filtering contacts by categories, departments, or custom classifications.
-   */
-  tags?: Array<string> | undefined;
-  /**
-   * Additional custom metadata associated with the contact as key-value pairs. Use this to store any extra information specific to your application.
-   */
-  metadata?: { [k: string]: any } | undefined;
-  /**
-   * The date and time the resource was created
-   */
-  created?: Date | undefined;
-  /**
-   * The date and time the resource was last updated
-   */
-  updated: Date;
-};
-
-/** @internal */
-export type UpdateIdentityRequestBody$Outbound = {
-  display_name?: string | null | undefined;
-  email?: string | null | undefined;
-  avatar_url?: string | null | undefined;
-  tags?: Array<string> | undefined;
-  metadata?: { [k: string]: any } | undefined;
-};
-
-/** @internal */
-export const UpdateIdentityRequestBody$outboundSchema: z.ZodType<
-  UpdateIdentityRequestBody$Outbound,
-  z.ZodTypeDef,
-  UpdateIdentityRequestBody
-> = z.object({
-  displayName: z.nullable(z.string()).optional(),
-  email: z.nullable(z.string()).optional(),
-  avatarUrl: z.nullable(z.string()).optional(),
-  tags: z.array(z.string()).optional(),
-  metadata: z.record(z.any()).optional(),
-}).transform((v) => {
-  return remap$(v, {
-    displayName: "display_name",
-    avatarUrl: "avatar_url",
-  });
-});
-
-export function updateIdentityRequestBodyToJSON(
-  updateIdentityRequestBody: UpdateIdentityRequestBody,
-): string {
-  return JSON.stringify(
-    UpdateIdentityRequestBody$outboundSchema.parse(updateIdentityRequestBody),
-  );
-}
-
 /** @internal */
 export type UpdateIdentityRequest$Outbound = {
   id: string;
-  RequestBody?: UpdateIdentityRequestBody$Outbound | undefined;
+  UpdateIdentityRequest: components.UpdateIdentityRequest$Outbound;
 };
 
 /** @internal */
@@ -135,11 +24,10 @@ export const UpdateIdentityRequest$outboundSchema: z.ZodType<
   UpdateIdentityRequest
 > = z.object({
   id: z.string(),
-  requestBody: z.lazy(() => UpdateIdentityRequestBody$outboundSchema)
-    .optional(),
+  updateIdentityRequest: components.UpdateIdentityRequest$outboundSchema,
 }).transform((v) => {
   return remap$(v, {
-    requestBody: "RequestBody",
+    updateIdentityRequest: "UpdateIdentityRequest",
   });
 });
 
@@ -150,40 +38,3 @@ export function updateIdentityRequestToJSON(
     UpdateIdentityRequest$outboundSchema.parse(updateIdentityRequest),
   );
 }
-
-/** @internal */
-export const UpdateIdentityResponseBody$inboundSchema: z.ZodType<
-  UpdateIdentityResponseBody,
-  z.ZodTypeDef,
-  unknown
-> = z.object({
-  _id: z.string(),
-  external_id: z.string(),
-  display_name: z.nullable(z.string()).optional(),
-  email: z.nullable(z.string()).optional(),
-  avatar_url: z.nullable(z.string()).optional(),
-  tags: z.array(z.string()).optional(),
-  metadata: z.record(z.any()).optional(),
-  created: z.string().datetime({ offset: true }).transform(v => new Date(v))
-    .optional(),
-  updated: z.string().datetime({ offset: true }).default(
-    "2026-05-13T09:56:59.680Z",
-  ).transform(v => new Date(v)),
-}).transform((v) => {
-  return remap$(v, {
-    "_id": "id",
-    "external_id": "externalId",
-    "display_name": "displayName",
-    "avatar_url": "avatarUrl",
-  });
-});
-
-export function updateIdentityResponseBodyFromJSON(
-  jsonString: string,
-): SafeParseResult<UpdateIdentityResponseBody, SDKValidationError> {
-  return safeParse(
-    jsonString,
-    (x) => UpdateIdentityResponseBody$inboundSchema.parse(JSON.parse(x)),
-    `Failed to parse 'UpdateIdentityResponseBody' from JSON`,
-  );
-}

package/src/models/operations/updateknowledge.ts

@@ -98,13 +98,13 @@ export type UpdateKnowledgeRequestBody2 = {
    */
   embeddingModel?: 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 | undefined;
   /**
@@ -195,13 +195,13 @@ export type UpdateKnowledgeRequestBody1 = {
    */
   description?: string | null | 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 | undefined;
   /**
@@ -323,13 +323,13 @@ export type UpdateKnowledgeResponseBody2 = {
    */
   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;
@@ -449,13 +449,13 @@ export type UpdateKnowledgeResponseBody1 = {
    */
   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/updateprompt.ts

@@ -879,13 +879,13 @@ export type UpdatePromptRequestBody = {
   prompt?: UpdatePromptPromptInput | undefined;
   metadata?: UpdatePromptMetadata | 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 | undefined;
 };

package/src/models/operations/updatetool.ts

@@ -93,13 +93,13 @@ export type UpdateToolRequestBodyToolsRequest5VersionIncrement = ClosedEnum<
  */
 export type UpdateCodeExecutionTool = {
   /**
-   * 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;
   /**
@@ -214,13 +214,13 @@ export type UpdateToolRequestBodyToolsRequestVersionIncrement = ClosedEnum<
  */
 export type UpdateMCPTool = {
   /**
-   * 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;
   /**
@@ -373,13 +373,13 @@ export type UpdateToolRequestBodyToolsVersionIncrement = ClosedEnum<
  */
 export type UpdateHTTPTool = {
   /**
-   * 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;
   /**
@@ -472,13 +472,13 @@ export type UpdateToolRequestBodyVersionIncrement = ClosedEnum<
  */
 export type UpdateJSONSchemaTool = {
   /**
-   * 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;
   /**
@@ -584,13 +584,13 @@ export type RequestBodyVersionIncrement = ClosedEnum<
  */
 export type UpdateFunctionTool = {
   /**
-   * 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;
   /**
@@ -712,13 +712,13 @@ export type UpdateToolResponseBodyCodeTool = {
 export type UpdateToolResponseBodyCodeExecutionTool = {
   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;
   /**
@@ -836,13 +836,13 @@ export type UpdateToolResponseBodyMcp = {
 export type UpdateToolResponseBodyMCPTool = {
   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;
   /**
@@ -995,13 +995,13 @@ export type UpdateToolResponseBodyHttp = {
 export type UpdateToolResponseBodyHTTPTool = {
   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;
   /**
@@ -1096,13 +1096,13 @@ export type UpdateToolResponseBodyJsonSchema = {
 export type UpdateToolResponseBodyJSONSchemaTool = {
   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;
   /**
@@ -1209,13 +1209,13 @@ export type UpdateToolResponseBodyFunction = {
 export type UpdateToolResponseBodyFunctionTool = {
   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;
   /**
@@ -1472,7 +1472,7 @@ export const RequestBodyTools$outboundSchema: z.ZodType<
   z.ZodTypeDef,
   RequestBodyTools
 > = z.object({
-  id: z.string().default("01KRGC9RM6PR9S58NXPT0ZAW19"),
+  id: z.string().default("01KRWQHHRT6T21RWYF5D1E77PS"),
   name: z.string(),
   description: z.string().optional(),
   schema: z.lazy(() => UpdateToolRequestBodyToolsSchema$outboundSchema),
@@ -2193,7 +2193,7 @@ export const UpdateToolResponseBodyCodeExecutionTool$inboundSchema: z.ZodType<
   z.ZodTypeDef,
   unknown
 > = z.object({
-  _id: z.string().default("tool_01KRGC9RKS847BRKK3P3JWT1D1"),
+  _id: z.string().default("tool_01KRWQHHRN89ET5EPKQ9EA8NYF"),
   path: z.string(),
   key: z.string(),
   display_name: z.string().optional(),
@@ -2296,7 +2296,7 @@ export const UpdateToolResponseBodyTools$inboundSchema: z.ZodType<
   z.ZodTypeDef,
   unknown
 > = z.object({
-  id: z.string().default("01KRGC9RKRTK7TD27KSHV4DPXR"),
+  id: z.string().default("01KRWQHHRM8Q1Z3FHCFNJ9C918"),
   name: z.string(),
   description: z.string().optional(),
   schema: z.lazy(() => UpdateToolResponseBodyToolsSchema$inboundSchema),
@@ -2354,7 +2354,7 @@ export const UpdateToolResponseBodyMCPTool$inboundSchema: z.ZodType<
   z.ZodTypeDef,
   unknown
 > = z.object({
-  _id: z.string().default("tool_01KRGC9RKQ3JND8K04NP5RZW67"),
+  _id: z.string().default("tool_01KRWQHHRKN0BJKGX95XFG2WBM"),
   path: z.string(),
   key: z.string(),
   display_name: z.string().optional(),
@@ -2543,7 +2543,7 @@ export const UpdateToolResponseBodyHTTPTool$inboundSchema: z.ZodType<
   z.ZodTypeDef,
   unknown
 > = z.object({
-  _id: z.string().default("tool_01KRGC9RKNT8SFNPV26D293Y2D"),
+  _id: z.string().default("tool_01KRWQHHRJZGTBNV71QF2Q44WX"),
   path: z.string(),
   key: z.string(),
   display_name: z.string().optional(),
@@ -2638,7 +2638,7 @@ export const UpdateToolResponseBodyJSONSchemaTool$inboundSchema: z.ZodType<
   z.ZodTypeDef,
   unknown
 > = z.object({
-  _id: z.string().default("tool_01KRGC9RKM93EQ66YNF4C4WHJH"),
+  _id: z.string().default("tool_01KRWQHHRHE2DK6H42YA271WZA"),
   path: z.string(),
   key: z.string(),
   display_name: z.string().optional(),
@@ -2741,7 +2741,7 @@ export const UpdateToolResponseBodyFunctionTool$inboundSchema: z.ZodType<
   z.ZodTypeDef,
   unknown
 > = z.object({
-  _id: z.string().default("tool_01KRGC9RKKC1BG283XG4GQ71J8"),
+  _id: z.string().default("tool_01KRWQHHRFXS9AFM3JYB1PRGW6"),
   path: z.string(),
   key: z.string(),
   display_name: z.string().optional(),

package/src/sdk/feedback.ts

@@ -9,22 +9,22 @@ import * as operations from "../models/operations/index.js";
 import { unwrapAsync } from "../types/fp.js";
 
 export class Feedback extends ClientSDK {
-  async postV2Feedback(
-    request?: operations.PostV2FeedbackRequestBody | undefined,
+  async postV2FeedbackRemove(
+    request?: operations.PostV2FeedbackRemoveRequestBody | undefined,
     options?: RequestOptions,
-  ): Promise<operations.PostV2FeedbackResponseBody> {
-    return unwrapAsync(feedbackPostV2Feedback(
+  ): Promise<operations.PostV2FeedbackRemoveResponseBody> {
+    return unwrapAsync(feedbackPostV2FeedbackRemove(
       this,
       request,
       options,
     ));
   }
 
-  async postV2FeedbackRemove(
-    request?: operations.PostV2FeedbackRemoveRequestBody | undefined,
+  async postV2Feedback(
+    request?: operations.PostV2FeedbackRequestBody | undefined,
     options?: RequestOptions,
-  ): Promise<operations.PostV2FeedbackRemoveResponseBody> {
-    return unwrapAsync(feedbackPostV2FeedbackRemove(
+  ): Promise<operations.PostV2FeedbackResponseBody> {
+    return unwrapAsync(feedbackPostV2Feedback(
       this,
       request,
       options,