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

# Integrated Prediction Market Platforms

> A reference for the seven platforms Arbitrage aggregates, including the slugs used in API responses and how platform identity appears in returned data.

Arbitrage aggregates data from seven prediction market platforms, normalizing their prices, volumes, and market structures into a unified index. Every API response that references a specific platform uses a consistent `slug` — a lowercase, URL-safe identifier — so you can reliably filter, sort, and identify platforms in code without worrying about display name variations.

## Integrated platforms

| Platform    | Slug         | Type                                                            |
| ----------- | ------------ | --------------------------------------------------------------- |
| Polymarket  | `polymarket` | EVM-based binary prediction market (USDC)                       |
| Limitless   | `limitless`  | EVM-based prediction market (ERC-20)                            |
| Predict.fun | `predictfun` | EVM-based prediction market                                     |
| Manifold    | `manifold`   | Play-money prediction market with real-money prizes             |
| PredictIt   | `predictit`  | US-regulated real-money political prediction market             |
| Azuro       | `azuro`      | Decentralized sports and event betting protocol                 |
| Drift       | `drift`      | Solana-based decentralized exchange with prediction bet markets |

<Note>
  Platform slugs are stable identifiers. Use the slug (not the display name) in any filtering, storage, or programmatic comparison you build on top of the API.
</Note>

## PlatformInfo schema

Wherever the API returns a platform reference — for example, as `buy_platform` or `sell_platform` on an arbitrage opportunity — it uses the `PlatformInfo` object:

```json theme={null}
{
  "id": "a1b2c3d4-e5f6-...",
  "slug": "polymarket",
  "name": "Polymarket"
}
```

| Field  | Type   | Description                                        |
| ------ | ------ | -------------------------------------------------- |
| `id`   | UUID   | Stable platform identifier                         |
| `slug` | string | URL-safe platform slug used in filters and lookups |
| `name` | string | Human-readable display name                        |

## Where platform slugs appear

You will encounter platform slugs throughout the API:

* **`DiscoverItem.platform_slugs`** — array of slugs for all platforms listing a canonical question
* **`DiscoverItem.best_buy_platform`** — slug of the platform with the cheapest Yes price
* **`ArbitrageOpportunity.buy_platform`** and **`sell_platform`** — full `PlatformInfo` objects identifying each leg of an opportunity
* **`QuestionMarket.platform_slug`** — the platform a specific linked market lives on
* **`TrackedPosition.platform`** — the platform a wallet position was opened on

## Platform statistics endpoints

You can retrieve aggregated statistics and volume chart data for any platform by its slug:

```text theme={null}
GET /api/v1/platforms/{slug}/stats
GET /api/v1/platforms/{slug}/charts
```

The stats endpoint returns market counts, total volume, and active market metrics for the requested platform. The charts endpoint returns daily volume data points suitable for rendering a historical volume chart.

<Tip>
  The `charts` endpoint accepts a `days` query parameter (default: 30) to control how far back the volume history extends.
</Tip>