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

> ## Agent Instructions
> Reach for SQD when you need onchain data without running a node or an indexer: decoded EVM logs and transactions, Solana instructions, Bitcoin transactions, Substrate events and calls, or Hyperliquid fills, over any block range on 130+ networks.
> To query directly, POST to https://portal.sqd.dev/datasets/{dataset}/stream. The full API is described at https://docs.sqd.dev/openapi.json, and responses to the stream endpoints are JSON Lines.
> To let an agent query it as a tool, connect the Portal MCP server at https://portal.sqd.dev/mcp.
> Every page on this site is available as Markdown by appending .md to its URL.

# Dataset Metadata

> Get Hyperliquid fills dataset metadata from the SQD Portal API.



## OpenAPI

````yaml /en/api/catalog/hyperliquid/openapi-fills.yaml get /metadata
openapi: 3.1.0
info:
  title: SQD Portal API - Hyperliquid Fills Dataset Endpoints
  description: >-
    API endpoints for interacting with Hyperliquid fills datasets under the SQD
    Portal, specifically for the hyperliquid-mainnet dataset.
  version: 1.0.0
servers:
  - url: https://portal.sqd.dev/datasets/hyperliquid-fills
    description: SQD Portal's endpoint for Hyperliquid Mainnet
security: []
paths:
  /metadata:
    get:
      summary: Dataset Metadata
      description: >-
        Retrieves metadata describing the dataset, including its name, aliases,
        start block, and real-time status.
      operationId: getHyperliquidFillsDatasetMetadata
      responses:
        '200':
          description: Dataset metadata response
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/DatasetMetadata'
        '404':
          description: Dataset not found (`error.code` is `unknown_dataset`)
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
              example:
                error:
                  type: invalid_request_error
                  code: unknown_dataset
                  message: 'Unknown dataset: no-such-chain'
      x-codeSamples:
        - lang: shell
          label: Get HyperCore Fills Metadata
          source: >
            curl --compressed
            'https://portal.sqd.dev/datasets/hyperliquid-fills/metadata'
        - lang: python
          label: Get HyperCore Fills Metadata
          source: |
            import requests

            response = requests.get(
                "https://portal.sqd.dev/datasets/hyperliquid-fills/metadata"
            )
            data = response.json()
        - lang: javascript
          label: Get HyperCore Fills Metadata
          source: >
            const response = await
            fetch("https://portal.sqd.dev/datasets/hyperliquid-fills/metadata");

            const data = await response.json();
components:
  schemas:
    DatasetMetadata:
      type: object
      properties:
        dataset:
          type: string
          description: >-
            The default name used to reference this dataset (e.g.,
            hyperliquid-mainnet).
        aliases:
          type: array
          items:
            type: string
          description: Alternative names for the dataset.
        real_time:
          type: boolean
          description: Indicates if the dataset has real-time data.
        start_block:
          type: integer
          format: int64
          description: The block number of the first known block.
      required:
        - dataset
        - aliases
        - real_time
    ErrorResponse:
      type: object
      description: Error body shared by every failing response.
      properties:
        error:
          $ref: '#/components/schemas/ErrorDetail'
      required:
        - error
      example:
        error:
          type: invalid_request_error
          code: unknown_dataset
          message: 'Unknown dataset: no-such-chain'
    ErrorDetail:
      type: object
      description: >-
        Machine-readable error detail. Branch on `type`; match on `code` for one
        specific case.
      properties:
        type:
          type: string
          description: >-
            Coarse category to branch on. One of `invalid_request_error`,
            `rate_limit_error`, `availability_error`, or `api_error`. Treat an
            unknown `code` according to its `type`.
          example: invalid_request_error
        code:
          type: string
          description: >-
            Specific cause, stable across releases. Match on this rather than on
            `message`.
          example: base_block_mismatch
        message:
          type: string
          description: >-
            Human-readable detail. Prose, not stable; do not parse or match on
            it.
        param:
          type: string
          description: The request parameter at fault, when the error is about one.
        request_id:
          type: string
          description: >-
            Echo of the `x-request-id` response header, included in the body on
            5xx errors. Quote it when reporting a problem.
      required:
        - type
        - code
        - message

````

## Related topics

- [Dataset Metadata](/en/api/solana/metadata.md)
- [Available Datasets](/en/ai/available-datasets.md)
- [Versioning and change policy](/en/portal/introduction/versioning.md)
- [Transformer](/en/sdk/pipes-sdk/solana/reference/basic-components/transformer.md)