> For the complete documentation index, see [llms.txt](https://rektofun.gitbook.io/rektofun/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://rektofun.gitbook.io/rektofun/welcome-to-rektofun.md).
# Welcome To RektoFun
## What exactly is rekto.fun?
RektoFun is a **PvP prediction battleground** where users compete on market outcomes.
Users can create and join challenges based on:
* Crypto price movements
* Sports events like IPL, FIFA, MMA, etc..
We believe prediction markets should be social and permissionless to everyone.
We are building a **competitive and permissionless prediction ecosystem** where users don’t just participate, they **compete and earn** in a transparent, real time environment.
By combining the excitement of real time PvP competition with market forecasting, our platform creates a unique ecosystem where top traders rise through skill and performance.
Users can:
* Challenge others directly in PVP battles
* Join **multiplayer challenges**, choosing sides based on their conviction
* Compete for shared prize pools where the **winning side takes it all**
---
# 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://rektofun.gitbook.io/rektofun/welcome-to-rektofun.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.