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

# Conversion Engine

The Conversion Engine moves value between supported assets: one token into another, or the same dollar from one network to another.

## What it does

* **Swaps inside an app.** On Solana, swaps route through Jupiter to find the best available price across markets.
* **Moving USDC between networks.** The design uses Circle's CCTP, which burns USDC on one network and mints it on another, rather than relying on a third-party bridge.
* **Treasury conversions.** Moving the system's own funds between the forms it needs, for example to fund the Yield Engine or to settle payouts.

## Fees

Conversion fees are agreed with each app and shared with it, on top of network fees.

## Status

In development. Swap routing is built. Treasury conversion flows are built and switched off.


---

# 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.zirodelta.com/modules/conversion-engine.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.