> For the complete documentation index, see [llms.txt](https://spredict.gitbook.io/whitepaper-v1/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://spredict.gitbook.io/whitepaper-v1/market-and-competition.md).

# Market & Competition

The sports and eSports market is significant. The most popular sports in terms of fan base is soccer with more than five billion fans around the world, followed by Formula 1 with one billion fans. Taken together with all the other sports and eSports that exist, the potential market reach is exponential. 

The main goal of Spredict is to secure a portion of this sizable fan base by delivering an intuitive platform that engages fans in entirely new and different ways with innovative prediction methods and newly developed games and game modes.

<figure><img src="/files/LKvfNEew1LYVKI5dTKZT" alt=""><figcaption><p>Market analysis from November 2024</p></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://spredict.gitbook.io/whitepaper-v1/market-and-competition.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.