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

# Overview

Helvex is a permissioned, trader-first RFQ desk on Canton Network. You set the minimum you'll receive. Solvers bid to meet or beat it.

Helvex is a permissioned, trader-first RFQ desk on Canton Network — a Dream Capital product. KYC-verified traders swap CC, CBTC, or USDCx. You set the minimum amount you'll receive. Solvers bid to meet or beat it. A qualifying bid is not a guaranteed fill. There is no public order book. Settlement is atomic: both assets move, or neither does.

The reference for that rule is [How trader-first RFQ works](/helvex-docs/02-helvex-how-the-app-works.md#how-trader-first-rfq-works).

Start with **How the app works** if you have never used Helvex. Use the **API integrator guide** only if you are calling the API from your own client.

{% hint style="warning" %}
Keep Helvex and Loop on the **same** network. TestNet tokens and parties do not work on MainNet, and the reverse.
{% endhint %}

|                 | TestNet (practice)                     | MainNet (real CC and real assets) |
| --------------- | -------------------------------------- | --------------------------------- |
| **App**         | <https://testnet-app.helvex.cc>        | <https://app.helvex.cc>           |
| **KYC**         | <https://testnet-app.helvex.cc/kyc>    | <https://app.helvex.cc/kyc>       |
| **API**         | <https://testnet-api.helvex.cc>        | <https://api.helvex.cc>           |
| **API health**  | <https://testnet-api.helvex.cc/health> | <https://api.helvex.cc/health>    |
| **Loop wallet** | <https://testnet.cantonloop.com>       | <https://cantonloop.com>          |

Health returns `{"status":"ok"}`.

| Guide                                                                  | Read it when                                                                                           |
| ---------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------ |
| [How the app works](/helvex-docs/02-helvex-how-the-app-works.md)       | You need the product model: the minimum you'll receive, qualifying bids, lock, fill, settle, withdraw. |
| [API integrator guide](/helvex-docs/01-helvex-api-integrator-guide.md) | You will post RFQs, fill RFQs, or transfer from code (HMAC API keys).                                  |

Neither guide covers KYC. Finish verification in the app first (government ID + live selfie).


---

# 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://helvex.gitbook.io/helvex-docs/readme.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.