> For the complete documentation index, see [llms.txt](https://openmetacity.gitbook.io/omc-v0.7-en/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://openmetacity.gitbook.io/omc-v0.7-en/platform/core-systems/nft-marketplace-tbu.md).

# NFT Marketplace (TBU)

## Trading Methods and Procedures

*  The transaction is executed between the seller and the buyer using a multi-party relative bargaining method.
* The buyer must complete the registration to receive the NFT.

## Transaction method

The goods used in the transaction are OMC.

## Fee

The fees associated with NFT transactions include the transaction fee paid by the seller and the registration fee paid by the buyer when registering.

**\[Transaction fee]** 

* Seller: 3% 
* Buyer: 0% 
* Payment method: OMC 

**\[Registration fee]** 

* Buyer: Fixed fee based on grade 
* Payment method: Clover

{% hint style="info" %}
Clover is a virtual currency used in the service.
{% endhint %}

*Future updates planned*


---

# 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://openmetacity.gitbook.io/omc-v0.7-en/platform/core-systems/nft-marketplace-tbu.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.