> ## 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.

# Check custom TraderCode availability (deprecated PitPass path)

> Check custom-handle availability (public, advisory).

 Unauthenticated as-you-type check for a custom handle: returns `available`
 plus, when unavailable, a snake_case `reason` code. Advisory only — the
 authoritative gate is the atomic claim in SetTraderCode — so a positive
 result never reserves the handle.



## OpenAPI

````yaml /proto-openapi/api/openapi.yaml get /api/v1/pitpass/codes/available
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://staging.apimonaco.xyz
    description: Staging server (Testnet)
security: []
tags:
  - name: AccountsService
  - name: ApplicationsService
  - name: AuthService
  - name: BuildercodeRewardsService
  - 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: SweeperService
  - name: TraderCodeService
  - name: TradesService
  - name: WhitelistService
  - name: WithdrawalsService
paths:
  /api/v1/pitpass/codes/available:
    get:
      tags:
        - TraderCodeService
        - PitPass
      summary: Check custom TraderCode availability (deprecated PitPass path)
      description: |-
        Check custom-handle availability (public, advisory).

         Unauthenticated as-you-type check for a custom handle: returns `available`
         plus, when unavailable, a snake_case `reason` code. Advisory only — the
         authoritative gate is the atomic claim in SetTraderCode — so a positive
         result never reserves the handle.
      operationId: pitpass_check_trader_code_availability
      parameters:
        - name: code
          in: query
          schema:
            type: string
      responses:
        '200':
          description: OK
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/CheckTraderCodeAvailabilityResponse'
        '429':
          description: Availability check rate-limit exceeded
        '500':
          description: Internal server error
      deprecated: true
components:
  schemas:
    CheckTraderCodeAvailabilityResponse:
      type: object
      properties:
        available:
          example: false
          type: boolean
          description: >-
            True when the handle passes validation and is neither live nor
            cooling down.
          nullable: true
        reason:
          example: taken
          type: string
          description: >-
            When unavailable, the snake_case reason: one of `taken`,
            `too_short`, `too_long`, `reserved`, `invalid_char`,
            `looks_like_address`. Empty when available.
          nullable: true

````

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