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

# Intents Connect SDK

TypeScript SDK and wallet packages for building Intents Connect integrations.

> **Beta.** The SDK talks to `https://intents-connect-alpha-api.aurora.dev`. APIs may change between minor versions. TON (`ton_connect`) and Tron (`tip191`) wallets are not supported yet.

The SDK turns the [Intents Connect API](https://docs.intents.aurora.dev/api-reference/intents-connect-api-reference) into a single call. **A new integration is just a step builder**: you describe the on-chain calls to run on the destination chain, and the SDK handles everything else:

* intermediary account resolution
* quoting and fee arithmetic
* wallet signing (EVM, Solana, NEAR, Stellar)
* the deposit transfer
* polling, expiry and in-flight recovery

## Packages

| Package                                                                                                          | What it is                                                                    | Docs                                                                               |
| ---------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------- | ---------------------------------------------------------------------------------- |
| [`@aurora-is-near/intents-connect`](https://www.npmjs.com/package/@aurora-is-near/intents-connect)               | Headless TypeScript client and execution runner, with optional React bindings | [TypeScript SDK](/intents-connect/intents-connect-sdk/typescript-sdk.md)           |
| [`@aurora-is-near/intents-connect-wallet`](https://www.npmjs.com/package/@aurora-is-near/intents-connect-wallet) | Wallet connection and deposit transfers, one subpath per chain                | [Wallet integrations](/intents-connect/intents-connect-sdk/wallet-integrations.md) |

## How it fits together

```mermaid
flowchart TB
    APP["<b>Your dApp</b><br/>recipe: the steps to run"]
    SDK["<b>intents-connect</b><br/>runner: plan · sign · deposit · poll"]
    WAL["<b>intents-connect-wallet</b><br/>connect wallets · send deposit"]
    API["Intents Connect API"]
    NI["NEAR Intents / 1Click<br/>bridges the funds"]
    INT["Intermediary account<br/>runs your steps on the destination chain"]

    APP --> SDK
    APP --> WAL
    WAL -- "wallet + transfer" --> SDK
    SDK --> API
    API --> NI --> INT
```

The user signs once from their own wallet, on any supported chain. An [intermediary account](https://docs.intents.aurora.dev/intents-connect/deep-dive/intermediary-accounts) on the destination chain, controlled by that wallet, executes the steps.

## Where to start

| I want to…                                              | Read                                                                                              |
| ------------------------------------------------------- | ------------------------------------------------------------------------------------------------- |
| Understand the SDK and run my first execution           | [TypeScript SDK](/intents-connect/intents-connect-sdk/typescript-sdk.md)                          |
| Describe on-chain steps and choose a fee strategy       | [Recipes & fees](/intents-connect/intents-connect-sdk/typescript-sdk/recipes-and-fees.md)         |
| Handle statuses, errors, retries and resume             | [Lifecycle & errors](/intents-connect/intents-connect-sdk/typescript-sdk/lifecycle-and-errors.md) |
| Use it from React                                       | [React](/intents-connect/intents-connect-sdk/typescript-sdk/react.md)                             |
| Connect EVM, Solana, NEAR or Stellar wallets            | [Wallet integrations](/intents-connect/intents-connect-sdk/wallet-integrations.md)                |
| See complete integrations (Hydrex, Polymarket, Jupiter) | [Examples](/intents-connect/intents-connect-sdk/examples.md)                                      |

## Related

* [What is Intents Connect?](https://docs.intents.aurora.dev/intents-connect/readme-1): the product
* [How It Works](https://docs.intents.aurora.dev/intents-connect/deep-dive/how-it-works) and [Execution Lifecycle](https://docs.intents.aurora.dev/intents-connect/deep-dive/execution-lifecycle): concepts behind the SDK
* [Intents Connect API Reference](https://docs.intents.aurora.dev/api-reference/intents-connect-api-reference): the HTTP API the SDK calls
* [Source on GitHub](https://github.com/aurora-is-near/intents-swap-widget/tree/main/packages/intents-connect)


---

# 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.intents.aurora.dev/intents-connect/intents-connect-sdk.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.