> For the complete documentation index, see [llms.txt](https://docs.zvaultmarketplace.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zvaultmarketplace.xyz/pricing-and-fees.md).

# Pricing and Fees

The marketplace fee is **5% of the agreed NFT price**. The seller receives the other **95%**. The fee is paid in real ZEC as part of a completed trade, not in a test token.

| Listed or accepted price | Seller receives | Platform receives |
| -----------------------: | --------------: | ----------------: |
|                 0.20 ZEC |        0.19 ZEC |          0.01 ZEC |
|                 1.00 ZEC |        0.95 ZEC |          0.05 ZEC |
|                 2.00 ZEC |        1.90 ZEC |          0.10 ZEC |

**Formula:** seller amount = price × 95%; platform amount = price × 5%.

The buyer's wallet is asked to send these amounts in two separate Zcash mainnet transactions. The displayed trade price is the sum of the two amounts. Standard blockchain transaction fees are separate and depend on the wallet and network.

{% hint style="warning" %}
**Network distinction:** The ZEC payments are real mainnet funds even though the NFT is a ZSA test-network asset.&#x20;
{% 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.zvaultmarketplace.xyz/pricing-and-fees.md?ask=<question>&goal=<user_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.
