> For the complete documentation index, see [llms.txt](https://docs.maple.finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.maple.finance/technical-resources/sdk/installation.md).

# Installation

The SDK is available as a single package, installable using your preferred package manager:

```bash
npm install @maplelabs/maple-js

// or if using yarn

yarn add @maplelabs/maple-js
```

⚠️ Important Note on SDK Versioning: Regularly check for updates and new releases to access the latest features, improvements, and bug fixes. Monitor the SDK's versioning by visiting the official repository, subscribing to release notifications, or checking your package manager's update logs. This ensures optimal experience and compatibility with the Maple Protocol ecosystem.

⚠️ **Beta Disclaimer:** Please be aware that the SDK is currently in beta. While we strive to provide the best possible experience, using it is at your own risk. We appreciate your understanding and encourage you to provide feedback on any issues or suggestions for improvements.

## Developer Links

* [Maple SDK GitHub repo](https://github.com/maple-labs/maple-js)
* [Maple Smart Contracts v2 GitHub repo](https://github.com/maple-labs/maple-core-v2)

## Requirements

* [ethers v5](https://docs.ethers.org/v5/)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.maple.finance/technical-resources/sdk/installation.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.