> For the complete documentation index, see [llms.txt](https://feeda.gitbook.io/litepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://feeda.gitbook.io/litepaper/6.-how-feeda-works.md). # 6. How Feeda Works ### Mechanics of the Knowledge Economy ### 6.1 Contributing Knowledge and Earning Feeda Tokens Users can contribute insights, updates, and new information to the Feeda Knowledge Base, earning Feeda Tokens for their contributions. This process incentivizes a community of contributors who actively enrich Feeda’s content, creating a decentralized, reward-based knowledge economy. ### 6.2 Knowledge Curation and Verification Feeda’s AI-driven verification system cross-references content with credible sources, while human moderators review flagged entries for quality control. This dual-layered system maintains a high standard of accuracy and ensures that Feeda’s knowledge remains reliable and up-to-date. ### 6.3 Accessing and Utilizing Knowledge Users can access Feeda’s knowledge through Feeda aiOS, which enables seamless interaction with Feeda applications and agents. The platform’s advanced search capabilities and personalized recommendations help users navigate and utilize knowledge effectively. --- # 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://feeda.gitbook.io/litepaper/6.-how-feeda-works.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.