> For the complete documentation index, see [llms.txt](https://docs.grix.finance/grix/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.grix.finance/grix/introduction.md). # Introduction Grix is building the data and infrastructure foundation specifically for AI-powered *derivatives* trading, simplifying access and analysis for both traders and AI agents. We address the challenge of fragmented *derivatives* data in DeFi by leveraging the Model Context Protocol (MCP). By implementing MCP (or providing dedicated plugins for leading AI platforms), Grix offers a standardized way for AI agents to connect to comprehensive *derivatives* data from across the DeFi landscape, creating a unified source of high-quality information. This allows AI agents to access diverse *derivatives*-related data sources, generate insightful signals, and execute sophisticated strategies more efficiently. Ultimately, Grix envisions providing a full suite of modular *derivatives* trading tools accessible through AI agents, further streamlining the DeFi *derivatives* experience. The $GRIX token empowers community governance and unlocks access to premium features within the ecosystem. Through strategic partnerships with leading AI platforms and DeFi derivatives protocols, Grix is fostering a more intelligent, accessible, and efficient *derivatives* market, unlocking new opportunities for everyone involved in the AI-driven DeFi revolution. --- # 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.grix.finance/grix/introduction.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.