# MetaFlux Knowledge Base

> Integration reference and user-facing docs for the MetaFlux derivatives exchange. Synced to GitBook.

Welcome. This is the place to start if you are **integrating with** or **building on** MetaFlux.

## Sections

### [API](/api.md)

* [REST](https://github.com/mtf-exchange/metaflux-knowledges/blob/main/api/rest/README.md) — `POST /exchange`, `POST /info`, and the HL-compat / CCXT-compat surfaces
* [WS](https://github.com/mtf-exchange/metaflux-knowledges/blob/main/api/ws/README.md) — subscriptions (coming)

### [Integration](/integration.md)

* How to bring an HL-style client over with zero code change
* Authentication & signing (EIP-712, agent wallets)

### [Concepts](/concepts.md)

* Cross-asset portfolio margin
* Tiered liquidation (T0 yellow card → T1 partial → T2 full → T3 backstop → T4 ADL)
* API wallets / agent delegation
* Sub-accounts

### [MIP](/mip.md)

* MIP-3 permissionless market deploy (perp / spot)

### [Bridge](/bridge.md)

* USDC via Circle CCTP
* Other assets via a single third-party bridge (selection TBD)

## Conventions

* All endpoints documented here are the **stable, public** wire surface.
* Request / response examples use real shapes — copy-paste safe.

## Status legend

Each doc carries a "Status" tag near the top:

* **stable** — wire shape committed for V1; can build against it.
* **preview** — works today; minor wire changes possible before mainnet (will be called out).
* **planned** — described but not yet shipped.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.mtf.exchange/readme.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.