> For the complete documentation index, see [llms.txt](https://docs.bao.la/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bao.la/baola-docs/baola-product-documentation/trading-and-rebates/transaction.md).
# Transaction
#### 1、Same-chain and Cross-chain Swap
upports same-chain or cross-chain swaps within the range of assets and networks provided by the platform, reducing the steps required for users to handle asset exchange and cross-chain operations separately. The specific available combinations are subject to the actual support status on the page.
#### 2、Compact/PRO Mode
Supports switching between Simple and PRO modes. The Simple mode focuses on asset selection, amount input, and exchange operations; the PRO mode adds candlestick charts, KOL buying and signal layers, asset list, and transaction history, allowing users to complete exchanges while monitoring market trends and fund status.
#### 3、Gasless
The redemption page displays a Gas-free function label, and eligible orders can use this corresponding capability. Applicable networks, assets and fee conditions are subject to the order page (Gas-free does not mean exemption from all transaction fees)
---
# 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.bao.la/baola-docs/baola-product-documentation/trading-and-rebates/transaction.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.
