> For the complete documentation index, see [llms.txt](https://polysport.gitbook.io/polysport/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://polysport.gitbook.io/polysport/development/development-plan.md).

# Development plan

<figure><img src="/files/i9YBsi7psEMxa9fn4dBJ" alt=""><figcaption></figcaption></figure>

* The team is currently developing a custom market where all Polysport NFTs will be tradable. As a bonus for the Polysport game, a proportion of the fees generated on the Market will be allocated to the Polysport game pool.
* Marketplace provides a platform where users can buy and sell various NFTs with each other. Users can set the price of their own NFTs and initiate sales orders. Buyers can buy what they like with listing prices. After the transaction is done, buyers will receive the NFTs from the seller, where a certain percentage of transaction fees and NFT royalties are drawn from the transaction amount. The marketplace is used both inside our game apps and on Starkfinance's official websites.
* We may develop our own NFT Marketplace. And we may also consider providing APIs to third-party partners and authorizing them to build up the NFT Marketplaces.


---

# 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://polysport.gitbook.io/polysport/development/development-plan.md?ask=<question>&goal=<endgoal>
```

`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.