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

# Introduction

Fat pandas will do anything for $BAMBOO

### Overview

Pandabera is a blockchain based deflationary model idle game with a halving based emission schedule, fixed supply, referral incentives, and token burns to ensure long term sustainability.

Once you strategically level up your panda and equip the pouch with the best tools, your panda can become a tradable NFT, ready to harvest $BAMBOO&#x20;

### Brief

In the world of Pandabera, fat pandas will do anything to collect $BAMBOO using Harvesting tools from their Panda Pouches. This system reimagines decentralized mining with harvesting tools and strategic thinking utilizing the limited pouches capacity and harvesting power.&#x20;

The token economy is governed by a fixed supply, predictable halving schedule, and on chain burning mechanics, creating a fair and transparent environment for all players.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.pandabera.fun/introduction.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
