> For the complete documentation index, see [llms.txt](https://docs.wanchain.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.wanchain.org/the-convert-n-burn-system/bridge-fees.md).

# Bridge fees

Wanchain’s cross-chain infrastructure is supported by two types of fees: a Network Fee and a Service Fee.

## Network Fee

The Network Fee is designed to cover the incurred on-chain costs associated with each cross-chain transaction. Depending on the destination chain, these can range from fractions of a cent to dozens of dollars per transaction. The Network Fee covers this cost and is routinely adjusted to reflect current market conditions.

## Service Fee

The Service Fee is calculated as a percentage of the user’s cross-chain transaction value. The base Service Fee is set below 0.2% for most routes.

The Service Fee has lower and upper limits. For most assets, the Service Fee’s lower and upper limits are set to $0.2 and $100, respectively.

*Note: In case of any discrepancies, the fees listed on* [*bridge.wanchain.org*](https://bridge.wanchain.org/) *shall prevail.*


---

# 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.wanchain.org/the-convert-n-burn-system/bridge-fees.md?ask=<question>&goal=<user_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.