> 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/examples.md).

# Examples

Real Intents Connect SDK integrations from the demo app, end to end.

Each example is a working integration from the [Intents Connect demo](https://github.com/aurora-is-near/intents-swap-widget/tree/main/apps/intents-connect-demo). Every page follows the same layout: what it does, what the user does, what happens behind the scenes, and the core SDK code.

| Example                                                                             | Destination | What the user gets                                    | SDK features shown                                                       |
| ----------------------------------------------------------------------------------- | ----------- | ----------------------------------------------------- | ------------------------------------------------------------------------ |
| [Hydrex](/intents-connect/intents-connect-sdk/examples/hydrex.md)                   | Base        | A cbETH/WETH liquidity position (NFT) in their wallet | EVM recipe, native destination, placeholder fee                          |
| [Polymarket](/intents-connect/intents-connect-sdk/examples/polymarket.md)           | Polygon     | pUSD in their Polymarket account                      | EVM recipe, token destination, recipient inside the steps                |
| [Solana (Jupiter)](/intents-connect/intents-connect-sdk/examples/solana-jupiter.md) | Solana      | Any of 10 SPL tokens 1Click doesn't list              | Solana recipe, `threeRound` fee, `preview`, steps-only sell and withdraw |

All three share the same setup:

```tsx
const api = createIntentsConnectApi({ baseUrl, apiKeyProxyUrl });
const { wallet } = useIntentsConnectWallet(); // EVM or Solana wallet, transfer wired in

<IntentsConnectProvider api={api} wallet={wallet}>
  <Tab /> {/* each tab: const exec = useExecution(); exec.run(plan) */}
</IntentsConnectProvider>;
```

The user can start from **any supported chain and token**. They either send from the connected wallet, or deposit to a shown address and QR code (`depositViaWallet: false`).

> Looking for Aave? See [Deposit into Aave from Solana](https://docs.intents.aurora.dev/intents-connect/examples/deposit-into-aave-from-solana), which uses the HTTP API directly.


---

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