> For the complete documentation index, see [llms.txt](https://docs.sire.bot/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sire.bot/get-started/mission-and-purpose.md). # Mission & Purpose #### **Mission** SIRE’s mission is to make advanced sports intelligence openly accessible through decentralised infrastructure.\ It connects data science, machine learning, and on-chain automation to create a transparent intelligence layer anyone can use, democratising institutional-grade analytics for real-world, uncorrelated performance. #### **Core Principles** * **Transparency:** All activity, fees, and agentic execution are verifiable on-chain. * **Accessibility:** Open participation in SIRE’s intelligence network, with access to data-driven, uncorrelated performance. * **Alignment:** Users, holders, and the protocol advance together through shared incentives. * **Autonomy:** AI agents continually learn from live data, refine their models, and execute strategies directly on-chain. * **Fairness:** SIRE launched through a fair, open-market distribution — with no presale, private allocation, or insider advantage — ensuring the network’s ownership and opportunity remain in the hands of its community. #### **Who It’s For** * **Sports Bettors:** Use model-driven insights to make data-backed decisions and manage risk. * **DeFi Users:** Diversify exposure with uncorrelated performance opportunities by adding USDC to receive αVault units and staking SIRE for reduced fees. * **DeFi Protocols & Partners:** Integrate αVault and αLink to give communities direct access to SIRE’s intelligence stack and on-chain execution. * **Contributors & DAO Members:** As a community-owned protocol, anyone can contribute research, build integrations, propose improvements, or support ecosystem growth through governance and bounties. --- # 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.sire.bot/get-started/mission-and-purpose.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.