> For the complete documentation index, see [llms.txt](https://docs.zoryu.trade/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zoryu.trade/overview.md).

# Overview

### What is Zoryu Trade

**Zoryu Trade** is a non-custodial trading terminal built for the Solana ecosystem, designed to unify **market data, AI-assisted trade intelligence, and on-chain execution** into a single, coherent system.

Zoryu is not an exchange, a broker, or a custodial platform. It does not hold user funds, manage private keys, or execute trades on behalf of users. Instead, it operates as a **trading infrastructure layer**, providing structured decision support and execution workflows while all assets remain fully under user control.

Unlike conventional trading dashboards that focus primarily on charts and indicators, Zoryu treats trading activity as a **stateful process**. Signals, positions, and execution outcomes are tracked systematically, allowing traders to evaluate performance based on real data rather than subjective interpretation.

Zoryu is built for traders who require clarity, execution transparency, and measurable outcomes without relying on opaque automation or centralized control.


---

# 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://docs.zoryu.trade/overview.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.
