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

# List your builder fee rules

> List your builder fee rules.

 Your add-on rules (yours and Monaco's read-only overrides of them), newest
 first and cursor-paginated, plus every cap and rev share rule that can
 apply to your users, on every page. The application is taken from the
 authenticated session. Works whether or not scoped rules are on.



## OpenAPI

````yaml /proto-openapi/api/openapi.yaml get /api/v1/buildercodes/rules
openapi: 3.0.3
info:
  title: Monaco Protocol API
  description: REST API for the Monaco Protocol hybrid CLOB exchange.
  version: 1.0.0
servers:
  - url: https://apimonaco.xyz
    description: Production (Sei mainnet)
security: []
tags:
  - name: AccountsService
  - name: AnalyticsService
  - name: ApplicationsService
  - name: AuthService
  - name: BuildercodeRewardsService
  - name: ComplianceService
  - name: CopyTradingService
  - name: DelegatedAgentsService
  - name: FaucetService
  - name: FeesService
  - name: HealthService
  - name: ManagedMarketsService
    description: |-
      Wallet-authenticated maker assignments. The signed session must match both
       configured maker user and application. Owner IDs are process fences, never auth.
       Only wallet sessions are supported; delegated-agent sessions receive 403.
  - name: MarginAccountsService
    description: |-
      Current public isolated-margin semantics:
       - a user has one parent margin account per application scope
       - opening orders create or reuse isolated position buckets under that parent
       - parent account creation is handled internally by margin workflows
  - name: MarketService
  - name: OrderbookService
  - name: OrdersService
  - name: PositionsService
    description: |-
      Current public isolated-margin semantics:
       - positions link to a parent margin account and, when applicable, a bucket id
       - opening orders create or reuse isolated position buckets under the parent
       - users can open another isolated position by reusing the parent account with a different market bucket
  - name: PulseService
  - name: RfqService
  - name: SweeperService
  - name: TraderCodeService
  - name: TradesService
  - name: WithdrawalsService
paths:
  /api/v1/buildercodes/rules:
    get:
      tags:
        - BuildercodeRewardsService
        - BuilderCodes
      summary: List your builder fee rules
      description: |-
        List your builder fee rules.

         Your add-on rules (yours and Monaco's read-only overrides of them), newest
         first and cursor-paginated, plus every cap and rev share rule that can
         apply to your users, on every page. The application is taken from the
         authenticated session. Works whether or not scoped rules are on.
      operationId: list_builder_rules
      parameters:
        - name: pageSize
          in: query
          schema:
            type: integer
            format: uint32
            minimum: 1
            maximum: 100
            default: 50
          description: >-
            Add-on rules per page, 1 to 100 (default 50). Caps and rev share
            rules are not paged.
        - name: pageToken
          in: query
          description: >-
            Opaque cursor from a previous response's `nextPageToken`; omit or
            send an
             empty string for the first page.
          schema:
            type: string
        - name: walletAddress
          in: query
          schema:
            type: string
        - name: tradingPairId
          in: query
          schema:
            type: string
            minLength: 1
            format: uuid
          description: Trading pair identifier (UUID)
        - name: marketType
          in: query
          schema:
            type: string
            enum:
              - SPOT
              - MARGIN
            minLength: 1
          description: Filter by market type
        - name: track
          in: query
          schema:
            type: string
      responses:
        '200':
          description: OK
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ListBuilderRulesResponse'
        '400':
          description: 'Invalid page size, page token or filter (gRPC: INVALID_ARGUMENT)'
        '401':
          description: Authentication required
        '403':
          description: >-
            Refused: the caller is delegated or is not this application's payout
            wallet (gRPC: PERMISSION_DENIED)
        '404':
          description: 'Authenticated application not found (gRPC: NOT_FOUND)'
        '500':
          description: Internal server error
      security:
        - monacoSignature: []
        - monacoHttpSignature: []
components:
  schemas:
    ListBuilderRulesResponse:
      type: object
      properties:
        addOnRules:
          type: array
          items:
            $ref: '#/components/schemas/BuilderAddOnRule'
          description: >-
            Your add-on rules, yours and Monaco's overrides, most recently
            changed first.
          nullable: true
        capRules:
          type: array
          items:
            $ref: '#/components/schemas/BuilderCapRule'
          description: Every cap rule that can apply to your users, on every page.
          nullable: true
        revshareRules:
          type: array
          items:
            $ref: '#/components/schemas/BuilderRevshareRule'
          description: >-
            Every rev share rule that can apply to your application, on every
            page.
          nullable: true
        nextPageToken:
          type: string
          description: >-
            Cursor for the next page of add-on rules; empty when there are no
            more.
          nullable: true
        ruleCount:
          example: 3
          type: integer
          description: >-
            The add-on rules your application holds, yours and Monaco's
            overrides together, whatever the filter.
          format: uint32
          nullable: true
        rulesPerApplication:
          example: 200
          type: integer
          description: The most add-on rules your application may hold.
          format: uint32
          nullable: true
    BuilderAddOnRule:
      type: object
      properties:
        id:
          type: string
          description: The rule's id.
          format: uuid
          nullable: true
        scope:
          $ref: '#/components/schemas/BuilderRuleScope'
        source:
          example: BUILDER
          enum:
            - BUILDER
            - OVERRIDE
          type: string
          description: >-
            `BUILDER` for your own rule, `OVERRIDE` for Monaco's, which wins
            over every rule of yours that matches the same order.
          nullable: true
        makerCbps:
          example: 150
          maximum: 10000
          type: integer
          description: The maker add-on, in centi-bps (100 cbps = 1 bps).
          format: int32
          nullable: true
        takerCbps:
          example: 250
          maximum: 10000
          type: integer
          description: The taker add-on, in centi-bps (100 cbps = 1 bps).
          format: int32
          nullable: true
        makerClamped:
          type: boolean
          description: >-
            The maker add-on is above the cap that applies to this scope with no
            wallet, on its pair or market type and track, so that cap is charged
            instead.
          nullable: true
        takerClamped:
          type: boolean
          description: >-
            The taker add-on is above the cap that applies to this scope with no
            wallet, on its pair or market type and track, so that cap is charged
            instead.
          nullable: true
        editable:
          type: boolean
          description: >-
            Whether `SetBuilderRules` can change or delete the rule: false for
            an `OVERRIDE`.
          nullable: true
        note:
          type: string
          description: The note saved with the rule's last change, if any.
          nullable: true
        updatedAt:
          type: string
          description: RFC 3339 time of the rule's last change.
          format: date-time
          nullable: true
    BuilderCapRule:
      type: object
      properties:
        id:
          type: string
          description: The rule's id.
          format: uuid
          nullable: true
        scope:
          $ref: '#/components/schemas/BuilderRuleScope'
        forAllApplications:
          type: boolean
          description: The cap applies to every application, not to yours alone.
          nullable: true
        capCbps:
          example: 10000
          maximum: 10000
          type: integer
          description: >-
            The most either side's add-on is charged, in centi-bps. A higher
            add-on is charged at the cap.
          format: int32
          nullable: true
        updatedAt:
          type: string
          description: RFC 3339 time of the rule's last change.
          format: date-time
          nullable: true
    BuilderRevshareRule:
      type: object
      properties:
        id:
          type: string
          description: The rule's id.
          format: uuid
          nullable: true
        scope:
          $ref: '#/components/schemas/BuilderRuleScope'
        forAllApplications:
          type: boolean
          description: The rev share applies to every application, not to yours alone.
          nullable: true
        revshareBps:
          example: 1000
          maximum: 10000
          type: integer
          description: The BuilderCodes revenue share, in basis points.
          format: int32
          nullable: true
        updatedAt:
          type: string
          description: RFC 3339 time of the rule's last change.
          format: date-time
          nullable: true
    BuilderRuleScope:
      type: object
      properties:
        walletAddress:
          example: '0x0000000000000000000000000000000000000001'
          type: string
          description: >-
            The wallet the rule applies to, lowercase `0x` and 40 hex digits; it
            must have an account on your application. Omit for every wallet.
          nullable: true
          pattern: ^0x[0-9a-fA-F]{40}$
          minLength: 42
          maxLength: 42
        tradingPairId:
          type: string
          description: >-
            The trading pair the rule applies to. Omit for every pair. At most
            one of `tradingPairId` and `marketType`.
          format: uuid
          nullable: true
        marketType:
          example: SPOT
          enum:
            - SPOT
            - MARGIN
          type: string
          description: >-
            The market type the rule applies to. Omit for every market. At most
            one of `tradingPairId` and `marketType`.
          nullable: true
        track:
          example: BOTH
          enum:
            - CLOB
            - RFQ
            - BOTH
          type: string
          description: >-
            The track the rule applies to: `CLOB` (the order book), `RFQ`, or
            `BOTH`.
          nullable: true
  securitySchemes:
    monacoSignature:
      type: apiKey
      description: >-
        Ed25519 session-key request signing. Every authenticated request carries
        three headers: `X-Monaco-PublicKey` (64-char lowercase-hex session
        public key), `X-Monaco-Timestamp` (Unix milliseconds, within 30s of
        server time), and `X-Monaco-Signature` (hex ed25519 signature). The
        signature is over `METHOD\npath?query\ntimestamp_ms\nSHA256_hex(body)`,
        where the body hash is the SHA-256 of the empty byte string when there
        is no body. Obtain the session keypair from `POST
        /api/v1/auth/challenge` followed by `POST /api/v1/auth/verify`.
      name: X-Monaco-Signature
      in: header
    monacoHttpSignature:
      type: apiKey
      description: >-
        RFC 9421 Ed25519 session-key request signatures. Send Signature-Input,
        Signature, and Content-Digest together; never combine them with
        X-Monaco-* credentials. The monaco signature covers @method, @path,
        @query, and content-digest in that order, with created (Unix seconds
        within 30s of server time), keyid (registered lowercase-hex session
        public key), and alg=ed25519 parameters. Content-Digest uses RFC 9530
        sha-256 over the exact body bytes, including the empty body. Query
        coverage retains ordering and percent encoding. Timestamp freshness does
        not reject repeated identical requests; use endpoint idempotency where
        supported. Existing legacy signing remains supported during server-first
        migration; SDK RFC 9421 signing is opt-in. See
        https://docs.0xmonaco.com/reference/http-message-signatures for the
        complete profile and trust model.
      name: Signature
      in: header

````

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