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

# Data sources

Every figure in the platform traces to one of four source classes, each with recorded provenance on every row.

## 1. Venue private APIs (the book)

Positions, balances, leverage, margin mode, liquidation prices and funding rates come from the fund's own venue accounts via **read-only** API keys (OKX, Bybit, Bitget, Binance, Kraken, Hyperliquid). Keys are stored in a per-tenant encrypted vault, verified read-only at save time and at every poll, and can never be read back by anyone once stored. An expired or invalid key degrades that venue — visibly — without interrupting monitoring of the others.

## 2. Venue public market-data APIs (prices and spreads)

Live marks and daily closes come from the venues' public data feeds — the same data shown on their trading screens. Bid/ask quotes are captured continuously and aggregated nightly into spread statistics, which progressively replace judgment-based liquidity haircuts with measured liquidation cost.

## 3. Independent reference data

* **CoinGecko (Pro)** — two years of daily prices, aggregated cross-venue volumes (the denominator for days-to-liquidate) and market caps, plus the total-market index. Assets are mapped by an explicit audited table — symbol-collision guessing is banned by design. CoinGecko data is used for liquidity, sensitivities and verification; it does not silently feed the official price series.
* **Coin Metrics** — independent reference rates; every run cross-checks venue closes and records divergences in basis points in its manifest.

## 4. The fund itself

* **Official NAV** — from the fund administrator (manual entry today, administrator API when available). The platform is deliberately *not* a NAV engine; every %-of-NAV figure uses the official number.
* **Off-venue positions** — assets no API can see (SAFTs, unlisted tokens) are entered and attested in the app, join the struck book alongside the venue snapshot, and appear in the disclosed-exclusions register when they cannot be priced.


---

# 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.fortemis.io/data-sources.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.