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

# Explore (Trade Board)

Path: `/explore`

Browse live swap offers other traders have listed.

## What you’ll see

* Cards for public (and filter-eligible) swaps
* Offering vs requesting previews
* Visibility badge, expiry, and status (e.g. **Awaiting counterparty**)

## Filters & discovery

Common filters (labels in the UI):

| Filter     | Examples                                              |
| ---------- | ----------------------------------------------------- |
| Collection | Narrow by NFT collection                              |
| Trade type | NFT ↔ NFT, NFT + SOL, Bundle, Collection-style offers |
| Other      | Search / SOL-related filters when available           |

Click a card to open the full **swap detail** page before you accept.

## Tips

* Always open the swap and verify mints and amounts — board cards are summaries.
* **Link** offers may not appear like full public listings; use the shared URL.
* Private offers only work for the designated receiver wallet.


---

# 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://niftix.gitbook.io/niftix-docs/using-the-app/explore.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.