> For the complete documentation index, see [llms.txt](https://docs.xaman.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.xaman.dev/js-ts-sdk/xumm-sdk-intro.md).

# Xaman SDK (Intro)

Developers can use the Xaman SDK to easily integrate with the Xaman platform. This allows for easy & secure end user interaction. With your application & the XRP Ledger.

## JavaScript/TypeScript

### NPM

The Xaman Javascript/TypeScript SDK can be found on **npm**:

{% embed url="<https://www.npmjs.com/package/xumm>" %}

### CDN

The latest version of the Xumm SDK is always available at:

```
https://xaman.app/assets/cdn/xumm.min.js
```

{% hint style="info" %}
Please note the CDN URL is heavily cached (edge and headers, so client side). If you are expecting a new version of the SDK to load, consider cleaning local cache and adding a random (e.g. your build hash) as a URL Query param to the URL to force URL uniqueness.
{% endhint %}

### Code samples

See [Examples / User stories](/js-ts-sdk/examples-user-stories.md)

### Warning (legacy packages)

{% hint style="warning" %}
Previously there were three different packages:

* `xumm-sdk`for backend interaction
* `xumm-xapp-sdk` for xApp frontend interaction
* `xumm-oauth2-pkce` for browser / "Web3" interaction

**All three packages above have been replaced by the** [**`xumm`**](https://www.npmjs.com/package/xumm) **package, which allows for easier (unified) interaction with the three aforementioned topics.**
{% endhint %}


---

# 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.xaman.dev/js-ts-sdk/xumm-sdk-intro.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.