@orq-ai/node 4.9.4 → 4.9.7

package/models/operations/updateknowledge.d.ts

@@ -79,13 +79,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;
     /**
@@ -168,13 +168,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;
     /**
@@ -278,13 +278,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;
@@ -389,13 +389,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/models/operations/updateprompt.d.ts

@@ -740,13 +740,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/models/operations/updatetool.d.ts

@@ -73,13 +73,13 @@ export type UpdateToolRequestBodyToolsRequest5VersionIncrement = ClosedEnum<type
  */
 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;
     /**
@@ -179,13 +179,13 @@ export type UpdateToolRequestBodyToolsRequestVersionIncrement = ClosedEnum<typeo
  */
 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;
     /**
@@ -325,13 +325,13 @@ export type UpdateToolRequestBodyToolsVersionIncrement = ClosedEnum<typeof Updat
  */
 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;
     /**
@@ -419,13 +419,13 @@ export type UpdateToolRequestBodyVersionIncrement = ClosedEnum<typeof UpdateTool
  */
 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;
     /**
@@ -523,13 +523,13 @@ export type RequestBodyVersionIncrement = ClosedEnum<typeof RequestBodyVersionIn
  */
 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;
     /**
@@ -630,13 +630,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;
     /**
@@ -745,13 +745,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;
     /**
@@ -893,13 +893,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;
     /**
@@ -992,13 +992,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;
     /**
@@ -1101,13 +1101,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;
     /**

package/models/operations/updatetool.js

@@ -371,7 +371,7 @@ function updateToolRequestBodyToolsSchemaToJSON(updateToolRequestBodyToolsSchema
 }
 /** @internal */
 exports.RequestBodyTools$outboundSchema = z.object({
-    id: z.string().default("01KRNM0V9NENEQ46BH157G2PPJ"),
+    id: z.string().default("01KRXPE59H38RX3EX8WF4TYKNT"),
     name: z.string(),
     description: z.string().optional(),
     schema: z.lazy(() => exports.UpdateToolRequestBodyToolsSchema$outboundSchema),
@@ -666,7 +666,7 @@ function updateToolResponseBodyCodeToolFromJSON(jsonString) {
 }
 /** @internal */
 exports.UpdateToolResponseBodyCodeExecutionTool$inboundSchema = z.object({
-    _id: z.string().default("tool_01KRNM0V9GBRE6KQT4X9JPCM07"),
+    _id: z.string().default("tool_01KRXPE59DYFNR7AACX74ERCK6"),
     path: z.string(),
     key: z.string(),
     display_name: z.string().optional(),
@@ -719,7 +719,7 @@ function updateToolResponseBodyToolsSchemaFromJSON(jsonString) {
 }
 /** @internal */
 exports.UpdateToolResponseBodyTools$inboundSchema = z.object({
-    id: z.string().default("01KRNM0V9G7P05X3H83ZG38FAC"),
+    id: z.string().default("01KRXPE59CE7S0J5BSGNQDYCM7"),
     name: z.string(),
     description: z.string().optional(),
     schema: z.lazy(() => exports.UpdateToolResponseBodyToolsSchema$inboundSchema),
@@ -749,7 +749,7 @@ function updateToolResponseBodyMcpFromJSON(jsonString) {
 }
 /** @internal */
 exports.UpdateToolResponseBodyMCPTool$inboundSchema = z.object({
-    _id: z.string().default("tool_01KRNM0V9FQRCW83QQSX0YRTGX"),
+    _id: z.string().default("tool_01KRXPE59B1HEFMZYG21Y5H5QP"),
     path: z.string(),
     key: z.string(),
     display_name: z.string().optional(),
@@ -836,7 +836,7 @@ function updateToolResponseBodyHttpFromJSON(jsonString) {
 }
 /** @internal */
 exports.UpdateToolResponseBodyHTTPTool$inboundSchema = z.object({
-    _id: z.string().default("tool_01KRNM0V9DY4T9A07TV5WTMWGP"),
+    _id: z.string().default("tool_01KRXPE59AFBEANJD6FT33BG9E"),
     path: z.string(),
     key: z.string(),
     display_name: z.string().optional(),
@@ -886,7 +886,7 @@ function updateToolResponseBodyJsonSchemaFromJSON(jsonString) {
 }
 /** @internal */
 exports.UpdateToolResponseBodyJSONSchemaTool$inboundSchema = z.object({
-    _id: z.string().default("tool_01KRNM0V9CQMM1R594T4P25RBV"),
+    _id: z.string().default("tool_01KRXPE5993DDVAT5TSAG19J9F"),
     path: z.string(),
     key: z.string(),
     display_name: z.string().optional(),
@@ -940,7 +940,7 @@ function updateToolResponseBodyFunctionFromJSON(jsonString) {
 }
 /** @internal */
 exports.UpdateToolResponseBodyFunctionTool$inboundSchema = z.object({
-    _id: z.string().default("tool_01KRNM0V9BFR8YHD54BG9NHS8X"),
+    _id: z.string().default("tool_01KRXPE598NC2BH43E58KASD93"),
     path: z.string(),
     key: z.string(),
     display_name: z.string().optional(),

package/package.json

@@ -1,9 +1,8 @@
 {
   "name": "@orq-ai/node",
-  "version": "4.9.4",
+  "version": "4.9.7",
   "author": "Orq",
   "exports": {
-    "./*": "./*",
     "./langchain": {
       "import": "./langchain/index.mjs",
       "require": "./langchain/index.js",
@@ -13,7 +12,8 @@
       "import": "./index.js",
       "require": "./index.js",
       "types": "./index.d.ts"
-    }
+    },
+    "./*": "./*"
   },
   "main": "./index.js",
   "sideEffects": false,

package/packages/orq-rc/src/funcs/identitiesCreate.ts

@@ -11,6 +11,7 @@ import { safeParse } from "../lib/schemas.js";
 import { RequestOptions } from "../lib/sdks.js";
 import { extractSecurity, resolveGlobalSecurity } from "../lib/security.js";
 import { pathToFunc } from "../lib/url.js";
+import * as components from "../models/components/index.js";
 import {
   ConnectionError,
   InvalidRequestError,
@@ -21,7 +22,6 @@ import {
 import { OrqError } from "../models/errors/orqerror.js";
 import { ResponseValidationError } from "../models/errors/responsevalidationerror.js";
 import { SDKValidationError } from "../models/errors/sdkvalidationerror.js";
-import * as operations from "../models/operations/index.js";
 import { APICall, APIPromise } from "../types/async.js";
 import { Result } from "../types/fp.js";
 
@@ -29,15 +29,15 @@ import { Result } from "../types/fp.js";
  * Create an identity
  *
  * @remarks
- * Creates a new identity with a unique external_id. If an identity with the same external_id already exists, the operation will fail. Use this endpoint to add users from your system to orq.ai for tracking their usage and engagement.
+ * Creates a new identity with a unique external_id. If an identity with the same external_id already exists, the operation will fail.
  */
 export function identitiesCreate(
   client: OrqCore,
-  request?: operations.CreateIdentityRequestBody | undefined,
+  request: components.CreateIdentityRequest,
   options?: RequestOptions,
 ): APIPromise<
   Result<
-    operations.CreateIdentityResponseBody,
+    components.CreateIdentityResponse,
     | OrqError
     | ResponseValidationError
     | ConnectionError
@@ -57,12 +57,12 @@ export function identitiesCreate(
 
 async function $do(
   client: OrqCore,
-  request?: operations.CreateIdentityRequestBody | undefined,
+  request: components.CreateIdentityRequest,
   options?: RequestOptions,
 ): Promise<
   [
     Result<
-      operations.CreateIdentityResponseBody,
+      components.CreateIdentityResponse,
       | OrqError
       | ResponseValidationError
       | ConnectionError
@@ -77,19 +77,14 @@ async function $do(
 > {
   const parsed = safeParse(
     request,
-    (value) =>
-      operations.CreateIdentityRequestBody$outboundSchema.optional().parse(
-        value,
-      ),
+    (value) => components.CreateIdentityRequest$outboundSchema.parse(value),
     "Input validation failed",
   );
   if (!parsed.ok) {
     return [parsed, { status: "invalid" }];
   }
   const payload = parsed.value;
-  const body = payload === undefined
-    ? null
-    : encodeJSON("body", payload, { explode: true });
+  const body = encodeJSON("body", payload, { explode: true });
 
   const path = pathToFunc("/v2/identities")();
 
@@ -145,7 +140,7 @@ async function $do(
   const response = doResult.value;
 
   const [result] = await M.match<
-    operations.CreateIdentityResponseBody,
+    components.CreateIdentityResponse,
     | OrqError
     | ResponseValidationError
     | ConnectionError
@@ -155,7 +150,7 @@ async function $do(
     | UnexpectedClientError
     | SDKValidationError
   >(
-    M.json(201, operations.CreateIdentityResponseBody$inboundSchema),
+    M.json(200, components.CreateIdentityResponse$inboundSchema),
     M.fail("4XX"),
     M.fail("5XX"),
   )(response, req);

package/packages/orq-rc/src/funcs/identitiesDelete.ts

@@ -2,7 +2,6 @@
  * Code generated by Speakeasy (https://speakeasy.com). DO NOT EDIT.
  */
 
-import * as z from "zod/v3";
 import { OrqCore } from "../core.js";
 import { encodeSimple } from "../lib/encodings.js";
 import { matchStatusCode } from "../lib/http.js";
@@ -12,6 +11,7 @@ import { safeParse } from "../lib/schemas.js";
 import { RequestOptions } from "../lib/sdks.js";
 import { extractSecurity, resolveGlobalSecurity } from "../lib/security.js";
 import { pathToFunc } from "../lib/url.js";
+import * as components from "../models/components/index.js";
 import {
   ConnectionError,
   InvalidRequestError,
@@ -19,7 +19,6 @@ import {
   RequestTimeoutError,
   UnexpectedClientError,
 } from "../models/errors/httpclienterrors.js";
-import * as errors from "../models/errors/index.js";
 import { OrqError } from "../models/errors/orqerror.js";
 import { ResponseValidationError } from "../models/errors/responsevalidationerror.js";
 import { SDKValidationError } from "../models/errors/sdkvalidationerror.js";
@@ -31,7 +30,7 @@ import { Result } from "../types/fp.js";
  * Delete an identity
  *
  * @remarks
- * Permanently deletes an identity from your workspace and cleans up associated budget configurations. This action cannot be undone.
+ * Permanently deletes an identity from your workspace and cleans up associated budget configurations.
  */
 export function identitiesDelete(
   client: OrqCore,
@@ -39,8 +38,7 @@ export function identitiesDelete(
   options?: RequestOptions,
 ): APIPromise<
   Result<
-    void,
-    | errors.DeleteIdentityResponseBody
+    components.DeleteIdentityResponse,
     | OrqError
     | ResponseValidationError
     | ConnectionError
@@ -65,8 +63,7 @@ async function $do(
 ): Promise<
   [
     Result<
-      void,
-      | errors.DeleteIdentityResponseBody
+      components.DeleteIdentityResponse,
       | OrqError
       | ResponseValidationError
       | ConnectionError
@@ -148,13 +145,8 @@ async function $do(
   }
   const response = doResult.value;
 
-  const responseFields = {
-    HttpMeta: { Response: response, Request: req },
-  };
-
   const [result] = await M.match<
-    void,
-    | errors.DeleteIdentityResponseBody
+    components.DeleteIdentityResponse,
     | OrqError
     | ResponseValidationError
     | ConnectionError
@@ -164,11 +156,10 @@ async function $do(
     | UnexpectedClientError
     | SDKValidationError
   >(
-    M.nil(204, z.void()),
-    M.jsonErr(404, errors.DeleteIdentityResponseBody$inboundSchema),
+    M.json(200, components.DeleteIdentityResponse$inboundSchema),
     M.fail("4XX"),
     M.fail("5XX"),
-  )(response, req, { extraFields: responseFields });
+  )(response, req);
   if (!result.ok) {
     return [result, { status: "complete", request: req, response }];
   }

package/packages/orq-rc/src/funcs/identitiesList.ts

@@ -11,6 +11,7 @@ import { safeParse } from "../lib/schemas.js";
 import { RequestOptions } from "../lib/sdks.js";
 import { extractSecurity, resolveGlobalSecurity } from "../lib/security.js";
 import { pathToFunc } from "../lib/url.js";
+import * as components from "../models/components/index.js";
 import {
   ConnectionError,
   InvalidRequestError,
@@ -37,7 +38,7 @@ export function identitiesList(
   options?: RequestOptions,
 ): APIPromise<
   Result<
-    operations.ListIdentitiesResponseBody,
+    components.ListIdentitiesResponse,
     | OrqError
     | ResponseValidationError
     | ConnectionError
@@ -62,7 +63,7 @@ async function $do(
 ): Promise<
   [
     Result<
-      operations.ListIdentitiesResponseBody,
+      components.ListIdentitiesResponse,
       | OrqError
       | ResponseValidationError
       | ConnectionError
@@ -91,7 +92,7 @@ async function $do(
 
   const query = encodeFormQuery({
     "ending_before": payload?.ending_before,
-    "filter_by": payload?.filter_by,
+    "filter_by.tags": payload?.["filter_by.tags"],
     "include_metrics": payload?.include_metrics,
     "limit": payload?.limit,
     "search": payload?.search,
@@ -150,7 +151,7 @@ async function $do(
   const response = doResult.value;
 
   const [result] = await M.match<
-    operations.ListIdentitiesResponseBody,
+    components.ListIdentitiesResponse,
     | OrqError
     | ResponseValidationError
     | ConnectionError
@@ -160,7 +161,7 @@ async function $do(
     | UnexpectedClientError
     | SDKValidationError
   >(
-    M.json(200, operations.ListIdentitiesResponseBody$inboundSchema),
+    M.json(200, components.ListIdentitiesResponse$inboundSchema),
     M.fail("4XX"),
     M.fail("5XX"),
   )(response, req);

package/packages/orq-rc/src/funcs/identitiesRetrieve.ts

@@ -11,6 +11,7 @@ import { safeParse } from "../lib/schemas.js";
 import { RequestOptions } from "../lib/sdks.js";
 import { extractSecurity, resolveGlobalSecurity } from "../lib/security.js";
 import { pathToFunc } from "../lib/url.js";
+import * as components from "../models/components/index.js";
 import {
   ConnectionError,
   InvalidRequestError,
@@ -18,7 +19,6 @@ import {
   RequestTimeoutError,
   UnexpectedClientError,
 } from "../models/errors/httpclienterrors.js";
-import * as errors from "../models/errors/index.js";
 import { OrqError } from "../models/errors/orqerror.js";
 import { ResponseValidationError } from "../models/errors/responsevalidationerror.js";
 import { SDKValidationError } from "../models/errors/sdkvalidationerror.js";
@@ -38,9 +38,7 @@ export function identitiesRetrieve(
   options?: RequestOptions,
 ): APIPromise<
   Result<
-    operations.RetrieveIdentityResponseBody,
-    | errors.RetrieveIdentityResponseBody
-    | errors.RetrieveIdentityIdentitiesResponseBody
+    components.RetrieveIdentityResponse,
     | OrqError
     | ResponseValidationError
     | ConnectionError
@@ -65,9 +63,7 @@ async function $do(
 ): Promise<
   [
     Result<
-      operations.RetrieveIdentityResponseBody,
-      | errors.RetrieveIdentityResponseBody
-      | errors.RetrieveIdentityIdentitiesResponseBody
+      components.RetrieveIdentityResponse,
       | OrqError
       | ResponseValidationError
       | ConnectionError
@@ -154,14 +150,8 @@ async function $do(
   }
   const response = doResult.value;
 
-  const responseFields = {
-    HttpMeta: { Response: response, Request: req },
-  };
-
   const [result] = await M.match<
-    operations.RetrieveIdentityResponseBody,
-    | errors.RetrieveIdentityResponseBody
-    | errors.RetrieveIdentityIdentitiesResponseBody
+    components.RetrieveIdentityResponse,
     | OrqError
     | ResponseValidationError
     | ConnectionError
@@ -171,12 +161,10 @@ async function $do(
     | UnexpectedClientError
     | SDKValidationError
   >(
-    M.json(200, operations.RetrieveIdentityResponseBody$inboundSchema),
-    M.jsonErr(404, errors.RetrieveIdentityResponseBody$inboundSchema),
-    M.jsonErr(500, errors.RetrieveIdentityIdentitiesResponseBody$inboundSchema),
+    M.json(200, components.RetrieveIdentityResponse$inboundSchema),
     M.fail("4XX"),
     M.fail("5XX"),
-  )(response, req, { extraFields: responseFields });
+  )(response, req);
   if (!result.ok) {
     return [result, { status: "complete", request: req, response }];
   }