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

# API Overview

Paragon markets are accessible via the standard Hyperliquid API. No separate API or authentication required.

> **Quick start:** Use `para:BTCD`, `para:TOTAL2`, `para:OTHERS`, or `para:AVGO` as the `coin` parameter in any Hyperliquid API call.

## Hyperliquid API

All Paragon markets use Hyperliquid's unified API infrastructure:

* **REST API**: Account info, order placement, position management
* **WebSocket**: Real-time orderbook, trades, and account updates

Full documentation: [Hyperliquid API Docs](https://hyperliquid.gitbook.io/hyperliquid-docs/for-developers/api)

## Market Identifiers

Paragon markets use the following identifiers in API calls:

| Market                     | Symbol        |
| -------------------------- | ------------- |
| Bitcoin Dominance          | `para:BTCD`   |
| Total Market Cap ex-BTC    | `para:TOTAL2` |
| Total Market Cap ex-Top 10 | `para:OTHERS` |
| Broadcom (equity)          | `para:AVGO`   |

> **Note:** The `para:` prefix specifies the Paragon DEX on Hyperliquid. This is required for all API calls.

## Common Operations

### Get Market Data

```python
# Example: Fetch orderbook for TOTAL2
import requests

response = requests.post(
    "https://api.hyperliquid.xyz/info",
    json={"type": "l2Book", "coin": "para:TOTAL2"}
)
orderbook = response.json()
```

### Place Order

```python
# Example: Market buy TOTAL2
# See Hyperliquid docs for full authentication and signing details

order = {
    "coin": "para:TOTAL2",
    "is_buy": True,
    "sz": 100,  # Size in USD
    "limit_px": None,  # Market order
    "order_type": {"market": {}}
}
```

### Get Position

```python
response = requests.post(
    "https://api.hyperliquid.xyz/info",
    json={"type": "clearinghouseState", "user": "0x..."}
)
positions = response.json()
```

## SDKs and Libraries

Community-maintained SDKs for Hyperliquid:

* **Python**: [hyperliquid-python-sdk](https://github.com/hyperliquid-dex/hyperliquid-python-sdk)
* **TypeScript**: [hyperliquid-ts-sdk](https://github.com/hyperliquid-dex/hyperliquid-ts-sdk)

These SDKs work with all Hyperliquid markets including Paragon indices.

## Rate Limits

Hyperliquid API rate limits apply to all markets:

* REST: 1200 requests per minute
* WebSocket: Connection limits per IP

See Hyperliquid documentation for current limits and best practices.

## Index Data

For programmatic access to index values and constituent data:

* Real-time index prices available via Hyperliquid WebSocket
* Historical data available through standard market data endpoints
* Constituent weightings published periodically (see [External Pricing](/markets/crypto-indices/external-pricing.md))
* Composition snapshots available via the [Index Composition API](/developers/index-composition-api.md)

## Historical Data

Historical data for the Paragon dex is available from [Hydromancer's Reservoir](https://docs.hydromancer.xyz/reservoir/paragon).

## Support

For API integration support:

* Hyperliquid Discord (general API questions)
* [Paragon Discord](https://discord.gg/qd6a9gTqqr) or [Telegram](https://t.me/paragon_trade) (Paragon-specific questions)


---

# 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:

```
GET https://docs.paragon.trade/developers/api.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.