> For the complete documentation index, see [llms.txt](https://avano.gitbook.io/dmeter/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://avano.gitbook.io/dmeter/tokenomics/innovation.md).
# Innovation
dMeter rewards you for coming up with new ideas, like inventing a new way to sense clean water or protect animals.
\- When you have a cool idea, you share it with the community. If it’s great, you get tokens as a reward.
\- Sometimes, you might work with friends on an idea, and everyone gets their fair share of the rewards.
\- If your idea keeps helping for a long time, you’ll keep getting rewards whenever it’s used.
\- When your idea is really successful, dMeter shows it off to everyone so others can be inspired.
\- Some tokens go towards starting new projects or investing in established ones to make dMeter even stronger.
\- dMeter also gives extra tokens when you invite friends to join or when you start for the first time.
\- dMeter is open to people all over the world, making it useful no matter where you live. The tokens you earn can be used to vote on important decisions or get special advice. You help guide the future of dMeter.
\- dMeter uses tokens to form partnerships with other organizations, helping us grow and reach new people.
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://avano.gitbook.io/dmeter/tokenomics/innovation.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 `automate deployments from our CI pipeline` 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.