> For the complete documentation index, see [llms.txt](https://docs.coinhall.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.coinhall.org/mission-control/about-us.md). # About Us Welcome onboard, fellow Astronaut ## Mission Coinhall ([coinhall.org](http://coinhall.org/)) is the leading Interchain Trading Terminal, offering a seamless and performant trading platform for amateurs and pros alike. You can access real-time price charts, liquidity pool analytics, and perform aggregated swaps across AMM DEXes on the supported networks. We are also active community validators, deeply involving ourselves in the growth of the ecosystems. While data from most blockchain is publicly *available*, it does not mean that they are *accessible*. Our mission is simple - **to make sense of data so you don’t have to**. Our goal is to support you with accurate and reliable data to aid you in making your own informed decisions. ## Partners ### TradingView The charts seen on Coinhall are powered by TradingView, an advanced platform for traders and investors. Supercharged by robust technologies across browser, desktop and mobile apps, the platform provides unparalleled access to live data e.g. [BTC USD chart](https://www.tradingview.com/symbols/BTCUSD/), the latest news, financial reports, Stock screener and Economic calendar. --- # 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://docs.coinhall.org/mission-control/about-us.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.