> For the complete documentation index, see [llms.txt](https://whitepaper.swe.at/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://whitepaper.swe.at/usdsweat-whitepaper/3.-sweat-wallet-gateway-to-the-movement-economy/3.5-near-intents-cross-chain-simplicity-powered-by-intelligence.md). # 3.5 NEAR Intents: Cross-Chain Simplicity, Powered by Intelligence Sweat Wallet’s multichain experience is powered by **NEAR Intents**, a decentralized request engine built on NEAR Protocol. No more need to interact with DEX, bridges or wormholes. Instead of manually bridging or swapping tokens, users simply express a goal and NEAR Intents handles the execution, unlocking an entirely new layer of Web3 intelligence. * **Step 1:** The user declares an intent (e.g., “Swap $50 worth of NEAR to ETH on Base”) * **Step 2:** Decentralized solvers return a quote, sourcing the best path and pricing * **Step 3:** The user confirms * **Step 4:** The transaction executes across chains It’s bridging and swapping, compressed into a single request to simplify and streamline the user experience. Every transaction uses **$SWEAT as gas**, reinforcing its role as the transactional currency of the Movement Economy. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://whitepaper.swe.at/usdsweat-whitepaper/3.-sweat-wallet-gateway-to-the-movement-economy/3.5-near-intents-cross-chain-simplicity-powered-by-intelligence.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.