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

# Public signing key

> Returns the public key blockgence uses to sign sealed documents, to verify who issued them. No API key
required. The response can be cached for up to 5 minutes.

Main fields:
- `configured`: the key this service signs with (`key_id`, `public_key`, `public_key_pem` and its status in the
 published registry), or `null`, with the reason in `configured_note`.
- `published`: the versioned blockgence key registry, with the active, retired and revoked keys and their
 validity period. It is advisable to also compare it with the one published on the blockgence website, which
 does not depend on this service.
- `matches_published`: whether the configured key is the active published key (`null` if there is no key).

It also includes the message that is signed (`signed_message`), what the signature proves and what it does
not, and the steps to verify it.



## OpenAPI

````yaml /openapi.en.json get /v1/evidence/signing-key
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/evidence/signing-key:
    get:
      tags:
        - Evidence
      summary: Public signing key
      description: >-
        Returns the public key blockgence uses to sign sealed documents, to
        verify who issued them. No API key

        required. The response can be cached for up to 5 minutes.


        Main fields:

        - `configured`: the key this service signs with (`key_id`, `public_key`,
        `public_key_pem` and its status in the
         published registry), or `null`, with the reason in `configured_note`.
        - `published`: the versioned blockgence key registry, with the active,
        retired and revoked keys and their
         validity period. It is advisable to also compare it with the one published on the blockgence website, which
         does not depend on this service.
        - `matches_published`: whether the configured key is the active
        published key (`null` if there is no key).


        It also includes the message that is signed (`signed_message`), what the
        signature proves and what it does

        not, and the steps to verify it.
      operationId: signing_key_v1_evidence_signing_key_get
      parameters: []
      responses:
        '200':
          description: The public signing key and the published key registry.
          content:
            application/json:
              schema: {}

````

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