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

# Phase4 AI

## Most Reliable Trading Partner

#### Functions:

\- Can help users deal with token trading demands and be a 24-hour online intelligent trading assistant.

\- Can give users risk tips. In the process of setting a sell instruction for users, when the real-time price exceeds the set selling price, Hasaki can send a price fluctuation reminder to the user and ask if the user wants to sell at the highest price.

#### Function example:

\- User issued an instruction after he connects the wallet: "Sell ETH for 2000 USDT." 

\- Hasaki responds: "Start checking the ETH price on the chain and automatically sell ETH via Uniswap when the price reaches 2000 USDT." 


---

# 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://hasaki-docs.gitbook.io/white-paper/roadmap/phase4-ai.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.