> 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-widget/introduction.md).
# Introduction
The Intents Connect Widget is an embeddable UI component that lets your users interact with your dApp from any other chain or using any asset, without leaving your interface or managing any cross-chain complexity themselves.
#### How it differs from the Swap Widget
The **Swap Widget** handles asset swaps: a user selects a source token and a destination token, and the widget handles the exchange. It is self-contained and designed to be dropped into any application quickly.
The **Intents Connect Widget** handles cross-chain protocol interactions. Rather than just swapping assets, it enables actions like depositing into a lending protocol, taking a position, or interacting with a smart contract on a chain the user does not have assets on. The user stays in your dApp, signs once, and the widget handles execution end-to-end.
#### When to use it
The Intents Connect Widget is the right integration path if you want to:
* Accept users from any chain into a protocol that lives on a specific chain
* Offer one-click access to cross-chain actions without requiring users to bridge, switch wallets, or manage gas
* Embed a ready-made UI rather than building a custom interface via the Intents Connect API
#### Get early access
To register interest or request early access, contact the team.
---
# 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-widget/introduction.md?ask=&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.
