> 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/what-is-spredict.md).

# What is Spredict?

Spredict is built on three foundations: a **Free-To-Play** element, a **Predict-To-Earn** (Spredict Pass) subscription service, and **Custom-To-Win** bespoke-built opportunities. As sports fans themselves, the team aims to build a new kind of gamified prediction experience for fans to be able to enjoy sports and non-sports events while efficiently and effectively setting their picks on a user-friendly platform. 

Spredict currently utilizes a proprietary blockchain to minimize costs to users and allow for effective design and modifications of the Spredict dApp (<https://dapp.spredict.io>) while using the blockchain as a key element of its ecosystem.&#x20;

Players can win in a number of ways in the Spredict ecosystem. They can:

* Win native token, $SPI, prizes in single event, tournament, monthly or season subscription pools. These pools will allow projects/lounges to compete against and with each other to win prizes.
* Earn revenue share by staking and claiming $SPI or $ETH after the SPI launch through the Spredict staking protocol. A portion of monthly revenue will be distributed to $SPI stakers on top of the tax revenue.
* Gain native token by staking a project NFT. These tokens have been set aside each year for the first three years of the project’s lifespan and the revenue sharing model will increase this staking allowance, making holding an NFT incredibly lucrative.

<figure><img src="/files/vaptWAXWnmlfSOAO4VGk" alt=""><figcaption><p>Spredict Product overview</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/what-is-spredict.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.