> 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/portfolio-and-chat.md).

# Portfolio & chat

Path: `/portfolio`

## Tabs

| Tab                 | Purpose                                                  |
| ------------------- | -------------------------------------------------------- |
| **Owned NFTs**      | Your wallet NFTs on the app cluster (search + Show more) |
| **Listed Swaps**    | Offers you created that are still active                 |
| **Incoming Offers** | Swaps you can accept                                     |
| **History**         | Completed, cancelled, or expired swaps                   |
| **Favorites**       | Saved collections (when available)                       |

## Sharing a swap

On `/swap/[id]` use **Copy Link** or **QR Code** to send the offer. Private offers still only accept from the designated receiver wallet.

## Trade Chat

* Available when the offer is **Open to offers** (firm offers may limit counters)
* Never share seed phrases or private keys
* Chat does not move assets — only signed escrow transactions do

## Alerts

`/notifications` shows activity and chat notices. You can adjust prefs under **Settings**.


---

# 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/portfolio-and-chat.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.