> For the complete documentation index, see [llms.txt](https://whitepaper.memetheftauto.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://whitepaper.memetheftauto.com/usdmta-token/tokenomics/marketplace-reserve-15.md).
# Marketplace Reserve 15%
150,000,000 $MTA
The Marketplace Reserve fuels the marketplace itself: product orders, maker payments and marketplace rewards. These tokens are spent on marketplace fulfilment and nothing else. They are never sold on the open market and never converted to stablecoins or fiat by the project.
### **Schedule:**
Locked for 1 month after listing, then released evenly over 12 months (12.5M per month). Released tokens that aren't needed for fulfilment stay in the reserve wallet.
#### **How the marketplace feeds back into $MTA.**
Every marketplace purchase is paid in $MTA, which buyers acquire from the pool. Makers are paid in $MTA; a maker who prefers cash is paid from the pool's accumulated trading fees, and the $MTA from that sale is split 50% to the Treasury and 50% burned. Each sale therefore either passes tokens to a maker or removes them from circulation — the marketplace is a source of demand and a source of burns, never a source of sell pressure from the project.
#### Wallet: m3bbJCXvuGq2GCxtZVW6yDciBQfi81dWUzehWhmymTA
---
# 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://whitepaper.memetheftauto.com/usdmta-token/tokenomics/marketplace-reserve-15.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.
