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

# Instrument Schema

> Trading instrument specification (Hyperliquid). Includes generated fields, route metadata, response shapes, and implementation-safe 0xArchive contract details.

Source OpenAPI: 0xArchive API 1.5.0; 140 paths; 119 component schemas.

Trading instrument specification (Hyperliquid)

## Required Fields

| Field         | Type    | Description                                   |
| ------------- | ------- | --------------------------------------------- |
| `is_active`   | boolean | Whether the instrument is currently tradeable |
| `name`        | string  | Instrument symbol                             |
| `sz_decimals` | integer | Size decimal precision                        |

## JSON Schema

```json theme={"theme":"github-dark"}
{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "title": "Instrument",
  "description": "Trading instrument specification (Hyperliquid)",
  "type": "object",
  "required": [
    "is_active",
    "name",
    "sz_decimals"
  ],
  "properties": {
    "instrument_type": {
      "description": "Type of instrument",
      "type": "string",
      "enum": [
        "perp",
        "spot"
      ],
      "nullable": true,
      "example": "perp"
    },
    "is_active": {
      "description": "Whether the instrument is currently tradeable",
      "type": "boolean",
      "example": true
    },
    "max_leverage": {
      "description": "Maximum leverage allowed",
      "type": "integer",
      "nullable": true,
      "example": 50
    },
    "name": {
      "description": "Instrument symbol",
      "type": "string",
      "example": "BTC"
    },
    "only_isolated": {
      "description": "If true, only isolated margin mode is allowed",
      "type": "boolean",
      "nullable": true
    },
    "sz_decimals": {
      "description": "Size decimal precision",
      "type": "integer",
      "example": 4
    }
  }
}
```

## Referenced By

Use this shared schema with the generated component index and route-specific endpoint pages during implementation.