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

# Builder fee split

> How one builder's fee is split with its sub-builders over a window of fill time, per fee token.



## OpenAPI

````yaml /data-api/openapi.json get /v1/builders/{builder}/sub-builders
openapi: 3.1.0
info:
  title: Hyperdash Data API
  version: v1
  description: >-
    Hyperliquid data from Hyperdash's own nodes and stored datasets; requests
    never call Hyperliquid's public API. Every response reports the credits it
    cost.
servers:
  - url: https://data.hyperdash.com
security: []
tags:
  - name: Accounts
  - name: Async jobs
  - name: Builders
  - name: Cohorts
  - name: HIP-3 dexes
  - name: Leaderboards
  - name: Lending
  - name: Liquidations
  - name: Markets
  - name: 'Markets: analytics'
  - name: 'Markets: funding'
  - name: 'Markets: liquidation and stop levels'
  - name: 'Markets: open interest and positioning'
  - name: 'Markets: order book'
  - name: 'Markets: prices and candles'
  - name: 'Markets: queue priority'
  - name: 'Markets: trades and flow'
  - name: 'Markets: TWAPs'
  - name: Network
  - name: Outcomes
  - name: Positions
  - name: Referrals
  - name: Snapshots
  - name: Spot
  - name: Staking
  - name: Traders
  - name: Vaults
paths:
  /v1/builders/{builder}/sub-builders:
    get:
      tags:
        - Builders
      summary: Builder fee split
      description: >-
        How one builder's fee is split with its sub-builders over a window of
        fill time, per fee token. Only the builder's fills that name
        sub-builders are counted.


        **How it works**

        - Hyperliquid sub-builders went live on 2026-10-28. An order's builder
        code can share its builder fee with up to 5 sub-builders.

        - Each fill carries its own split, which is its sub-builders and their
        shares. Earnings are computed per fill as builder fee times share.

        - Earnings are complete since the first sub-builder fills on 2026-10-31.


        **Rows**

        - `kind=split_total`: those fills and their builder fee, with each fill
        counted once.

        - `kind=kept`: what the builder keeps of it.

        - `kind=paid`: one row per sub-builder.


        **Limits**

        - One query returns at most your plan's wallet-list cap across its
        pages: Starter 100, Growth 500, Scale and Enterprise 1,000.

        - A query cut at the cap ends with `meta.truncated` set to `true`.


        **Notes**

        - Fills without sub-builders are not included, because the builder keeps
        their whole fee.


        **Credits:** 20 per request + 1 per row.


        **Scope:** `analytics:read`
      operationId: getBuilderSubBuilderSplit
      parameters:
        - name: builder
          in: path
          required: true
          description: 'Builder address: `0x` followed by 40 hex characters.'
          schema:
            type: string
        - name: start_time
          in: query
          required: false
          description: >-
            Start of the fill-time window, in epoch milliseconds. Defaults to 7
            days before the end. The window is at most 30 days.
          schema:
            type: integer
        - name: end_time
          in: query
          required: false
          description: End time in epoch milliseconds, exclusive. Defaults to now.
          schema:
            type: integer
        - name: limit
          in: query
          required: false
          description: Rows to return, at most 500.
          schema:
            type: integer
            minimum: 1
            maximum: 500
            default: 100
        - name: cursor
          in: query
          required: false
          description: Opaque cursor from `next_cursor`.
          schema:
            type: string
      responses:
        '200':
          description: OK
          headers:
            X-Credits-Charged:
              schema:
                type: integer
            X-Credit-Price-Version:
              schema:
                type: integer
            X-Request-Id:
              schema:
                type: string
          content:
            application/json:
              schema:
                type: object
                required:
                  - data
                  - has_more
                  - next_cursor
                  - meta
                properties:
                  data:
                    type: array
                    items:
                      type: object
                      properties:
                        kind:
                          type: string
                          description: '`split_total`, `kept` or `paid`.'
                        sub_builder:
                          type:
                            - string
                            - 'null'
                          description: Sub-builder, on `paid` rows.
                        fee_token:
                          type: string
                          description: Token the builder fee is paid in.
                        orders:
                          type: integer
                          description: Orders filled in the window.
                        fills:
                          type: integer
                          description: Fills.
                        notional:
                          type: string
                          description: >-
                            Filled notional, which is px times size, in each
                            market's quote. Decimal string.
                        fee:
                          type: string
                          description: >-
                            Builder fee (`split_total`), kept or paid, in
                            `fee_token`. Decimal string.
                        fee_unreported_fills:
                          type: integer
                          description: >-
                            Fills whose builder fee the node did not report.
                            These are not counted in `fee`.
                        first_fill:
                          type: integer
                          description: First fill, in epoch milliseconds.
                        last_fill:
                          type: integer
                          description: Last fill, in epoch milliseconds.
                    description: Result rows.
                  has_more:
                    type: boolean
                    description: '`true` when another page follows.'
                  next_cursor:
                    type:
                      - string
                      - 'null'
                    description: >-
                      Cursor for the next page, passed as `cursor`. `null` on
                      the last page.
                  meta:
                    type: object
                    description: >-
                      Response metadata. Its keys depend on the endpoint and are
                      described above.
        '400':
          description: 'Invalid parameter (also: a request body that is not valid JSON)'
          content:
            application/problem+json:
              schema:
                $ref: '#/components/schemas/Problem'
        '401':
          description: Invalid, expired or revoked key
          content:
            application/problem+json:
              schema:
                $ref: '#/components/schemas/Problem'
        '403':
          description: Scope, plan, history or credit limit
          content:
            application/problem+json:
              schema:
                $ref: '#/components/schemas/Problem'
        '409':
          description: Price version changed, or a cursor's snapshot expired
          content:
            application/problem+json:
              schema:
                $ref: '#/components/schemas/Problem'
        '429':
          description: >-
            Rate limited (Retry-After; free): request rate, concurrent requests
            (a request counts one slot per 1,000 rows it can return), or this
            server busy with your workspace's requests
          content:
            application/problem+json:
              schema:
                $ref: '#/components/schemas/Problem'
        '502':
          description: Upstream data source failed (free; retry later)
          content:
            application/problem+json:
              schema:
                $ref: '#/components/schemas/Problem'
        '503':
          description: Backend at capacity or temporarily unavailable (Retry-After)
          content:
            application/problem+json:
              schema:
                $ref: '#/components/schemas/Problem'
        '504':
          description: Upstream data source timed out (free; retry later)
          content:
            application/problem+json:
              schema:
                $ref: '#/components/schemas/Problem'
      security:
        - bearer: []
      x-codeSamples:
        - lang: curl
          source: >-
            curl -H "Authorization: Bearer $HYPERDASH_API_KEY"
            'https://data.hyperdash.com/v1/builders/0x…/sub-builders'
components:
  schemas:
    Problem:
      type: object
      required:
        - type
        - title
        - status
        - code
        - request_id
      properties:
        type:
          type: string
        title:
          type: string
        status:
          type: integer
        code:
          type: string
        detail:
          type: string
        hint:
          type: string
        request_id:
          type: string
  securitySchemes:
    bearer:
      type: http
      scheme: bearer
      description: Your API key, sent as `Bearer hdk_sk_live_v1_…`.

````

This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.