> For the complete documentation index, see [llms.txt](https://docs.en.omnibridge.pro/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.en.omnibridge.pro/master/fees.md).

# Fees

The OmniBridge fee structure comprises two components: the bridging fee and the target chain gas fee. This structure ensures fast and reliable asset transfers.

* Bridging Fee

  Charged as a percentage of the transfer amount, we levy a 0.3% bridging fee on all users.
* Target Chain Gas Fee

  This fee covers the gas costs incurred when sending tokens to the user's address on the target chain.

Example: Suppose a user initiates a cross-chain swap on the Ethereum source chain, exchanging 1 ETH for BTC on the Bitcoin target chain:

 

Bridging Fee: 1 ETH \* 0.003 = 0.003 ETH

The cross-chain system uses 0.997 ETH for the actual swap. If the exchange rate yields 0.1 BTC, and the target chain gas fee is 0.001 BTC, the user will receive:

Final Amount: 0.1 BTC - 0.001 BTC = 0.099 BTC

<br>

<br>


---

# 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://docs.en.omnibridge.pro/master/fees.md?ask=<question>&goal=<endgoal>
```

`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.