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

# Summary

The BeeHive Protocol presents a structured and incentivised approach to DeFi participation through its unique combination of tokens, staking mechanisms, and reward distribution. The protocol aims to create a balanced and rewarding ecosystem for all participants.

Key Highlights:

* **Minimum Entry**: 100K PLS tokens.
* **Dynamic Participation**: Users can tailor their investment through the purchase of flowers and bees.
* **Flexible Rewards Management**: Multiple options for claiming and utilising earned Honey Tokens.
* **Sustainable Tokenomics**: Balanced distribution of tokens to support growth, development, and participant rewards.
* **Long-Term Incentives**: A Tiered rewards system encouraging extended staking periods for higher returns.

The BeeHive Protocol thus offers a comprehensive and engaging platform for users looking to invest in a decentralised, community-driven financial ecosystem.


---

# 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://docs.powercity.io/beehive/summary.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.