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

# Walk the funding ancestry for one or many wallets

> For each wallet, returns the chain of funders up to `depth` levels.
Each entry is `{wallet, fundedBy, fundedAt, signature, slot, lamports, solAmount, source}`;
the chain stops at a wallet with no observed funder or when `depth`
is exceeded.

Useful for tracing a sniper wallet back to its root funder, or
finding the common ancestor between two trader networks.




## OpenAPI

````yaml openapi-spec/history.yaml get /api/sol/funding/chain
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/funding/chain:
    get:
      summary: Walk the funding ancestry for one or many wallets
      description: >
        For each wallet, returns the chain of funders up to `depth` levels.

        Each entry is `{wallet, fundedBy, fundedAt, signature, slot, lamports,
        solAmount, source}`;

        the chain stops at a wallet with no observed funder or when `depth`

        is exceeded.


        Useful for tracing a sniper wallet back to its root funder, or

        finding the common ancestor between two trader networks.
      operationId: fundingChain
      parameters:
        - name: wallets
          in: query
          required: true
          schema:
            type: string
          description: One or more wallet addresses (comma-separated, max 150).
        - name: depth
          in: query
          schema:
            type: integer
            minimum: 1
            maximum: 10
            default: 5
      responses:
        '200':
          description: Success
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/FundingChainResponse'
        '400':
          description: Bad request
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
components:
  schemas:
    FundingChainResponse:
      type: object
      properties:
        success:
          type: boolean
        chains:
          type: object
          description: >-
            Map keyed by input wallet address; value is the ordered chain
            (closest funder first).
          additionalProperties:
            type: array
            items:
              $ref: '#/components/schemas/FundingChainEntry'
        enrichmentEnqueued:
          type: array
          items:
            type: string
          description: >-
            Wallets queued for asynchronous RPC backfill because no observed
            funder was found.
    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
    FundingChainEntry:
      type: object
      properties:
        wallet:
          type: string
        fundedBy:
          type: string
          nullable: true
        fundedAt:
          type: string
          format: date-time
        signature:
          type: string
        slot:
          type: integer
          format: int64
        lamports:
          type: string
        solAmount:
          type: number
        source:
          type: string
          enum:
            - observed
            - rpc_backfilled
            - rpc_unresolved
            - ch_backfilled
            - car_backfilled
  securitySchemes:
    ApiKeyAuth:
      type: apiKey
      in: query
      name: apiKey

````