> For the complete documentation index, see [llms.txt](https://www.aevo.xyz/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.aevo.xyz/docs/aevo-products/aevo-exchange/trading-on-aevo/fair-usage-disclaimer.md).

# Fair Usage Disclaimer

Self-trading within a single account or across multiple accounts under common control is strictly prohibited. Aevo maintains a zero-tolerance policy toward any form of market manipulation, including but not limited to wash trading, spoofing, layering, quote stuffing, and artificial price manipulation. The platform employs advanced surveillance systems to detect suspicious trading patterns, anomalous order behavior, and coordinated manipulative activity.

Violations of these policies may result in immediate trading suspension, permanent account termination, forfeiture of rewards or incentives, and reversal of trades associated with manipulative behavior.

Aevo reserves the right to take any necessary actions, including freezing assets, clawing back ill-gotten gains, and reporting violations to regulatory authorities, to protect its users, ensure fair price discovery, and maintain the integrity of the marketplace. All users are expected to trade in good faith and contribute to a transparent, efficient trading environment.


---

# 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://www.aevo.xyz/docs/aevo-products/aevo-exchange/trading-on-aevo/fair-usage-disclaimer.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.
