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

# Deploy by mint address



## OpenAPI

````yaml openapi-spec/history.yaml get /api/sol/tokens/mint/{mint}
openapi: 3.0.3
info:
  title: Raze Database API
  description: >
    Paid subscription API for Solana transaction data and history.


    Also hosts write utilities (`/utils/sol/*`): token launch, transfer, burn,

    consolidate, fees claim/config, and agent initialize — previously on

    `router.raze.bot`. Mixer/distribute removed 2026-07-25.


    ## Batch Requests

    All endpoints with path parameters (mint, signer, address, tokenMint,
    ownerAddress) support batch queries

    via comma-separated values. For example:
    `/api/sol/trades/mint/mint1,mint2,mint3?limit=50`


    - Maximum 10 values per batch request

    - Each value must be a valid address (>= 32 characters)

    - Single values behave identically to non-batch requests

    - Batch response format: `{ "success": true, "results": { "value1": {...},
    "value2": {...} }, "count": N, "timestamp": "..." }`

    - Each key in `results` contains the full single-entity response

    - Queries run in parallel for maximum performance
  version: 1.0.0
servers:
  - url: https://api.raze.bot
    description: >-
      Raze global History API — GeoDNS routes to the nearest region
      automatically
security:
  - ApiKeyAuth: []
paths:
  /api/sol/tokens/mint/{mint}:
    get:
      summary: Deploy by mint address
      operationId: getDeployByMint
      parameters:
        - name: mint
          in: path
          required: true
          schema:
            type: string
          example: Fyx78ew4wRY26gPj5CkTyuZ4kvW7CkPff5Jm2vNspump
        - name: analysis
          in: query
          schema:
            type: string
            enum:
              - true
              - protrader
              - all
              - stats
              - holdings
          description: >
            Optional analysis parameter. Use `true` for sniper/bundle signers,
            `protrader` for pro-trader signers, `all` for all analysis types,
            `stats` for aggregated statistics, or `holdings` for token holdings
            by analyzed addresses.
      responses:
        '200':
          description: >
            Success. A not-found or invalid mint returns HTTP 200 with

            `{ "error": true, "message": "..." }` (not a 404/400).


            Two field sets are possible:

            - **Live-cache fast path** — the token is still live in RAM; a lean
            set of
              deploy + realtime fields.
            - **DB cold path** — adds `volume24h`, `trades24h`,
            `uniqueTraders24h`,
              `buyVolume24h`, `sellVolume24h`, `total_fees_spent`, `total_trades`,
              and `currentPrice`.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/DeployResponse'
        '500':
          description: Database error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
components:
  schemas:
    DeployResponse:
      type: object
      properties:
        success:
          type: boolean
        data:
          type: object
          description: >
            Deploy object (includes mint, signer, name, symbol, uri, platform,
            etc.).


            Two field sets are possible:

            - **Live-cache fast path** (token still live in RAM): a lean set of
            deploy + realtime fields.

            - **DB cold path**: adds 24h trading activity — `volume24h`,
            `trades24h`,
              `uniqueTraders24h`, `buyVolume24h`, `sellVolume24h`, `total_fees_spent`,
              `total_trades`, and `currentPrice`.

            A not-found or invalid mint returns `{ error: true, message }` with
            HTTP 200.
    ErrorResponse:
      type: object
      properties:
        error:
          type: string
        message:
          type: string
        code:
          type: string
        success:
          type: boolean
      example:
        error: Unauthorized
        message: Invalid API key
        code: INVALID_KEY
        success: false
  securitySchemes:
    ApiKeyAuth:
      type: apiKey
      in: query
      name: apiKey

````