Dataset coverage, or one address's graph statistics
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.
Request
- Base URL: https://intelapi.publicaml.org
- URL: https://intelapi.publicaml.org/stats
- Auth: one of:
- API key in header X-API-Key
- none
Query parameters
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
Coverage, or per-address statistics.
Changes
No recorded changes to this operation across all 1 revision of this API.