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

# Get Fee Policy

> View your current fee configuration for Polymarket

Scoped to your API key - no `accountId` required. If you've never configured a partner fee, returns the default policy (`partnerFeeBps: 0`). Fee policies are currently Polymarket-only; Predict and Opinion charge an exchange fee applied by their matching engines and have no configurable partner fee.


## OpenAPI

````yaml GET /api/fees/policy
openapi: 3.1.0
info:
  title: Predexon Trading API
  description: Unified trading API for prediction markets
  version: 1.0.0
servers:
  - url: https://trade.predexon.com
security:
  - ApiKeyAuth: []
paths:
  /api/fees/policy:
    get:
      tags:
        - Fees
      summary: Get Fee Policy
      description: >-
        View your current fee configuration for a venue. If no policy has been
        set, returns the default (`partnerFeeBps: 0`).
      operationId: get_fee_policy
      parameters:
        - name: venue
          in: query
          required: true
          schema:
            type: string
            enum:
              - polymarket
          description: Venue to query. Fee policies are currently Polymarket-only.
      responses:
        '200':
          description: Fee policy
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/FeePolicy'
              examples:
                default_no_partner_fee:
                  summary: Default policy (no partner fee)
                  value:
                    venue: polymarket
                    enabled: true
                    platformFeeBps: 0
                    partnerFeeBps: 0
                    partnerTreasuryAddress: null
                    totalFeeBps: 0
                with_partner_fee:
                  summary: With partner fee configured
                  value:
                    venue: polymarket
                    enabled: true
                    platformFeeBps: 0
                    partnerFeeBps: 50
                    partnerTreasuryAddress: '0xAbCdEf0123456789AbCdEf0123456789AbCdEf01'
                    totalFeeBps: 50
        '400':
          description: Missing or invalid venue
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ApiError'
        '401':
          description: API key required
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ApiError'
components:
  schemas:
    FeePolicy:
      type: object
      properties:
        enabled:
          type: boolean
          description: Whether fees are active
        platformFeeBps:
          type: number
          description: Platform fee in basis points
        partnerFeeBps:
          type: number
          description: Partner markup fee in basis points (0 if not configured)
        partnerTreasuryAddress:
          type: string
          nullable: true
          description: EVM address receiving partner fee revenue
        totalFeeBps:
          type: number
          description: 'Combined fee: platformFeeBps + partnerFeeBps'
    ApiError:
      type: object
      description: >-
        Unified error envelope returned by every endpoint on any 4xx or 5xx
        response. The `error` field is a stable snake_case code partners can
        branch on; `message` is the human-readable explanation (free-form, may
        change); `requestId` is the request correlation id (also returned in the
        `x-request-id` response header) — quote it when contacting support.
      required:
        - error
        - message
        - requestId
      properties:
        error:
          type: string
          description: >-
            Stable machine-readable code. See [Error
            codes](/trading-api/error-codes) for the full list. Snake_case,
            never renamed once shipped.
          example: insufficient_balance
        message:
          type: string
          description: >-
            Human-readable explanation. Free-form text that may include
            specifics (amounts, IDs, hints); do not parse — branch on `error`
            instead.
          example: 'Insufficient balance: need 50.000000, have 12.500000'
        requestId:
          type: string
          format: uuid
          description: >-
            Request correlation id. Quote this when filing a support ticket.
            Also returned in the `x-request-id` response header on every
            response (success or failure).
          example: a1b2c3d4-e5f6-7890-abcd-ef1234567890
  securitySchemes:
    ApiKeyAuth:
      type: apiKey
      in: header
      name: x-api-key

````