> For the complete documentation index, see [llms.txt](https://doc.catrix.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.catrix.xyz/executive-summary.md).
# Executive Summary
Wall Street Alpha for All, Powered by Decentralized AI
Catrix is building a **Decentralized AI Trading Platform** for the AI era.\
\
We're solving the biggest inequality in finance: the gap between those with access to advanced tools and those without. For years, **top-tier trading strategies, high-frequency systems, and 24/7 risk management** have only served wealthy institutions. Regular investors are left to trade on emotion and outdated information, leading to predictable losses. Catrix is here to end this.
By building an Automated Wealth Engine powered by Large Language Models (LLM) and a Multi-Agent trading system, Catrix turns hedge fund-level investment strategies into a simple interface anyone can use. Our unique "**Simulation-as-Training" data flywheel** continuously learns from millions of real user behaviors, creating an unbeatable data advantage.
**Our mission is clear: Give everyone access to Wall Street's best AI-powered automated asset management - for any amount of money, across global markets including Crypto and U.S. Stocks.**
---
# 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://doc.catrix.xyz/executive-summary.md?ask=&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.
