> For the complete documentation index, see [llms.txt](https://docs.vortexfinance.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.vortexfinance.co/fx-pricing-and-transparency.md).

# FX pricing and transparency

FX pricing in Vortex is closely linked to the role of the Vortex DEX. The DEX provides transparent conversion between the **primary settlement stablecoin** and local partner stablecoins. Pricing is based on **interbank FX rates**, or — in markets with multiple rates — on **prevailing real trading rates** that reflect actual liquidity. This ensures that conversions are fair and aligned with real market conditions.

In addition to FX pricing, two types of fees apply:

* **Processing Fee** – A fixed percentage applied across supported rails. This covers FX processing and infrastructure costs (such as UX, KYC, payouts).
* **Network Fee** – Paid to blockchain validators. This covers one or more on-chain transactions, depending on network congestion and the output asset selected. For example, if funds are routed from a stablecoin into another token through a DEX, the user pays the related network 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.vortexfinance.co/fx-pricing-and-transparency.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.