> For the complete documentation index, see [llms.txt](https://docs.safrootics.com/whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.safrootics.com/whitepaper/tokenomics-and-value/nfts/4.the-marketplace.md).
# 4.The Marketplace
Players would be able to list and trade their unique Tics on the marketplace with other players. All in-game items and assets living on the blockchain and can be purchased or transferred easily on the Safrootics marketplace.
Founder's Badges holders will be receiving a  from every non-Founder's Badge NFT sale on the marketplace, this includes Tics, and in-game items.
{% hint style="info" %}
**Notes:**\
Percentages will be distributed equally amongst all of the same badges, for example 1% of sales will be distributed amongst all Gold Founder’s Badges.
Sales share applies to all non-Badges NFT sales in the marketplace, badge sales are not included.
Players can buy more than one badge and the sales share will stack, however the in-game perks will not stack and the game will detect the highest badge owned and will apply the benefits accordingly for one badge.
{% endhint %}
---
# 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.safrootics.com/whitepaper/tokenomics-and-value/nfts/4.the-marketplace.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.