> For the complete documentation index, see [llms.txt](https://docs.platform.softwareone.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.platform.softwareone.com/modules-and-features/settings/exchange.md).

# Exchange

Learn about currencies and exchange rates in the platform.

The **Exchange** module in the Marketplace is a centralized location for viewing the currencies and exchange rates used for pricing and billing within the platform.

This module is read-only and is designed to provide visibility into supported currencies and their associated exchange rate configurations.

You can use the module to view all supported currencies in the platform, access detailed information about a specific currency, and view related currency pairs along with individual currency pair details.

<table data-card-size="large" data-view="cards"><thead><tr><th></th><th></th></tr></thead><tbody><tr><td><a href="/modules-and-features/settings/exchange/currencies.md">Currencies</a></td><td>View currencies supported by the Marketplace.</td></tr><tr><td><a href="/modules-and-features/settings/exchange/currency-exchange.md">Currency exchange</a></td><td>View all currency pairs and exchange rates.</td></tr></tbody></table>


---

# 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.platform.softwareone.com/modules-and-features/settings/exchange.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.