> 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/market-scope.md).

# Market Scope: Where PolyGoat Operates

PolyGoat does not guess market direction. It exploits a structural, mathematically definable inefficiency present in every short-duration prediction market: **the gap between when a price should change and when it actually does**.

## Market types

PolyGoat targets 5- and 15-minute binary crypto markets. Daily, weekly and event/political markets are out of scope — their outcomes depend on analysis and information asymmetry, where latency gives no advantage.

<figure><img src="/files/KEnBFE2I6TBx05tadB00" alt="5-minute and 15-minute markets are active targets; daily and event markets are out of scope"><figcaption></figcaption></figure>

## The LIVE section: why it matters

Within Polymarket, PolyGoat targets exclusively the **LIVE section** — markets currently accepting orders with a countdown timer running. This is where pricing inefficiency is highest. A market qualifies only when all four criteria are met at once.

<figure><img src="/files/2AbJVc9WKyKJ9welOgba" alt="Four qualification criteria: LIVE status, 5 or 15 minute duration, crypto underlying, sufficient liquidity"><figcaption></figcaption></figure>

## Why 5 and 15 minutes: the efficiency sweet spot

Not all timeframes offer the same execution edge. Too short — no liquidity, impossible to fill. Too long — the market corrects before entry and the latency advantage disappears.

<figure><img src="/files/EvfsbvVlYSLgWkc1tDmD" alt="Under 5 minutes too short, 5-15 minutes optimal zone, over 30 minutes too long"><figcaption></figcaption></figure>


---

# 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/market-scope.md?ask=<question>&goal=<endgoal>
```

`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.