> ## Documentation Index
> Fetch the complete documentation index at: https://artemis.ai/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Perpetuals

> Volume, open interest, fees, funding rates and order-book depth for perpetual futures venues

Perpetuals metrics come from fill events on-chain or from each venue's API. Volume and fees are daily sums; open interest is an end-of-day snapshot.

## Metrics

| Metric               | Label                              | Unit     | Aggregation |
| -------------------- | ---------------------------------- | -------- | ----------- |
| `PERP_VOLUME`        | Perpetuals Volume                  | Currency | `SUM`       |
| `OPEN_INTEREST`      | Open Interest                      | Currency | `LAST`      |
| `PERP_FEES`          | Perp Fees                          | Currency | `SUM`       |
| `PERP_DAU`           | Perpetuals Daily Active Users      | Nominal  | `AVERAGE`   |
| `PERP_TXNS`          | Perpetuals Transactions            | Nominal  | `SUM`       |
| `PERP_LIQUIDATION`   | Perpetual Liquidations             | Currency | `SUM`       |
| `FUNDING_RATE`       | Funding Rate                       | Nominal  | `LAST`      |
| `OI_BY_VOLUME_RATIO` | OI / Volume Ratio                  | Nominal  | `AVERAGE`   |
| `TAKE_RATE`          | Take Rate                          | Nominal  | `LAST`      |
| `DEPTH_1BPS`         | Depth within 1bps of the mid price | Nominal  | `AVERAGE`   |
| `DEPTH_2BPS`         | Depth within 2bps of the mid price | Nominal  | `AVERAGE`   |
| `DEPTH_3BPS`         | Depth within 3bps of the mid price | Nominal  | `AVERAGE`   |

<Warning>
  `OPEN_INTEREST` is `LAST`: an end-of-day snapshot of outstanding positions. **Never sum it.** `PERP_VOLUME` is `SUM` and does accumulate. Mixing the two up is the most common error in perps analysis.
</Warning>

## Covered venues

`hype` · `aster` · `lit` · `apex` · `edgex` · `extended` · `ostium` · `paradex` · `gns` · `gmtrade` · `hyena` · `paragon` · `tradexyz` · `jup`

## Example: Volume, open interest and fees

```bash theme={null}
curl -s "https://data-svc.artemisxyz.com/v2/data/PERP_VOLUME,OPEN_INTEREST,PERP_FEES?symbols=hype,aster,lit,paradex,ostium&startDate=2026-07-25&endDate=2026-08-01&summarize=true&APIKey=$ARTEMIS_API_KEY"
```

| Venue       | Volume     | Open interest | Fees     |
| ----------- | ---------- | ------------- | -------- |
| Hyperliquid | \$2,016.5M | \$10,170.4M   | \$575.1K |
| Aster       | \$834.7M   | \$1,902.3M    | -        |
| Lighter     | \$509.2M   | \$869.7M      | \$37.9K  |
| Paradex     | \$3.4M     | \$36.9M       | \$326    |
| Ostium      | \$0.6M     | \$4.6M        | \$247    |

A dash means the venue doesn't expose that metric. How the absence arrives depends on the call: without `summarize`, the response carries the string `"Metric not available for asset."` in place of the data array; with `summarize=true` (as in the request above) it comes back as a well-formed tuple, `["Aster", null]`, with a `null` value instead. See [Core concepts](/docs/artemis-api/core-concepts).

## Hyperliquid goes deeper

Hyperliquid exposes 78 metrics, well beyond the standard set: order-book depth at 1/2/3bps, `TAKE_RATE`, `BUILDER_CODE_VOLUME`, chain-level metrics for the L1 itself (`CHAIN_TVL`, `CHAIN_FEES`, `CHAIN_DAU` and more), and `_EXCLUDING_HIP3` variants of the core perps metrics (`PERP_VOLUME_EXCLUDING_HIP3`, `OPEN_INTEREST_EXCLUDING_HIP3`, and others) that strip out HIP-3 builder-deployed markets:

```bash theme={null}
curl -s "https://data-svc.artemisxyz.com/supported-metrics/?symbol=hype&APIKey=$ARTEMIS_API_KEY"
```

## Split volume by market

`dimensionType=TOKEN` breaks `PERP_VOLUME` down per market on venues that support it:

```bash theme={null}
curl -s "https://data-svc.artemisxyz.com/v2/data/PERP_VOLUME?symbols=hype&startDate=2026-08-01&endDate=2026-08-01&dimensionType=TOKEN&APIKey=$ARTEMIS_API_KEY"
```

This returns one series per market: `BTC-hype`, `ETH-hype`, `AAVE-hype`, and so on.

On Hyperliquid, `PERP_VOLUME` splits by `TOKEN` and `TOKEN_TYPE`. Each metric's `cuts` array in [`GET /supported-metrics/`](/docs/artemis-api/discovery) lists the dimensions it supports.