> For the complete documentation index, see [llms.txt](https://queenbee-swap.gitbook.io/queenbee-paper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://queenbee-swap.gitbook.io/queenbee-paper/introduction.md). # Introduction ### Project & Ecosystem The QueenBee project is a decentralized finance (DeFi) protocol that facilitates safe and efficient token exchange through an Automated Market Maker (AMM) \ \ In the DeFi AMM ecosystem \ QueenBee Token plays an essential role in providing access to highly liquid markets with low transaction costs for users \ \ QueenBee Token provides users with the opportunity to earn high returns on their investments through staking, farming, and lending \ The project is based on transparent and secure blockchain technology and has a development policy focused on providing an excellent user experience and sustainable long-term growth. \ \ In this Gitbook Page users can find complete information about the basic concepts of DeFi AMM, the tokenomics of QueenBee Token, the implementation of the QueenBee Token protocol, and a guide on how to use the QueenBee Token platform. --- # 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://queenbee-swap.gitbook.io/queenbee-paper/introduction.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.