> 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/explore-nfts.md).

# Explore NFTs

**Explore** is the public starting point for discovering available NFTs. Each card shows the NFT image, name, collection, and current listing status when that information is available.

## Browse and inspect

{% stepper %}
{% step %}

## Open Explore

Open **Explore** from the site navigation.
{% endstep %}

{% step %}

## Select an NFT

Select an NFT card to read its detail page.
{% endstep %}

{% step %}

## Check NFT details

Check the collection name, asset identifier, image, and listing price.
{% endstep %}

{% step %}

## Buy or make an offer

Use **Buy now** for an active listing or **Make Offer** where available.
{% endstep %}
{% endstepper %}

The public collection list is restricted to the configured ZSA test-network data source. Its market figures should come from the marketplace service and indexed activity, not sample NFTs or placeholder statistics. If the source has no verified records, an empty state is expected.

{% hint style="warning" %}
**Before paying:** Check that you are viewing the intended NFT and that the total ZEC amount matches the wallet prompts. A listing price already includes the 5% platform share; see [Pricing and the platform fee](https://docs.zvaultmarketplace.xyz/pricing-and-fees.md).
{% endhint %}

For the full sequence after selecting **Buy now**, continue to [Buy an NFT](https://docs.zvaultmarketplace.xyz/buy-an-nft.md).


---

# 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/explore-nfts.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.
