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

# Introduction

**introducing Apebets NFT: Unleashing a New Era in NFT Utility and Community Betting**

Welcome to ApeBets, where owning an NFT means more than just collecting a digital token - it's your ticket to a world of exclusive sports betting insights. Imagine getting a front-row seat to the action with our team of accomplished professional sports betting, analyst, who have a 65%+ success rate in major sports like Basketball , Baseball, Hockey  Football, European football, and  MMA. With ApeBets, you're not just holding an NFT - you're holding the key to a riveting, high-stakes sports betting experience like no other. In other words, 

<figure><img src="/files/KP7Nle0DbS7YKOt0xP4k" alt=""><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://apebets-organization.gitbook.io/apebets-nft-whitepaper/introduction.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.