> For the complete documentation index, see [llms.txt](https://village-labs.gitbook.io/coworker-product-and-developer-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://village-labs.gitbook.io/coworker-product-and-developer-docs/legacy-knowledge-base/awards.md). # Awards ## Introduction Village lets you distribute any source of value in an automated way. One output operation that occurs when a rule executes is the distribution of an award. Awards come in various forms, such as cash, or non-monetary units like points or credits, status, badges, and digital assets. Because all awards are created and configured within Village, you're able to tailor these awards to a very flexible set of use cases. The following pages walk through the different types of awards, how they are created and configured, and their various use cases. It’s worth noting that these fall into two broad categories: Fungible Awards and Non-Fungible or Unique Awards. * **Fungible awards** are interchangeable and include cash and non-monetary awards like points or funded awards. * **Non-Fungible awards** are unique and include badges, status, digital assets and coupons like discount codes or promos. --- # 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 following URL with the `ask` and `goal` query parameters: ``` GET https://village-labs.gitbook.io/coworker-product-and-developer-docs/legacy-knowledge-base/awards.md?ask=&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 `build a script that syncs our docs to a CMS` 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.