> For the complete documentation index, see [llms.txt](https://docs.chikn.farm/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.chikn.farm/nfts/roostr-nft/architecture.md). # Architecture Everyone knows that chikn lay $EGG, and Roostr squirt $FERT. The need to rhyme is stronger than we are. Roostr produce the all-important $FERT—a token that can be used to improve FarmLand reward yields among other things. For more information on what $FERT can be used for, see the section on[ $FERT](/tokens/fert.md). To produce $FERT, Roostr need to eat $EGG. These protein-rich ovals pass through the Roostr’s digestive system, helping them grow bigger and coming out the other end as $FERT.

The $FERT Cycle - animation by linsanity

Roostr bring added complexity to the Chikn game and give players the opportunity to optimize their Farming strategies. With the rollout of Foraging introducing new ways to spend $FERT, Roostr themselves have become even more important in the broader meta. --- # 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.chikn.farm/nfts/roostr-nft/architecture.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.