> For the complete documentation index, see [llms.txt](https://docs.epsilon.exchange/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.epsilon.exchange/products/portfolio.md).

# Portfolio

The Portfolio gives you a single view of your on-chain activity across every wallet linked to your account.

## All your wallets, one dashboard

Balances, PnL, and history are aggregated across your embedded trading account and every linked external wallet. Wallet chips at the top let you filter down to any single wallet, or view everything combined.

## Overview

Summary cards show your key numbers at a glance:

* **Portfolio value** and number of assets held.
* **Total PnL** with percentage return.
* **Unrealized PnL** across open positions.
* **Realized PnL** from closed trades.
* **Open orders** and **active DCAs** counts.

## Allocation

An allocation breakdown visualizes how your value is distributed across your holdings, with smaller positions grouped together.

## Holdings, trades, and orders

Tabs let you drill into:

* **Holdings**: per-token balance, average price, current price, value, and unrealized PnL.
* **Trades**: your swap history.
* **Open orders / Active DCAs**: automation you can manage or cancel.
* **History**: filled, cancelled, and expired orders together with swaps.


---

# 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://docs.epsilon.exchange/products/portfolio.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.