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

# ONI.exchange INTRODUCTION

![oni.exchange](/files/-MYavKxxvG2U26GBHF_K)

ONI.exchange is a **intelligent decentralized exchange** running on Binance Smart Chain, with AMM, NFTs and Yield Farming.

ONI was build for a community. It was built for you to make profit. It was built for you to control it.

### Main Features

#### ↔️ Trade

The ONI exchange is an automated market maker (“AMM”) that allows two tokens to be exchanged on the Binance Smart Chain.

NFT Hub & Marketplace - Buy, sell, trade, breed our Robots and Minions and use them in our game later. (soon)

#### 💸 Earn

On top of that, you can earn ONI with yield farms, earn ONI with Staking, and earn even more tokens with Fuel Pools, Games, upcoming NFT Marketplace and more.

#### 🎲 Win

Play games we added for you and win some serious cash!\
\
                                                                         **QUICK PRESENTATION**

![](/files/-MZBjij39AShpY1GH88z)


---

# 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 dynamically by asking a question.

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

```
GET https://oni-exchange.gitbook.io/oni-exchange/master.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.