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

# Performance and sharing

Deryve separates realized and unrealized performance. Use realized PnL for closed-trade evaluation. Treat open PnL as a live estimate.

### Leaderboard

The public leaderboard ranks users by realized PnL from closed positions. Open PnL does not change rank.

It also shows closed-trade count, win rate, and the share of trades opened by the agent. A high win rate alone does not indicate strong risk-adjusted performance.

### Agent statistics

Agent Stats groups results by model and market. Compare model results over a meaningful sample. Review sizing, regime mix, and loss distribution before drawing conclusions.

### Share PnL

Export a share card from a position using **Share PnL**. You can choose visible fields before downloading, copying, or sharing it.

Only share information you are comfortable making public. PnL cards are presentation assets, not trading records.


---

# 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.deryve.xyz/trading/performance-and-sharing.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.
