> For the complete documentation index, see [llms.txt](https://omen-protocol.gitbook.io/omen-protocol-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://omen-protocol.gitbook.io/omen-protocol-docs/guides/using-swap.md). # Using Swap Learn how to use the OMEN Utility trading panel, from selecting Buy or Sell and choosing a payment asset to configuring trade settings, reviewing transaction details, and confirming a swap through you The OMEN Utility trading panel provides two trading modes: 1. **Buy:** Purchase the selected token using a supported payment asset. 2. **Sell:** Exchange the selected token for another supported asset. Available actions and trading settings depend on the selected token, network, and current implementation. Before trading, verify the token name, contract address, and selected network. Similar token names and tickers may refer to different assets. ### Choosing a Payment Asset Use the **Pay with** menu to select the asset used to fund your trade. OMEN Utility provides the following payment asset options: 1. **ETH:** Native ETH on the supported network. 2. **Native WETH:** The Native WETH option displayed in the trading interface. 3. **USDG:** A supported USD-denominated payment asset. Available payment options may depend on the selected token and supported trading route. Before proceeding, confirm the selected payment asset, the amount you intend to spend, and the token you expect to receive. Review the latest quote, estimated output, applicable fees, and transaction details before approving the swap through your connected wallet. ### Entering an Amount Enter the amount you want to trade. OMEN requests a quote based on the selected assets and trade amount. Review the estimated output and other displayed details before proceeding. Quotes may expire or change as prices, liquidity, and market conditions change. A valid quote may be required before the transaction can proceed. ### Tax Settings The trading panel may provide **Auto** and **Manual** tax settings, depending on the current implementation. 1. **Auto:** Uses the application configured logic for the tax setting. 2. **Manual:** Allows users to specify a tax value through the available controls. Review the selected mode and displayed value before trading. Tax behavior can vary by token and implementation. A displayed setting does not guarantee a successful transaction. ### Reviewing the Transaction Before proceeding, review the transaction information displayed in the interface, including: 1. Estimated output. 2. Price impact, where available. 3. Slippage settings. 4. Network and applicable fees. 5. Any token approval or allowance request. Use **Review approval** when this option is available, then carefully inspect the information presented by your connected wallet. Some transactions require a token allowance before the swap can proceed. Review the requested permission before approving it. Quoted amounts are estimates and may differ from the final result because of price movements, liquidity changes, or execution conditions. ### Confirming the Swap When you are ready to proceed, confirm the required transaction through your connected wallet. OMEN does not need your seed phrase or private keys to facilitate a wallet-authorized swap. Wait for the transaction to complete and check its status. If the transaction fails, review the available transaction details before attempting it again. Repeated attempts may incur additional network fees. ### Slippage and Fees Slippage tolerance determines how much the execution price can move within the permitted range before a transaction fails. The available behavior depends on the selected setting and current implementation. 1. **Auto Slippage:** Uses the application configured behavior where supported. 2. **Manual Slippage:** Allows users to adjust the tolerance through the available controls. The default is **1.00% only if confirmed in the current implementation**. A higher tolerance allows a wider price movement but may result in a less favorable execution price. A lower tolerance may cause a transaction to fail if the price moves beyond the permitted range. Network fees, price impact, liquidity, and any applicable trading or integration fees may also affect the final result. Always review the latest transaction details before signing. ### Take Profit and Stop Loss **Status: Coming Soon** Take Profit (TP) and Stop Loss (SL) are planned features. They should not be treated as available trading functionality until they have been implemented and officially confirmed. ### Trading Risks Token prices and liquidity can change quickly. Transactions may fail, execution prices may differ from quoted estimates, and individual tokens may carry additional risks. Always verify the token contract, selected network, payment asset, and transaction details before signing. The availability of a token in OMEN Utility does not guarantee that the token is safe to trade. Users remain responsible for evaluating assets and understanding the risks associated with blockchain transactions. --- # 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://omen-protocol.gitbook.io/omen-protocol-docs/guides/using-swap.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.