> For the complete documentation index, see [llms.txt](https://docs.midasmarkets.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.midasmarkets.xyz/about/why-are-we-building-this.md). # Why are we building this? Markets move faster than interfaces. Midas exists to compress research, portfolio awareness, and execution into one coherent workflow. * **Information is fragmented** — Traders bounce between social feeds, charts, wallets, bridges, exchanges, and spreadsheets. * **Execution is fragmented** — The right action may require a Solana swap, EVM bridge, protocol deposit, perp order, or withdrawal. * **AI needs tools** — A useful markets AI needs live data, account context, and safe action boundaries, not only text output. ## The problem The average trading stack makes the user assemble context manually. They read social feeds in one place, analyze charts in another, move funds in a wallet, route a bridge elsewhere, and finally trade on a venue. That fragmentation slows users down and increases the chance of acting on stale, incomplete, or mismatched information. ## The Midas answer Midas brings the loop into one interface. The product does not remove judgment; it makes the relevant context easier to see before the user acts. * Market feeds explain what is moving. * Analysis pages explain why it might matter. * Portfolio context explains what the user already owns or risks. * Execution routes let the user act after explicit confirmation. ## Why now Wallet infrastructure, cross-chain routing, perpetual venues, and AI tooling are mature enough to combine. Midas is built for that convergence. --- # 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.midasmarkets.xyz/about/why-are-we-building-this.md?ask=&goal= ``` `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.