> 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/why-polygoat-exists.md).
# Why PolyGoat Exists
In short-duration markets, a human trader loses **not on analysis — but on reaction time**.
## Latency kills profit
The execution timeline of a human trader vs an execution system, within the same opportunity window. A human needs 2–5 seconds to notice, decide and submit. PolyGoat needs \~100–150ms.
{% hint style="warning" %}
On a $5,000 position, a 5¢ difference in entry price = **$250 in lost edge per trade** — not from a wrong decision, but purely from reaction delay.
{% endhint %}
## Three scenarios, same market
Same market, same outcome, same $5,000 position — only execution speed differs. PolyGoat captures **6.7× more edge** than a manual trader on an identical trade.
This is the core product proposition: **infrastructure as alpha**.
---
# 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.polygoatbot.com/why-polygoat-exists.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.