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

# perpCategories | Hyperliquid info

> The info endpoint with type: "perpCategories" retrieves all HIP-3 perpetual assets that have a category set via setPerpAnnotation.

<Info>
  This method is available on Chainstack. Not all Hyperliquid methods are available on Chainstack, as the open-source node implementation does not support them yet — see [Hyperliquid methods](/docs/hyperliquid-methods) for the full availability breakdown.
</Info>

The `info` endpoint with `type: "perpCategories"` retrieves all HIP-3 perpetual assets that have a category set via `setPerpAnnotation`. Returns an array of `[coin, category]` tuples, or an empty array if no deployers have set categories.

## Parameters

### Request body

* `type` (string, required) — The request type. Must be `"perpCategories"`.

## Response

An array of two-element arrays, where each entry contains:

* Index 0 (string) — HIP-3 asset symbol in `deployer:TICKER` format.
* Index 1 (string) — Category label assigned by the deployer.

Returns an empty array if no deployers have set categories. Only HIP-3 deployed assets appear — native Hyperliquid perps (BTC, ETH, etc.) are never included.

The official Hyperliquid UI only displays categories from a predefined set in lowercase with no special characters (e.g., `"indices"`, `"commodities"`, `"ai"`, `"meme"`, `"defi"`, `"gaming"`, `"layer1"`, `"layer2"`, `"stocks"`, `"forex"`).

## Example request

<CodeGroup>
  ```shell Shell theme={"system"}
  curl -X POST \
    -H "Content-Type: application/json" \
    -d '{"type": "perpCategories"}' \
    https://hyperliquid-mainnet.core.chainstack.com/4f8d8f4040bdacd1577bff8058438274/info
  ```

  ```python Python (hyperliquid-python-sdk) theme={"system"}
  from hyperliquid.info import Info

  # The hyperliquid-python-sdk has no dedicated perpCategories method,
  # so post the request type directly with the generic post helper.
  info = Info("YOUR_CHAINSTACK_ENDPOINT", skip_ws=True)

  categories = info.post("/info", {"type": "perpCategories"})
  print(categories)
  ```

  ```typescript TypeScript (@nktkas/hyperliquid) theme={"system"}
  import * as hl from "@nktkas/hyperliquid";

  const transport = new hl.HttpTransport({ apiUrl: "YOUR_CHAINSTACK_ENDPOINT" });
  const client = new hl.InfoClient({ transport });

  const categories = await client.perpCategories();
  console.log(categories);
  ```
</CodeGroup>

<Note>
  **Use your own endpoint in your code.** The code examples use a placeholder Chainstack endpoint (YOUR\_CHAINSTACK\_ENDPOINT) — replace it with your own Hyperliquid node endpoint from the [Chainstack console](https://console.chainstack.com/). The curl above uses a shared public endpoint for quick checks only; do not use it in production.
</Note>

## Example response

When categories exist:

```json theme={"system"}
[
  ["xyz:GOLD", "commodities"],
  ["xyz:SPX", "indices"],
  ["abc:AGENT", "ai"]
]
```

When no deployers have set categories:

```json theme={"system"}
[]
```

## Use case

The `info` endpoint with `type: "perpCategories"` is useful for:

* Organizing HIP-3 perpetual assets into categories for trading interfaces
* Building category-based navigation and filtering for asset discovery
* Displaying a categorized catalog of deployer-created perpetual contracts


## OpenAPI

````yaml openapi/hyperliquid_node_api/hypercore_info/info_perp_categories.json post /4f8d8f4040bdacd1577bff8058438274/info
openapi: 3.0.0
info:
  title: Hyperliquid Node API
  version: 1.0.0
  description: This is an API for interacting with Chainstack Hyperliquid node.
servers:
  - url: https://hyperliquid-mainnet.core.chainstack.com
security: []
paths:
  /4f8d8f4040bdacd1577bff8058438274/info:
    post:
      tags:
        - hyperliquid operations
      summary: info (perpCategories)
      operationId: infoPerpCategories
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: object
              properties:
                type:
                  type: string
                  description: Request type
                  default: perpCategories
                  enum:
                    - perpCategories
              required:
                - type
      responses:
        '200':
          description: Array of perpetual category classifications
          content:
            application/json:
              schema:
                type: array
                items:
                  type: array
                  items:
                    type: string
                  description: Two-element array of [coin, category]

````