@orq-ai/node
v4.1.6
Published
Developer-friendly & type-safe Typescript SDK specifically catered to leverage *@orq-ai/node* API.
Readme
@orq-ai/node
Developer-friendly & type-safe Typescript SDK specifically catered to leverage @orq-ai/node API.
Summary
orq.ai API: orq.ai API documentation
For more information about the API: orq.ai Documentation
Table of Contents
SDK Installation
The SDK can be installed with either npm, pnpm, bun or yarn package managers.
NPM
npm add @orq-ai/nodePNPM
pnpm add @orq-ai/nodeBun
bun add @orq-ai/nodeYarn
yarn add @orq-ai/nodeModel Context Protocol (MCP) Server
This SDK is also an installable MCP server where the various SDK methods are exposed as tools that can be invoked by AI applications.
Node.js v20 or greater is required to run the MCP server from npm.
Add the following server definition to your claude_desktop_config.json file:
{
"mcpServers": {
"Orq": {
"command": "npx",
"args": [
"-y", "--package", "@orq-ai/node",
"--",
"mcp", "start",
"--api-key", "...",
"--contact-id", "...",
"--environment", "..."
]
}
}
}Create a .cursor/mcp.json file in your project root with the following content:
{
"mcpServers": {
"Orq": {
"command": "npx",
"args": [
"-y", "--package", "@orq-ai/node",
"--",
"mcp", "start",
"--api-key", "...",
"--contact-id", "...",
"--environment", "..."
]
}
}
}You can also run MCP servers as a standalone binary with no additional dependencies. You must pull these binaries from available Github releases:
curl -L -o mcp-server \
https://github.com/{org}/{repo}/releases/download/{tag}/mcp-server-bun-darwin-arm64 && \
chmod +x mcp-serverIf the repo is a private repo you must add your Github PAT to download a release -H "Authorization: Bearer {GITHUB_PAT}".
{
"mcpServers": {
"Todos": {
"command": "./DOWNLOAD/PATH/mcp-server",
"args": [
"start"
]
}
}
}For a full list of server arguments, run:
npx -y --package @orq-ai/node -- mcp start --helpRequirements
For supported JavaScript runtimes, please consult RUNTIMES.md.
SDK Example Usage
Example
import { Orq } from "@orq-ai/node";
const orq = new Orq({
apiKey: process.env["ORQ_API_KEY"] ?? "",
});
async function run() {
const result = await orq.contacts.create({
externalId: "user_12345",
displayName: "Jane Smith",
email: "[email protected]",
avatarUrl: "https://example.com/avatars/jane-smith.jpg",
tags: [
"premium",
"beta-user",
"enterprise",
],
metadata: {
"department": "Engineering",
"role": "Senior Developer",
"subscription_tier": "premium",
"last_login": "2024-01-15T10:30:00Z",
},
});
console.log(result);
}
run();
Authentication
Per-Client Security Schemes
This SDK supports the following security scheme globally:
| Name | Type | Scheme | Environment Variable |
| -------- | ---- | ----------- | -------------------- |
| apiKey | http | HTTP Bearer | ORQ_API_KEY |
To authenticate with the API the apiKey parameter must be set when initializing the SDK client instance. For example:
import { Orq } from "@orq-ai/node";
const orq = new Orq({
apiKey: process.env["ORQ_API_KEY"] ?? "",
});
async function run() {
const result = await orq.contacts.create({
externalId: "user_12345",
displayName: "Jane Smith",
email: "[email protected]",
avatarUrl: "https://example.com/avatars/jane-smith.jpg",
tags: [
"premium",
"beta-user",
"enterprise",
],
metadata: {
"department": "Engineering",
"role": "Senior Developer",
"subscription_tier": "premium",
"last_login": "2024-01-15T10:30:00Z",
},
});
console.log(result);
}
run();
Available Resources and Operations
Agents
- create - Create agent
- delete - Delete agent
- retrieve - Retrieve agent
- update - Update agent
- ~~invoke~~ - Execute an agent task :warning: Deprecated
- list - List agents
- ~~run~~ - Run an agent with configuration :warning: Deprecated
- ~~streamRun~~ - Run agent with streaming response :warning: Deprecated
- ~~stream~~ - Stream agent execution in real-time :warning: Deprecated
Agents.Responses
- create - Create response
Chunking
- parse - Parse text
Contacts
- create - Create a contact
- list - List contacts
- retrieve - Retrieve a contact
- update - Update a contact
- delete - Delete a contact
Conversations
- list - List conversations
- create - Create conversation
- generateName - Generate conversation name
- retrieve - Retrieve conversation
- update - Update conversation
- delete - Delete conversation
Datasets
- list - List datasets
- create - Create a dataset
- retrieve - Retrieve a dataset
- update - Update a dataset
- delete - Delete a dataset
- listDatapoints - List datapoints
- createDatapoint - Create a datapoint
- retrieveDatapoint - Retrieve a datapoint
- updateDatapoint - Update a datapoint
- deleteDatapoint - Delete a datapoint
- clear - Delete all datapoints
Deployments
Deployments.Metrics
- create - Add metrics
Evals
- all - Get all Evaluators
- create - Create an Evaluator
- update - Update an Evaluator
- delete - Delete an Evaluator
- invoke - Invoke a Custom Evaluator
Evaluators
- getV2EvaluatorsIdVersions - List evaluator versions
- getV2EvaluatorsIdVersionsVersionId - Get evaluator version
Feedback
- create - Submit feedback
Files
Knowledge
- list - List all knowledge bases
- create - Create a knowledge
- retrieve - Retrieves a knowledge base
- update - Updates a knowledge
- delete - Deletes a knowledge
- search - Search knowledge base
- listDatasources - List all datasources
- createDatasource - Create a new datasource
- retrieveDatasource - Retrieve a datasource
- deleteDatasource - Deletes a datasource
- updateDatasource - Update a datasource
- createChunks - Create chunks for a datasource
- listChunks - List all chunks for a datasource
- deleteChunks - Delete multiple chunks
- listChunksPaginated - List chunks with offset-based pagination
- getChunksCount - Get chunks total count
- updateChunk - Update a chunk
- deleteChunk - Delete a chunk
- retrieveChunk - Retrieve a chunk
MemoryStores
- list - List memory stores
- create - Create memory store
- retrieve - Retrieve memory store
- update - Update memory store
- delete - Delete memory store
- listMemories - List all memories
- createMemory - Create a new memory
- retrieveMemory - Retrieve a specific memory
- updateMemory - Update a specific memory
- deleteMemory - Delete a specific memory
- listDocuments - List all documents for a memory
- createDocument - Create a new memory document
- retrieveDocument - Retrieve a specific memory document
- updateDocument - Update a specific memory document
- deleteDocument - Delete a specific memory document
Models
- list - List models
Prompts
- list - List all prompts
- create - Create a prompt
- retrieve - Retrieve a prompt
- update - Update a prompt
- delete - Delete a prompt
- listVersions - List all prompt versions
- getVersion - Retrieve a prompt version
Remoteconfigs
- retrieve - Retrieve a remote config
Router
- chatCompletions - Create chat completion
- imagesGenerate - Create image
Tools
- list - List tools
- create - Create tool
- update - Update tool
- delete - Delete tool
- retrieve - Retrieve tool
- getV2ToolsToolIdVersions - List tool versions
- getV2ToolsToolIdVersionsVersionId - Get tool version
Standalone functions
All the methods listed above are available as standalone functions. These functions are ideal for use in applications running in the browser, serverless runtimes or other environments where application bundle size is a primary concern. When using a bundler to build your application, all unused functionality will be either excluded from the final bundle or tree-shaken away.
To read more about standalone functions, check FUNCTIONS.md.
agentsCreate- Create agentagentsDelete- Delete agentagentsList- List agentsagentsResponsesCreate- Create responseagentsRetrieve- Retrieve agentagentsUpdate- Update agentchunkingParse- Parse textcontactsCreate- Create a contactcontactsDelete- Delete a contactcontactsList- List contactscontactsRetrieve- Retrieve a contactcontactsUpdate- Update a contactconversationsCreate- Create conversationconversationsDelete- Delete conversationconversationsGenerateName- Generate conversation nameconversationsList- List conversationsconversationsRetrieve- Retrieve conversationconversationsUpdate- Update conversationdatasetsClear- Delete all datapointsdatasetsCreate- Create a datasetdatasetsCreateDatapoint- Create a datapointdatasetsDelete- Delete a datasetdatasetsDeleteDatapoint- Delete a datapointdatasetsList- List datasetsdatasetsListDatapoints- List datapointsdatasetsRetrieve- Retrieve a datasetdatasetsRetrieveDatapoint- Retrieve a datapointdatasetsUpdate- Update a datasetdatasetsUpdateDatapoint- Update a datapointdeploymentsGetConfig- Get configdeploymentsInvoke- InvokedeploymentsList- List all deploymentsdeploymentsMetricsCreate- Add metricsdeploymentsStream- StreamevalsAll- Get all EvaluatorsevalsCreate- Create an EvaluatorevalsDelete- Delete an EvaluatorevalsInvoke- Invoke a Custom EvaluatorevalsUpdate- Update an EvaluatorevaluatorsGetV2EvaluatorsIdVersions- List evaluator versionsevaluatorsGetV2EvaluatorsIdVersionsVersionId- Get evaluator versionfeedbackCreate- Submit feedbackfilesCreate- Create filefilesDelete- Delete filefilesGet- Retrieve a filefilesList- List all filesknowledgeCreate- Create a knowledgeknowledgeCreateChunks- Create chunks for a datasourceknowledgeCreateDatasource- Create a new datasourceknowledgeDelete- Deletes a knowledgeknowledgeDeleteChunk- Delete a chunkknowledgeDeleteChunks- Delete multiple chunksknowledgeDeleteDatasource- Deletes a datasourceknowledgeGetChunksCount- Get chunks total countknowledgeList- List all knowledge basesknowledgeListChunks- List all chunks for a datasourceknowledgeListChunksPaginated- List chunks with offset-based paginationknowledgeListDatasources- List all datasourcesknowledgeRetrieve- Retrieves a knowledge baseknowledgeRetrieveChunk- Retrieve a chunkknowledgeRetrieveDatasource- Retrieve a datasourceknowledgeSearch- Search knowledge baseknowledgeUpdate- Updates a knowledgeknowledgeUpdateChunk- Update a chunkknowledgeUpdateDatasource- Update a datasourcememoryStoresCreate- Create memory storememoryStoresCreateDocument- Create a new memory documentmemoryStoresCreateMemory- Create a new memorymemoryStoresDelete- Delete memory storememoryStoresDeleteDocument- Delete a specific memory documentmemoryStoresDeleteMemory- Delete a specific memorymemoryStoresList- List memory storesmemoryStoresListDocuments- List all documents for a memorymemoryStoresListMemories- List all memoriesmemoryStoresRetrieve- Retrieve memory storememoryStoresRetrieveDocument- Retrieve a specific memory documentmemoryStoresRetrieveMemory- Retrieve a specific memorymemoryStoresUpdate- Update memory storememoryStoresUpdateDocument- Update a specific memory documentmemoryStoresUpdateMemory- Update a specific memorymodelsList- List modelspromptsCreate- Create a promptpromptsDelete- Delete a promptpromptsGetVersion- Retrieve a prompt versionpromptsList- List all promptspromptsListVersions- List all prompt versionspromptsRetrieve- Retrieve a promptpromptsUpdate- Update a promptremoteconfigsRetrieve- Retrieve a remote configrouterChatCompletions- Create chat completionrouterImagesGenerate- Create imagetoolsCreate- Create tooltoolsDelete- Delete tooltoolsGetV2ToolsToolIdVersions- List tool versionstoolsGetV2ToolsToolIdVersionsVersionId- Get tool versiontoolsList- List toolstoolsRetrieve- Retrieve tooltoolsUpdate- Update tool- ~~
agentsInvoke~~ - Execute an agent task :warning: Deprecated - ~~
agentsRun~~ - Run an agent with configuration :warning: Deprecated - ~~
agentsStream~~ - Stream agent execution in real-time :warning: Deprecated - ~~
agentsStreamRun~~ - Run agent with streaming response :warning: Deprecated
Server-sent event streaming
Server-sent events are used to stream content from certain
operations. These operations will expose the stream as an async iterable that
can be consumed using a for await...of loop. The loop will
terminate when the server no longer has any events to send and closes the
underlying connection.
import { Orq } from "@orq-ai/node";
const orq = new Orq({
environment: "<value>",
contactId: "<id>",
apiKey: process.env["ORQ_API_KEY"] ?? "",
});
async function run() {
const result = await orq.deployments.stream({
key: "<key>",
});
for await (const event of result) {
console.log(event);
}
}
run();
File uploads
Certain SDK methods accept files as part of a multi-part request. It is possible and typically recommended to upload files as a stream rather than reading the entire contents into memory. This avoids excessive memory consumption and potentially crashing with out-of-memory errors when working with very large files. The following example demonstrates how to attach a file stream to a request.
[!TIP]
Depending on your JavaScript runtime, there are convenient utilities that return a handle to a file without reading the entire contents into memory:
- Node.js v20+: Since v20, Node.js comes with a native
openAsBlobfunction innode:fs.- Bun: The native
Bun.filefunction produces a file handle that can be used for streaming file uploads.- Browsers: All supported browsers return an instance to a
Filewhen reading the value from an<input type="file">element.- Node.js v18: A file stream can be created using the
fileFromhelper fromfetch-blob/from.js.
import { Orq } from "@orq-ai/node";
import { openAsBlob } from "node:fs";
const orq = new Orq({
apiKey: process.env["ORQ_API_KEY"] ?? "",
});
async function run() {
const result = await orq.files.create({
file: await openAsBlob("example.file"),
});
console.log(result);
}
run();
Retries
Some of the endpoints in this SDK support retries. If you use the SDK without any configuration, it will fall back to the default retry strategy provided by the API. However, the default retry strategy can be overridden on a per-operation basis, or across the entire SDK.
To change the default retry strategy for a single API call, simply provide a retryConfig object to the call:
import { Orq } from "@orq-ai/node";
const orq = new Orq({
apiKey: process.env["ORQ_API_KEY"] ?? "",
});
async function run() {
const result = await orq.contacts.create({
externalId: "user_12345",
displayName: "Jane Smith",
email: "[email protected]",
avatarUrl: "https://example.com/avatars/jane-smith.jpg",
tags: [
"premium",
"beta-user",
"enterprise",
],
metadata: {
"department": "Engineering",
"role": "Senior Developer",
"subscription_tier": "premium",
"last_login": "2024-01-15T10:30:00Z",
},
}, {
retries: {
strategy: "backoff",
backoff: {
initialInterval: 1,
maxInterval: 50,
exponent: 1.1,
maxElapsedTime: 100,
},
retryConnectionErrors: false,
},
});
console.log(result);
}
run();
If you'd like to override the default retry strategy for all operations that support retries, you can provide a retryConfig at SDK initialization:
import { Orq } from "@orq-ai/node";
const orq = new Orq({
retryConfig: {
strategy: "backoff",
backoff: {
initialInterval: 1,
maxInterval: 50,
exponent: 1.1,
maxElapsedTime: 100,
},
retryConnectionErrors: false,
},
apiKey: process.env["ORQ_API_KEY"] ?? "",
});
async function run() {
const result = await orq.contacts.create({
externalId: "user_12345",
displayName: "Jane Smith",
email: "[email protected]",
avatarUrl: "https://example.com/avatars/jane-smith.jpg",
tags: [
"premium",
"beta-user",
"enterprise",
],
metadata: {
"department": "Engineering",
"role": "Senior Developer",
"subscription_tier": "premium",
"last_login": "2024-01-15T10:30:00Z",
},
});
console.log(result);
}
run();
Error Handling
OrqError is the base class for all HTTP error responses. It has the following properties:
| Property | Type | Description |
| ------------------- | ---------- | --------------------------------------------------------------------------------------- |
| error.message | string | Error message |
| error.statusCode | number | HTTP response status code eg 404 |
| error.headers | Headers | HTTP response headers |
| error.body | string | HTTP body. Can be empty string if no body is returned. |
| error.rawResponse | Response | Raw HTTP response |
| error.data$ | | Optional. Some errors may contain structured data. See Error Classes. |
Example
import { Orq } from "@orq-ai/node";
import * as errors from "@orq-ai/node/models/errors";
const orq = new Orq({
apiKey: process.env["ORQ_API_KEY"] ?? "",
});
async function run() {
try {
const result = await orq.contacts.retrieve({
id: "<id>",
});
console.log(result);
} catch (error) {
// The base class for HTTP error responses
if (error instanceof errors.OrqError) {
console.log(error.message);
console.log(error.statusCode);
console.log(error.body);
console.log(error.headers);
// Depending on the method different errors may be thrown
if (error instanceof errors.RetrieveContactResponseBody) {
console.log(error.data$.error); // string
}
}
}
}
run();
Error Classes
Primary error:
OrqError: The base class for HTTP error responses.
Network errors:
ConnectionError: HTTP client was unable to make a request to a server.RequestTimeoutError: HTTP request timed out due to an AbortSignal signal.RequestAbortedError: HTTP request was aborted by the client.InvalidRequestError: Any input used to create a request is invalid.UnexpectedClientError: Unrecognised or unexpected error.
Inherit from OrqError:
HonoApiError: Applicable to 10 of 102 methods.*GenerateConversationNameResponseBody: Conversation already has a display name. This endpoint only generates names for conversations with empty display names. Status code400. Applicable to 1 of 102 methods.*RetrieveContactResponseBody: Contact not found. Status code404. Applicable to 1 of 102 methods.*UpdateContactResponseBody: Contact not found. Status code404. Applicable to 1 of 102 methods.*DeleteContactResponseBody: Contact not found. Status code404. Applicable to 1 of 102 methods.*GetEvalsResponseBody: Workspace ID is not found on the request. Status code404. Applicable to 1 of 102 methods.*CreateEvalResponseBody: Workspace ID is not found on the request. Status code404. Applicable to 1 of 102 methods.*UpdateEvalResponseBody: Workspace ID is not found on the request. Status code404. Applicable to 1 of 102 methods.*DeleteEvalResponseBody: Workspace ID is not found on the request. Status code404. Applicable to 1 of 102 methods.*InvokeEvalResponseBody: Workspace ID is not found on the request. Status code404. Applicable to 1 of 102 methods.*GetV2EvaluatorsIdVersionsResponseBody: Evaluator not found. Status code404. Applicable to 1 of 102 methods.*GetV2EvaluatorsIdVersionsVersionIdResponseBody: Evaluator or version not found. Status code404. Applicable to 1 of 102 methods.*DeleteAgentResponseBody: Agent not found. The specified agent key does not exist in the workspace or has already been deleted. Status code404. Applicable to 1 of 102 methods.*RetrieveAgentRequestResponseBody: Agent not found. The specified agent key does not exist in the workspace or you do not have permission to access it. Status code404. Applicable to 1 of 102 methods.*UpdateAgentResponseBody: Agent not found. The specified agent key does not exist in the workspace or you do not have permission to modify it. Status code404. Applicable to 1 of 102 methods.*StreamRunAgentResponseBody: Model not found. Status code404. Applicable to 1 of 102 methods.*StreamAgentResponseBody: Agent not found. Status code404. Applicable to 1 of 102 methods.*GenerateConversationNameConversationsResponseBody: Conversation not found. Status code404. Applicable to 1 of 102 methods.*RetrieveConversationResponseBody: Conversation not found. The specified conversation ID does not exist in the workspace or you do not have permission to access it. Status code404. Applicable to 1 of 102 methods.*UpdateConversationResponseBody: Conversation not found. The specified conversation ID does not exist in the workspace or you do not have permission to modify it. Status code404. Applicable to 1 of 102 methods.*DeleteConversationResponseBody: Conversation not found. The specified conversation ID does not exist in the workspace or has already been deleted. Status code404. Applicable to 1 of 102 methods.*UpdatePromptResponseBody: Prompt not found. Status code404. Applicable to 1 of 102 methods.*GetPromptVersionResponseBody: Not Found - The prompt or prompt version does not exist. Status code404. Applicable to 1 of 102 methods.*UpdateToolResponseBody: Tool not found. Status code404. Applicable to 1 of 102 methods.*GetV2ToolsToolIdVersionsResponseBody: Tool not found. Status code404. Applicable to 1 of 102 methods.*GetV2ToolsToolIdVersionsVersionIdResponseBody: Tool or version not found. Status code404. Applicable to 1 of 102 methods.*CreateAgentRequestResponseBody: Conflict - An agent with the specified key already exists in this workspace. Each agent must have a unique key within a workspace to ensure proper identification and management. Status code409. Applicable to 1 of 102 methods.*InvokeEvalEvalsResponseBody: Error running the evaluator. Status code500. Applicable to 1 of 102 methods.*ResponseValidationError: Type mismatch between the data returned from the server and the structure expected by the SDK. Seeerror.rawValuefor the raw value anderror.pretty()for a nicely formatted multi-line string.
* Check the method documentation to see if the error is applicable.
Server Selection
Override Server URL Per-Client
The default server can be overridden globally by passing a URL to the serverURL: string optional parameter when initializing the SDK client instance. For example:
import { Orq } from "@orq-ai/node";
const orq = new Orq({
serverURL: "https://my.orq.ai",
apiKey: process.env["ORQ_API_KEY"] ?? "",
});
async function run() {
const result = await orq.contacts.create({
externalId: "user_12345",
displayName: "Jane Smith",
email: "[email protected]",
avatarUrl: "https://example.com/avatars/jane-smith.jpg",
tags: [
"premium",
"beta-user",
"enterprise",
],
metadata: {
"department": "Engineering",
"role": "Senior Developer",
"subscription_tier": "premium",
"last_login": "2024-01-15T10:30:00Z",
},
});
console.log(result);
}
run();
Custom HTTP Client
The TypeScript SDK makes API calls using an HTTPClient that wraps the native
Fetch API. This
client is a thin wrapper around fetch and provides the ability to attach hooks
around the request lifecycle that can be used to modify the request or handle
errors and response.
The HTTPClient constructor takes an optional fetcher argument that can be
used to integrate a third-party HTTP client or when writing tests to mock out
the HTTP client and feed in fixtures.
The following example shows how to use the "beforeRequest" hook to to add a
custom header and a timeout to requests and how to use the "requestError" hook
to log errors:
import { Orq } from "@orq-ai/node";
import { HTTPClient } from "@orq-ai/node/lib/http";
const httpClient = new HTTPClient({
// fetcher takes a function that has the same signature as native `fetch`.
fetcher: (request) => {
return fetch(request);
}
});
httpClient.addHook("beforeRequest", (request) => {
const nextRequest = new Request(request, {
signal: request.signal || AbortSignal.timeout(5000)
});
nextRequest.headers.set("x-custom-header", "custom value");
return nextRequest;
});
httpClient.addHook("requestError", (error, request) => {
console.group("Request Error");
console.log("Reason:", `${error}`);
console.log("Endpoint:", `${request.method} ${request.url}`);
console.groupEnd();
});
const sdk = new Orq({ httpClient: httpClient });Debugging
You can setup your SDK to emit debug logs for SDK requests and responses.
You can pass a logger that matches console's interface as an SDK option.
[!WARNING] Beware that debug logging will reveal secrets, like API tokens in headers, in log messages printed to a console or files. It's recommended to use this feature only during local development and not in production.
import { Orq } from "@orq-ai/node";
const sdk = new Orq({ debugLogger: console });You can also enable a default debug logger by setting an environment variable ORQ_DEBUG to true.
Development
Maturity
This SDK is in beta, and there may be breaking changes between versions without a major version update. Therefore, we recommend pinning usage to a specific package version. This way, you can install the same version each time without breaking changes unless you are intentionally looking for the latest version.
Contributions
While we value open-source contributions to this SDK, this library is generated programmatically. Any manual changes added to internal files will be overwritten on the next generation. We look forward to hearing your feedback. Feel free to open a PR or an issue with a proof of concept and we'll do our best to include it in a future release.
