> For the complete documentation index, see [llms.txt](https://docs.polygoatbot.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.polygoatbot.com/readme.md).
# Execution Infrastructure for Prediction Markets
Execute before the market reacts. PolyGoat Whitepaper, 2026.
## What is PolyGoat?
PolyGoat is a **real-time execution system** designed to capture short-lived pricing inefficiencies in prediction markets. It removes the barrier between intent and execution — giving any user access to infrastructure that previously required dedicated engineering teams.
## Not a trading bot
PolyGoat is an **execution layer** — a system that sits between the user and the market, handling all the complexity that makes high-frequency prediction market trading inaccessible to most people.
## Execution is the edge
> "PolyGoat doesn't predict whether BTC goes up or down. It detects the 8-second window where the market hasn't decided yet — and enters before it does."
---
# 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.polygoatbot.com/readme.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.
