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

# Case evidence package

> Returns the case evidence package: a sealed, signed, verifiable and self-contained document.

It is built on the saved snapshot, without rerunning the trace, so that it reflects what the analyst saw and
concluded. Querying the networks today would produce a different graph (new blocks, other prices, updated
labels). For the same reason, labels and sanctions history are those of the snapshot and are not re-verified
against the current lists. It includes what was expanded, revealed or reread after the trace.

Main sections:
- `manifest`: the document identity, `issued_by_user` (the person who issues it) and `integrity`, with the sha256
 digest and the signature;
- `findings` and `limitations`: the results, the coverage and its limits;
- `chain_of_custody`: the most recent queries of the case, up to 1,000. The query that generates the document is
 not included;
- `case_recordings`: the recording of each case query that read data sources, with its parameters, its order and
 the source responses, so it can be replayed;
- `annotations`: the case annotations and their log;
- `view`: the nodes removed from the view and the log of each removal and restoration. Removed nodes remain in
 the package, marked with `removed_from_view`; risk, exposure and coverage are computed on the full trace;
- `change_log`: the case change log.

A snapshot that did not record read failures cannot claim complete coverage: the package has
`findings.coverage.complete: null` and the notice at the top of `limitations`. To claim coverage, run the trace
again.

Errors: `404` if the caller cannot view the case, `409` if the case does not have a saved trace yet and `422` if
the snapshot is not a valid graph.

**Cost:** free.



## OpenAPI

````yaml /openapi.en.json get /v1/cases/{token}/evidence
openapi: 3.1.0
info:
  title: blockgence API
  description: >-
    The **blockgence** API provides fund tracing, entity attribution and
    explainable risk screening across several

    networks, with the evidence behind every result.


    ### Authentication

    Every `/v1/*` route requires an **API key**, sent in the `X-API-Key: <key>`
    header or as

    `Authorization: Bearer <key>`. Your organization issues the key. The
    evidence verification routes

    (`/v1/evidence/*`) do not require a key.


    ### Credits and limits

    Each plan has a **per-minute request limit** and a **monthly credit
    allowance**. Each operation states its cost in

    credits. **Only successful responses (status below 400) are charged:** an
    error response is recorded with 0

    credits. Check your usage with `GET /v1/account`.


    ### Data that could not be read

    If the data source cannot read what you requested, the response is `503
    source_unavailable`, with no charge,

    stating the source, the network, the query, the reason and whether a retry
    is advisable. If an intermediate step

    fails, the response is 200 and declares it in `degraded_sources` and in the
    `coverage_gaps` of the node or edge:

    in those cases, missing data does not mean missing activity.


    ### Networks

    `ethereum`, `bsc`, `polygon`, `arbitrum`, `base` and `optimism`; plus `tron`
    for tracing, profile, funding, network

    probing and transactions. `GET /v1/chains` states what can be queried on
    each network, at no cost. The networks

    `monero`, `bitcoin`, `litecoin` and `solana` are recognized in `/screening`
    and `/address`, where the network is

    inferred from the address format. Any other network returns `400`: it is
    never replaced with Ethereum.
  contact:
    name: blockgence
    url: https://www.blockgence.com/
  version: 1.0.0
servers:
  - url: https://app.blockgence.com
    description: Production
security: []
tags:
  - name: Platform
    description: >-
      Available networks, what can be queried on each one, from which sources
      and under which methodology. No cost.
  - name: Tracing
    description: >-
      Fund-flow tracing and reads of an address or a transaction: a
      time-consistent graph in both directions, funding, counterparties,
      bridges, swaps, mixers, labels and on-chain data.
  - name: Screening
    description: >-
      Risk screening of an address, with a recommendation (allow, review or
      block), its reasons and its sources.
  - name: Contracts
    description: Contract inspection and simulation of a transaction before signing it.
  - name: Tokens
    description: Token profile, with its issuer, supply, holders and risk signals.
  - name: Compromise
    description: >-
      Compromise vector of a stolen wallet, that is, how control of the funds
      was lost.
  - name: Incidents
    description: >-
      Incident response for victims, hacks and scams: playbook, freeze requests
      to issuers, post-mortem and deliverables.
  - name: Copilot
    description: >-
      AI investigation copilot that answers in natural language and cites the
      evidence (SSE streaming).
  - name: Cases
    description: >-
      Investigation cases to save, share and export, with their evidence,
      activity and annotations.
  - name: Permissions
    description: >-
      Approvals, delegations and signatures that grant access to an address's
      funds (ERC-20, Permit2 and EIP-7702).
  - name: Guard
    description: Wallet and protocol monitoring, with alerts by webhook and email.
  - name: Travel Rule
    description: >-
      Travel Rule without third-party connections: ownership challenge,
      counterparty, reconciliation and validation of IVMS101 messages.
  - name: Audit
    description: >-
      Smart contract audits, with the status, findings and evidence of each
      audit.
  - name: Evidence
    description: >-
      Verification of sealed evidence, with the signing public key and
      timestamps. No API key or charge required.
  - name: Monero
    description: >-
      Public profile of a Monero transaction and verification of a payment
      proof. Monero does not publish senders or amounts, so it is not traced.
  - name: Account
    description: Usage and limits of your API key.
  - name: Icons
    description: Entity logos to render graphs in your own interface. No cost.
  - name: Service
    description: Service status.
paths:
  /v1/cases/{token}/evidence:
    get:
      tags:
        - Cases
      summary: Case evidence package
      description: >-
        Returns the case evidence package: a sealed, signed, verifiable and
        self-contained document.


        It is built on the saved snapshot, without rerunning the trace, so that
        it reflects what the analyst saw and

        concluded. Querying the networks today would produce a different graph
        (new blocks, other prices, updated

        labels). For the same reason, labels and sanctions history are those of
        the snapshot and are not re-verified

        against the current lists. It includes what was expanded, revealed or
        reread after the trace.


        Main sections:

        - `manifest`: the document identity, `issued_by_user` (the person who
        issues it) and `integrity`, with the sha256
         digest and the signature;
        - `findings` and `limitations`: the results, the coverage and its
        limits;

        - `chain_of_custody`: the most recent queries of the case, up to 1,000.
        The query that generates the document is
         not included;
        - `case_recordings`: the recording of each case query that read data
        sources, with its parameters, its order and
         the source responses, so it can be replayed;
        - `annotations`: the case annotations and their log;

        - `view`: the nodes removed from the view and the log of each removal
        and restoration. Removed nodes remain in
         the package, marked with `removed_from_view`; risk, exposure and coverage are computed on the full trace;
        - `change_log`: the case change log.


        A snapshot that did not record read failures cannot claim complete
        coverage: the package has

        `findings.coverage.complete: null` and the notice at the top of
        `limitations`. To claim coverage, run the trace

        again.


        Errors: `404` if the caller cannot view the case, `409` if the case does
        not have a saved trace yet and `422` if

        the snapshot is not a valid graph.


        **Cost:** free.
      operationId: case_evidence_v1_cases__token__evidence_get
      parameters:
        - name: token
          in: path
          required: true
          schema:
            type: string
            title: Token
          description: >-
            Case token (`case_…`). If the caller cannot view the case, the
            response is `404`, the same as for a case that does not exist.
        - name: X-Case-Id
          in: header
          required: false
          schema:
            anyOf:
              - type: string
              - type: 'null'
            title: X-Case-Id
          description: >-
            Active case, optional: the token of a case you can view. The query
            is recorded in that case and also uses its own labels. A case that
            does not exist, was deleted or is no longer shared with you returns
            `400 case_unavailable` and the query is not run, with no charge.
      responses:
        '200':
          description: Successful response.
          content:
            application/json:
              schema: {}
        '401':
          description: The API key is missing, invalid or revoked.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
        '402':
          description: The monthly credits are exhausted.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
        '422':
          description: >-
            The request does not have the expected shape; `detail` states which
            field to correct.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/HTTPValidationError'
        '429':
          description: >-
            The per-minute request limit was exceeded. Retry after the number of
            seconds in `Retry-After`.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
      security:
        - APIKeyHeader: []
        - BearerAuth: []
components:
  schemas:
    Error:
      type: object
      title: Error
      description: >-
        Common shape of errors: a readable `detail` and, in many cases, an
        `error` with a stable code to recognize it without parsing the text.
      properties:
        detail:
          type: string
          description: What happened, in one sentence.
        error:
          type: string
          description: Stable error code, when there is one.
      required:
        - detail
    HTTPValidationError:
      properties:
        detail:
          items:
            $ref: '#/components/schemas/ValidationError'
          type: array
          title: Detail
      type: object
      title: HTTPValidationError
    ValidationError:
      properties:
        loc:
          items:
            anyOf:
              - type: string
              - type: integer
          type: array
          title: Location
        msg:
          type: string
          title: Message
        type:
          type: string
          title: Error Type
        input:
          title: Input
        ctx:
          type: object
          title: Context
      type: object
      required:
        - loc
        - msg
        - type
      title: ValidationError
  securitySchemes:
    APIKeyHeader:
      type: apiKey
      in: header
      name: X-API-Key
      description: Your API key in the `X-API-Key` header.
    BearerAuth:
      type: http
      scheme: bearer
      description: >-
        The same API key as `Authorization: Bearer <key>`, as an alternative to
        `X-API-Key`.

````

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