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

# Claim Protocol Fees

> Claim accrued protocol fees from the market (anyone can call)

<Note>
  This is a smart contract write function. The curl example shown is for illustration. To call this function, use web3 libraries (ethers.js, viem, web3.py) or JSON-RPC directly.
</Note>


## OpenAPI

````yaml POST /market/{marketAddress}/claimProtocolFees
openapi: 3.0.3
info:
  title: Based Protocol Smart Contracts API
  description: >-
    OpenAPI specification for the Based Protocol - a bidirectional perpetual
    markets platform built for EVM blockchains. The protocol allows users to
    create binary markets where participants can take "Based" (positive) or
    "Cringe" (negative) positions using the Based Market mechanism.
  version: 1.0.0
  license:
    name: LicenseRef-Proprietary
servers:
  - url: https://mainnet.base.org
    description: Base Mainnet (default RPC endpoint)
security: []
tags:
  - name: BasedProtocol
    description: Operations related to the main protocol contract
  - name: BasedMarket
    description: Operations for individual markets
  - name: BasedMarketRouter
    description: Router operations with safety checks and deadline protection
paths:
  /market/{marketAddress}/claimProtocolFees:
    post:
      tags:
        - BasedMarket
      summary: Claim protocol fees
      description: Claim accrued protocol fees from the market (anyone can call)
      operationId: claimProtocolFees
      parameters:
        - name: marketAddress
          in: path
          required: true
          schema:
            type: string
            pattern: ^0x[a-fA-F0-9]{40}$
          description: Address of the market contract
      responses:
        '200':
          description: Protocol fees claimed successfully
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/TransactionResponse'
components:
  schemas:
    TransactionResponse:
      type: object
      properties:
        transactionHash:
          type: string
          pattern: ^0x[a-fA-F0-9]{64}$
          description: Transaction hash
        blockNumber:
          type: integer
          format: uint256
          description: Block number where transaction was mined
        gasUsed:
          type: integer
          format: uint256
          description: Amount of gas used
        success:
          type: boolean
          description: Whether transaction was successful

````