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

# Latest chain health score



## OpenAPI

````yaml openapi-spec/history.yaml get /api/sol/sentiment/latest
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/sentiment/latest:
    get:
      summary: Latest chain health score
      operationId: getLatestSentiment
      parameters: []
      responses:
        '200':
          description: Success
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/LatestSentimentResponse'
        '404':
          description: No chain health data available
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
        '503':
          description: Database unavailable
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
components:
  schemas:
    LatestSentimentResponse:
      type: object
      properties:
        success:
          type: boolean
        score:
          type: number
        status:
          type: string
          enum:
            - excellent
            - good
            - fair
            - poor
        time:
          type: string
          format: date-time
        metrics:
          type: object
          description: >
            Raw metric counters. Keys - `avgHoldingSeconds`, `bundleCount`,

            `buyCount`, `deployCount`, `migrationCount`, `proTradeCount`,

            `sellCount`, `sniperCount`, `tradeCount`, `uniqueTraders`,
            `volumeSol`.
        componentScores:
          type: object
          description: >
            Per-component contribution to the composite score (camelCase field
            on

            this endpoint). Keys - `bundleRatio`, `buyCount`, `deployCount`,

            `holdingTime`, `migrationBonus`, `proTradeRatio`, `sniperRatio`,

            `tradeCount`, `volume`.
        timestamp:
          type: string
          format: date-time
    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

````