# Coverage & data conventions.

> Source: https://implyra.com/docs/data-coverage
> Implyra API docs · Core concepts · Coverage & conventions

Know which dataset, units and historical window each feature represents.

## Coverage by feature

| Name | Type | Description |
| --- | --- | --- |
| `Trader rankings & wallet analytics` | Polymarket | Global leaderboard, profiles, positions, trades and reported wallet history. |
| `Cohorts & funding` | Polymarket | Grouped wallet positioning and observed funding sources; records depend on the available dataset. |
| `Market discovery` | Venue-specific | Polymarket, Kalshi and Hyperliquid use separate endpoint families and may expose different units and fields. |
| `Matched markets` | Polymarket ↔ Kalshi | Matched contracts and confidence scores. A match does not guarantee equivalent settlement terms. |
| `Streaming` | Separate service | Supported SSE channels and access are documented in the streaming guide. |

## Keep units visible

- The global leaderboard winRate is 0–1; profile winRatePct is already a percentage.
- P&L and portfolio values are USD unless the endpoint specifies otherwise. Kalshi volumes may represent contracts.
- A price change from 0.60 to 0.65 is five percentage points, not a five-percent relative return.
- Keep null distinct from zero. Do not fill a missing time-series observation with an invented data point.

## A response is not always the whole record

Show snapshot timestamps and the returned historical window. Paginate positions and trades before presenting totals as complete. Advanced metrics can describe an older or different period from the overall leaderboard P&L; its latest snapshot timestamp does not establish freshness for every field. Risk measures depend on the available P&L history and are not cash-flow-adjusted returns.

- [Risk metric definitions](https://implyra.com/docs/trader-analytics#metrics): Ratios, drawdowns, scores and sample size.
- [Errors & limits](https://implyra.com/docs/errors): Unavailable data, timeouts and retries.