> For the complete documentation index, see [llms.txt](https://docs.everyworld.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.everyworld.com/everyworld-abstract/how-everyworld-works/payouts.md).
# Payouts
The pool of $EVERY that is allocated to each Jackpot is equal to the number of Tickets in each pool. Payouts will be paid out as follows:
* 40-45% to the individual Jackpot winner
* 40-45% to be donated to environmental conservation organizations
* 0-10% to any users above the winning user in a Referral Tree\*
* 10% to be burned
*\* If less than 10% of the Payout is earned through the referral tree, the remainder is split equally between the Jackpot winner and the conservation organization. If the winner does not have anyone above them in a Referral Tree, the winner and the conservation organization will each receive 45% of the Payout.*
Winners of Jackpots will be required to adhere to the applicable terms and conditions including know your customer (“KYC”) rules and restrictions. Winners will receive $EVERY tokens based on a 3 year vesting period where tokens are unlocked on a monthly basis with the initial unlock upon delivery of the payouts.
---
# 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.everyworld.com/everyworld-abstract/how-everyworld-works/payouts.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.