> For the complete documentation index, see [llms.txt](https://hub.moonexe.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hub.moonexe.com/how-it-works/how-the-liquidity-platform-works.md).

# How the liquidity platform works

How MoonExe pools member USDT and supplies it to businesses.

MoonExe is a **USDT liquidity provider**. It pools members' USDT and supplies it as liquidity to businesses that need it.

## B2B liquidity flow

{% stepper %}
{% step %}

### Supply

**MoonExe members** supply USDT liquidity on the MoonExe platform.
{% endstep %}

{% step %}

### MoonExe platform

MoonExe pools the liquidity and routes it to demand in a way that is **transparent, efficient and secure**.
{% endstep %}

{% step %}

### Demand

**Businesses**, such as on-ramp service providers that need USDT, take the liquidity.
{% endstep %}
{% endstepper %}

## Members share in the spread

1. Members supply USDT to the MoonExe platform.
2. MoonExe supplies USDT to businesses.
3. The difference between the supply and demand prices is the **spread**.
4. The platform and its members share the profit from the spread.

{% hint style="warning" %}
Earnings depend on market conditions and are not guaranteed. Log in to your member account for details of the programme.
{% endhint %}


---

# 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://hub.moonexe.com/how-it-works/how-the-liquidity-platform-works.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.