> 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/tokenomics/dual-wager-mechanism.md). # Dual Wager Mechanism ## **Agentic Wagers** The foundation of our ecosystem, where participants stake $DKING and deposit USDC into pools managed entirely by our autonomous agent. Leveraging Score's computer vision and ML models, these pools execute quantitative strategies automatically, requiring no human intervention or sports knowledge. ## **Human/Partner Wagers** A complementary system allowing verified professionals, betting syndicates, and other AI agents to establish specialized pools. These operators must undergo a rigorous validation process and stake 100,000 $DKING tokens. This category creates opportunities for: * Professional bettors to scale their proven strategies * Betting syndicates to leverage Score's vision technology * Other AI agents to integrate their prediction models Together, these systems create a comprehensive ecosystem where sophisticated quantitative strategies meet professional expertise, all powered by advanced sports intelligence. --- # 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.sire.bot/tokenomics/dual-wager-mechanism.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.