Developer-friendly & type-safe TypeScript SDK for the Mix REST API - providing session management, messaging, and system operations.
Mix REST API: REST API for the Mix application - session management, messaging, and system operations
The SDK can be installed with either npm, pnpm, bun or yarn package managers.
npm add mix-typescript-sdk
pnpm add mix-typescript-sdk
bun add mix-typescript-sdk
yarn add mix-typescript-sdk zod
# Note that Yarn does not install peer dependencies automatically. You will need
# to install zod as shown above.
Note
This package is published with CommonJS and ES Modules (ESM) support.
For supported JavaScript runtimes, please consult RUNTIMES.md.
import { Mix } from "mix-typescript-sdk";
const mix = new Mix();
async function run() {
const result = await mix.authentication.storeApiKey({
apiKey: "<value>",
provider: "openrouter",
});
console.log(result);
}
run();
Available methods
- setApiKey - Set API key
- storeApiKey - Store API key
- login - OAuth authentication
- handleOAuthCallback - Handle OAuth callback
- startOAuthFlow - Start OAuth authentication
- getAuthStatus - Get authentication status
- validatePreferredProvider - Validate preferred provider
- deleteCredentials - Delete provider credentials
- list - List session files
- upload - Upload file to session
- delete - Delete session file
- get - Get session file
- getHistory - Get global message history
- cancelProcessing - Cancel agent processing
- getSession - List session messages
- send - Send a message to session
- get - Get user preferences
- update - Update user preferences
- getProviders - Get available providers
- reset - Reset preferences
- list - List all sessions
- create - Create a new session
- delete - Delete a session
- get - Get a specific session
- fork - Fork a session
- listCommands - List available commands
- getCommand - Get specific command
- listMcpServers - List MCP servers
- healthCheck - Health check
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.
Available standalone functions
authenticationDeleteCredentials
- Delete provider credentialsauthenticationGetAuthStatus
- Get authentication statusauthenticationHandleOAuthCallback
- Handle OAuth callbackauthenticationLogin
- OAuth authenticationauthenticationStartOAuthFlow
- Start OAuth authenticationauthenticationStoreApiKey
- Store API keyauthenticationValidatePreferredProvider
- Validate preferred providerauthSetApiKey
- Set API keyfilesDelete
- Delete session filefilesGet
- Get session filefilesList
- List session filesfilesUpload
- Upload file to sessionmessagesCancelProcessing
- Cancel agent processingmessagesGetHistory
- Get global message historymessagesGetSession
- List session messagesmessagesSend
- Send a message to sessionpermissionsDeny
- Deny permissionpermissionsGrant
- Grant permissionpreferencesGet
- Get user preferencespreferencesGetProviders
- Get available providerspreferencesReset
- Reset preferencespreferencesUpdate
- Update user preferencessessionsCreate
- Create a new sessionsessionsDelete
- Delete a sessionsessionsFork
- Fork a sessionsessionsGet
- Get a specific sessionsessionsList
- List all sessionssystemGetCommand
- Get specific commandsystemHealthCheck
- Health checksystemListCommands
- List available commandssystemListMcpServers
- List MCP servers
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
openAsBlob
function innode:fs
. - Bun: The native
Bun.file
function produces a file handle that can be used for streaming file uploads. - Browsers: All supported browsers return an instance to a
File
when reading the value from an<input type="file">
element. - Node.js v18: A file stream can be created using the
fileFrom
helper fromfetch-blob/from.js
.
import { Mix } from "mix-typescript-sdk";
import { openAsBlob } from "node:fs";
const mix = new Mix();
async function run() {
const result = await mix.files.upload({
id: "<id>",
requestBody: {
file: await openAsBlob("example.file"),
},
});
console.log(result);
}
run();
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 { Mix } from "mix-typescript-sdk";
const mix = new Mix();
async function run() {
const result = await mix.authentication.storeApiKey({
apiKey: "<value>",
provider: "openrouter",
}, {
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 { Mix } from "mix-typescript-sdk";
const mix = new Mix({
retryConfig: {
strategy: "backoff",
backoff: {
initialInterval: 1,
maxInterval: 50,
exponent: 1.1,
maxElapsedTime: 100,
},
retryConnectionErrors: false,
},
});
async function run() {
const result = await mix.authentication.storeApiKey({
apiKey: "<value>",
provider: "openrouter",
});
console.log(result);
}
run();
MixError
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. |
import { Mix } from "mix-typescript-sdk";
import * as errors from "mix-typescript-sdk/models/errors";
const mix = new Mix();
async function run() {
try {
const result = await mix.authentication.storeApiKey({
apiKey: "<value>",
provider: "openrouter",
});
console.log(result);
} catch (error) {
// The base class for HTTP error responses
if (error instanceof errors.MixError) {
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.ErrorResponse) {
console.log(error.data$.error); // models.RESTError
}
}
}
}
run();
Primary errors:
MixError
: The base class for HTTP error responses.ErrorResponse
: Generic error.
Less common errors (6)
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 MixError
:
ResponseValidationError
: Type mismatch between the data returned from the server and the structure expected by the SDK. Seeerror.rawValue
for the raw value anderror.pretty()
for a nicely formatted multi-line string.
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 { Mix } from "mix-typescript-sdk";
const mix = new Mix({
serverURL: "http://localhost:8088",
});
async function run() {
const result = await mix.authentication.storeApiKey({
apiKey: "<value>",
provider: "openrouter",
});
console.log(result);
}
run();
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 { Mix } from "mix-typescript-sdk";
import { HTTPClient } from "mix-typescript-sdk/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 Mix({ httpClient });
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 { Mix } from "mix-typescript-sdk";
const sdk = new Mix({ debugLogger: console });
You can also enable a default debug logger by setting an environment variable MIX_DEBUG
to true.
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.
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.