> For the complete documentation index, see [llms.txt](https://crypto-bike.gitbook.io/crypto-bike.game/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://crypto-bike.gitbook.io/crypto-bike.game/my-account/my-nfts.md).
# MY NFTs
The My NFTs section displays all NFT items the user has acquired in the game. \
\
Rent Bike - Give opportunity to user choose the right bike and rent him for other user in market place. Timing and price of rent user put by him self. Token for rent will be in MTCB per hour.
\
Sell\Return - as well from My NFT page users can choose what he want sell ist can be Bike, Parts or charaters. He can sell NFT only in MTCB\
\
Create NFT account - give opportunity to create NFT Account, with many uniqe functions \
\
Sell NFT account - selling entire account and all NFT with metadata on it, on the marketplace. When you decide sell account automatically you will sell consumables balance from the game, so before sell check you balance.
---
# 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://crypto-bike.gitbook.io/crypto-bike.game/my-account/my-nfts.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.
