---
title: "Dataset coverage, or one address's graph statistics"
method: GET
path: "/stats"
tags: ["Reference"]
---

# Dataset coverage, or one address's graph statistics

`GET /stats`

## Request

- Base URL: `https://intelapi.publicaml.org`
- URL: `https://intelapi.publicaml.org/stats`
- Auth: one of:
  - API key in header `X-API-Key`
  - none

With no parameters: how much data backs the API — clusters, labelled entities, sanction seeds per chain and per jurisdiction. Some figures are estimates and say so in `estimated`.

With `?address=` and `?chain=`: cluster membership and counterparty counts for that one address, which is cheaper than a full enrich when the shape of the graph is all you need.

## Query parameters

- `address` string
- `chain` 'bitcoin' | 'ethereum' | 'bsc' | 'tron': Which blockchain the address belongs to. Send one of the four values in the enum. The short forms used by the older clients (ETH, BTC, TRX, BNB) and any capitalisation are still accepted, but responses always echo the canonical spelling. Getting this wrong is the single commonest integration bug: the same 0x-prefixed address exists on ethereum, bsc and tron and means a different wallet on each, so the chain is part of the identity, never a hint. If it does not match the address format the call fails with `invalid_address_format`, which names the chain the address does look like.

## Response `200`

Coverage, or per-address statistics.

- object

## Other responses

- `400`: Malformed request.
- `429`: Rate limited: anonymous callers, and keys issued with a quota of their own. Authenticate to remove the limit.
- `500`: Server error.

---

[API](https://skmtc.dev/publicaml/apis/publicaml-intelligence-api.md) · [All operations](https://skmtc.dev/publicaml/apis/publicaml-intelligence-api/llms.txt) · [OpenAPI document](https://skmtc.dev/publicaml/apis/publicaml-intelligence-api/revisions/7c0c6315088c?raw)