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

# Introduction

WagerGang is the first original smart contract protocol built to disrupt the old bookmaker model. 

Traditional Bookmakers have an edge over you by fixing the odds and taking a substantial cut.

**WagerGang disrupts this old model** and makes wagers on sports contest 100% transparent.

**No odds, no handicap.**

We have lots of additional features that let you **earn official sports teams tokens**, **exchange your favorite sport star NFTs** or just **stake your GANG tokens for farming.**

**The GANG token also allows you to take part and vote on every family decision.**

 Let's get rid of these old bookies together!

Join Don CoonFather and be part of the family

![](/files/C24rOskaVI5H2kTeJJmf)


---

# 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://wagergang.gitbook.io/wagergang/master.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.