npm package: @fermidevsdk/fermi
Description: Developer-friendly & type-safe Typescript SDK specifically catered to leverage *fermisdk* API.
Author: Speakeasy
Latest version: 0.0.3

# fermisdk

Developer-friendly & type-safe Typescript SDK specifically catered to leverage *fermisdk* API.

[![Built by Speakeasy](https://img.shields.io/badge/Built_by-SPEAKEASY-374151?style=for-the-badge&labelColor=f3f4f6)](https://www.speakeasy.com/?utm_source=fermisdk&utm_campaign=typescript)
[![License: MIT](https://img.shields.io/badge/LICENSE_//_MIT-3b5bdb?style=for-the-badge&labelColor=eff6ff)](https://opensource.org/licenses/MIT)


<br /><br />

<!-- Start Summary [summary] -->
## Summary

Fermi API: API documentation for Fermi platform including data connectors, brain visualization, and chat/session management
<!-- End Summary [summary] -->

<!-- Start Table of Contents [toc] -->
## Table of Contents
<!-- $toc-max-depth=2 -->
* [fermisdk](#fermisdk)
  * [SDK Installation](#sdk-installation)
  * [Requirements](#requirements)
  * [SDK Example Usage](#sdk-example-usage)
  * [Authentication](#authentication)
  * [Available Resources and Operations](#available-resources-and-operations)
  * [Standalone functions](#standalone-functions)
  * [File uploads](#file-uploads)
  * [Retries](#retries)
  * [Error Handling](#error-handling)
  * [Server Selection](#server-selection)
  * [Custom HTTP Client](#custom-http-client)
  * [Debugging](#debugging)
* [Development](#development)
  * [Maturity](#maturity)
  * [Contributions](#contributions)

<!-- End Table of Contents [toc] -->

<!-- Start SDK Installation [installation] -->
## SDK Installation

The SDK can be installed with either [npm](https://www.npmjs.com/), [pnpm](https://pnpm.io/), [bun](https://bun.sh/) or [yarn](https://classic.yarnpkg.com/en/) package managers.

### NPM

```bash
npm i @fermidevsdk/fermi
```

### PNPM

```bash
pnpm add @fermidevsdk/fermi
```

### Bun

```bash
bun add @fermidevsdk/fermi
```

### Yarn

```bash
yarn add @fermidevsdk/fermi
```

> [!NOTE]
> This package is published with CommonJS and ES Modules (ESM) support.
<!-- End SDK Installation [installation] -->

<!-- Start Requirements [requirements] -->
## Requirements

For supported JavaScript runtimes, please consult [RUNTIMES.md](RUNTIMES.md).
<!-- End Requirements [requirements] -->

<!-- Start SDK Example Usage [usage] -->
## SDK Example Usage

### Example

```typescript
import { Fermisdk } from "@fermidevsdk/fermi";

const fermisdk = new Fermisdk({
  bearerAuth: process.env["FERMISDK_BEARER_AUTH"] ?? "",
});

async function run() {
  const result = await fermisdk.brain.performVisualization({
    action: "visualization",
  });

  console.log(result);
}

run();

```
<!-- End SDK Example Usage [usage] -->

<!-- Start Authentication [security] -->
## Authentication

### Per-Client Security Schemes

This SDK supports the following security scheme globally:

| Name         | Type | Scheme      | Environment Variable   |
| ------------ | ---- | ----------- | ---------------------- |
| `bearerAuth` | http | HTTP Bearer | `FERMISDK_BEARER_AUTH` |

To authenticate with the API the `bearerAuth` parameter must be set when initializing the SDK client instance. For example:
```typescript
import { Fermisdk } from "fermisdk";

const fermisdk = new Fermisdk({
  bearerAuth: process.env["FERMISDK_BEARER_AUTH"] ?? "",
});

async function run() {
  const result = await fermisdk.brain.performVisualization({
    action: "visualization",
  });

  console.log(result);
}

run();

```
<!-- End Authentication [security] -->

<!-- Start Available Resources and Operations [operations] -->
## Available Resources and Operations

<details open>
<summary>Available methods</summary>

### [Brain](docs/sdks/brain/README.md)

* [performVisualization](docs/sdks/brain/README.md#performvisualization) - Perform Action API – Visualization

### [ChatAndSessions](docs/sdks/chatandsessions/README.md)

* [manageSession](docs/sdks/chatandsessions/README.md#managesession) - Manage Session
* [listSessions](docs/sdks/chatandsessions/README.md#listsessions) - List Chat Sessions
* [getSessionInfo](docs/sdks/chatandsessions/README.md#getsessioninfo) - Get Session Info

### [DataConnectors](docs/sdks/dataconnectors/README.md)

* [createConnectSession](docs/sdks/dataconnectors/README.md#createconnectsession) - Create Connection Session
* [listConnections](docs/sdks/dataconnectors/README.md#listconnections) - List Connections
* [getConnection](docs/sdks/dataconnectors/README.md#getconnection) - Get Connection Details
* [deleteConnection](docs/sdks/dataconnectors/README.md#deleteconnection) - Disconnect Connection
* [getConnectionMetadata](docs/sdks/dataconnectors/README.md#getconnectionmetadata) - Get Connection Metadata
* [updateConnectionMetadata](docs/sdks/dataconnectors/README.md#updateconnectionmetadata) - Update Connection Metadata
* [uploadDocuments](docs/sdks/dataconnectors/README.md#uploaddocuments) - Upload Documents
* [testDatabaseConnection](docs/sdks/dataconnectors/README.md#testdatabaseconnection) - Test Database Connection
* [getDatabaseMetadata](docs/sdks/dataconnectors/README.md#getdatabasemetadata) - Test Connection and Fetch Databases
* [enqueueSync](docs/sdks/dataconnectors/README.md#enqueuesync) - Start Sync

</details>
<!-- End Available Resources and Operations [operations] -->

<!-- Start Standalone functions [standalone-funcs] -->
## 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](./FUNCTIONS.md).

<details>

<summary>Available standalone functions</summary>

- [`brainPerformVisualization`](docs/sdks/brain/README.md#performvisualization) - Perform Action API – Visualization
- [`chatAndSessionsGetSessionInfo`](docs/sdks/chatandsessions/README.md#getsessioninfo) - Get Session Info
- [`chatAndSessionsListSessions`](docs/sdks/chatandsessions/README.md#listsessions) - List Chat Sessions
- [`chatAndSessionsManageSession`](docs/sdks/chatandsessions/README.md#managesession) - Manage Session
- [`dataConnectorsCreateConnectSession`](docs/sdks/dataconnectors/README.md#createconnectsession) - Create Connection Session
- [`dataConnectorsDeleteConnection`](docs/sdks/dataconnectors/README.md#deleteconnection) - Disconnect Connection
- [`dataConnectorsEnqueueSync`](docs/sdks/dataconnectors/README.md#enqueuesync) - Start Sync
- [`dataConnectorsGetConnection`](docs/sdks/dataconnectors/README.md#getconnection) - Get Connection Details
- [`dataConnectorsGetConnectionMetadata`](docs/sdks/dataconnectors/README.md#getconnectionmetadata) - Get Connection Metadata
- [`dataConnectorsGetDatabaseMetadata`](docs/sdks/dataconnectors/README.md#getdatabasemetadata) - Test Connection and Fetch Databases
- [`dataConnectorsListConnections`](docs/sdks/dataconnectors/README.md#listconnections) - List Connections
- [`dataConnectorsTestDatabaseConnection`](docs/sdks/dataconnectors/README.md#testdatabaseconnection) - Test Database Connection
- [`dataConnectorsUpdateConnectionMetadata`](docs/sdks/dataconnectors/README.md#updateconnectionmetadata) - Update Connection Metadata
- [`dataConnectorsUploadDocuments`](docs/sdks/dataconnectors/README.md#uploaddocuments) - Upload Documents

</details>
<!-- End Standalone functions [standalone-funcs] -->

<!-- Start File uploads [file-upload] -->
## 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 `openAsBlob` function in [`node:fs`](https://nodejs.org/docs/latest-v20.x/api/fs.html#fsopenasblobpath-options).
> - **Bun:** The native [`Bun.file`](https://bun.sh/docs/api/file-io#reading-files-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`](https://developer.mozilla.org/en-US/docs/Web/API/File) when reading the value from an `<input type="file">` element.
> - **Node.js v18:** A file stream can be created using the `fileFrom` helper from [`fetch-blob/from.js`](https://www.npmjs.com/package/fetch-blob).

```typescript
import { Fermisdk } from "fermisdk";

const fermisdk = new Fermisdk({
  bearerAuth: process.env["FERMISDK_BEARER_AUTH"] ?? "",
});

async function run() {
  const result = await fermisdk.dataConnectors.uploadDocuments({
    files: [],
  });

  console.log(result);
}

run();

```
<!-- End File uploads [file-upload] -->

<!-- Start Retries [retries] -->
## 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:
```typescript
import { Fermisdk } from "fermisdk";

const fermisdk = new Fermisdk({
  bearerAuth: process.env["FERMISDK_BEARER_AUTH"] ?? "",
});

async function run() {
  const result = await fermisdk.brain.performVisualization({
    action: "visualization",
  }, {
    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:
```typescript
import { Fermisdk } from "fermisdk";

const fermisdk = new Fermisdk({
  retryConfig: {
    strategy: "backoff",
    backoff: {
      initialInterval: 1,
      maxInterval: 50,
      exponent: 1.1,
      maxElapsedTime: 100,
    },
    retryConnectionErrors: false,
  },
  bearerAuth: process.env["FERMISDK_BEARER_AUTH"] ?? "",
});

async function run() {
  const result = await fermisdk.brain.performVisualization({
    action: "visualization",
  });

  console.log(result);
}

run();

```
<!-- End Retries [retries] -->

<!-- Start Error Handling [errors] -->
## Error Handling

[`FermisdkError`](./src/models/errors/fermisdkerror.ts) 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](#error-classes). |

### Example
```typescript
import { Fermisdk } from "fermisdk";
import * as errors from "fermisdk/models/errors";

const fermisdk = new Fermisdk({
  bearerAuth: process.env["FERMISDK_BEARER_AUTH"] ?? "",
});

async function run() {
  try {
    const result = await fermisdk.brain.performVisualization({
      action: "visualization",
    });

    console.log(result);
  } catch (error) {
    // The base class for HTTP error responses
    if (error instanceof errors.FermisdkError) {
      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.ErrorT) {
        console.log(error.data$.error); // string
        console.log(error.data$.detail); // string
      }
    }
  }
}

run();

```

### Error Classes
**Primary errors:**
* [`FermisdkError`](./src/models/errors/fermisdkerror.ts): The base class for HTTP error responses.
  * [`ErrorT`](./src/models/errors/errort.ts): Generic error.

<details><summary>Less common errors (6)</summary>

<br />

**Network errors:**
* [`ConnectionError`](./src/models/errors/httpclienterrors.ts): HTTP client was unable to make a request to a server.
* [`RequestTimeoutError`](./src/models/errors/httpclienterrors.ts): HTTP request timed out due to an AbortSignal signal.
* [`RequestAbortedError`](./src/models/errors/httpclienterrors.ts): HTTP request was aborted by the client.
* [`InvalidRequestError`](./src/models/errors/httpclienterrors.ts): Any input used to create a request is invalid.
* [`UnexpectedClientError`](./src/models/errors/httpclienterrors.ts): Unrecognised or unexpected error.


**Inherit from [`FermisdkError`](./src/models/errors/fermisdkerror.ts)**:
* [`ResponseValidationError`](./src/models/errors/responsevalidationerror.ts): Type mismatch between the data returned from the server and the structure expected by the SDK. See `error.rawValue` for the raw value and `error.pretty()` for a nicely formatted multi-line string.

</details>
<!-- End Error Handling [errors] -->

<!-- Start Server Selection [server] -->
## 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:
```typescript
import { Fermisdk } from "fermisdk";

const fermisdk = new Fermisdk({
  serverURL: "https://api.fermi.dev/public/v1",
  bearerAuth: process.env["FERMISDK_BEARER_AUTH"] ?? "",
});

async function run() {
  const result = await fermisdk.brain.performVisualization({
    action: "visualization",
  });

  console.log(result);
}

run();

```
<!-- End Server Selection [server] -->

<!-- Start Custom HTTP Client [http-client] -->
## Custom HTTP Client

The TypeScript SDK makes API calls using an `HTTPClient` that wraps the native
[Fetch API](https://developer.mozilla.org/en-US/docs/Web/API/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:

```typescript
import { Fermisdk } from "fermisdk";
import { HTTPClient } from "fermisdk/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 Fermisdk({ httpClient: httpClient });
```
<!-- End Custom HTTP Client [http-client] -->

<!-- Start Debugging [debug] -->
## 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.

```typescript
import { Fermisdk } from "fermisdk";

const sdk = new Fermisdk({ debugLogger: console });
```

You can also enable a default debug logger by setting an environment variable `FERMISDK_DEBUG` to true.
<!-- End Debugging [debug] -->

<!-- Placeholder for Future Speakeasy SDK Sections -->

# 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. 

### SDK Created by [Speakeasy](https://www.speakeasy.com/?utm_source=fermisdk&utm_campaign=typescript)