> For the complete documentation index, see [llms.txt](https://docs.edgepoly.fun/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.edgepoly.fun/overview.md). # Overview Overview Edge Poly is the first chain-reaction automation layer for prediction markets. Built on top of Polymarket, Edge Poly lets traders create pre-programmed sequences of bets so that capital moves automatically along a narrative as events resolve. Instead of waiting, claiming, and re-entering manually, users can say: IF Market A resolves YES, THEN deploy winnings into Market B. That simple automation turns dead capital into continuous, narrative-driven exposure. Edge Poly is designed for speed, composability, and usability. Users design Chains visually, set risk and slippage rules, and let the platform execute. For early adopters this means catching the next narrative wave faster, compounding outcomes across markets, and trading causality rather than isolated odds. --- # 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.edgepoly.fun/overview.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.