POST

/v1/entities

Resolve cluster ids to labels, categories, size and sanction status.

Takes cluster ids and returns what is known about each: the category and its confidence, the cluster type, and how many addresses the cluster holds. Anything unresolved comes back in not_found with a reason rather than being silently dropped, so a batch answer can be reconciled against what was asked.

Request

curl -X POST https://intelapi.publicaml.org/v1/entities \
  -H 'Content-Type: application/json' \
  -d '{
  "entity_ids": ["unnamed:eth:0x…"]
}'

Response

{
  "entities": [
    {
      "entity_id": "unnamed:eth:0xd8da6bf26964af9d7eed9e03e53415d37aa96045",
      "cluster_id": "unnamed:eth:0xd8da6bf26964af9d7eed9e03e53415d37aa96045",
      "chain": "ETH",
      "cluster_type": "unnamed",
      "category": "cex",
      "category_confidence": 1.0,
      "confidence": 1.0,
      "member_count": 6362,
      "cluster_size": 6362
    }
  ],
  "not_found": []
}

Response fields

Field	Type	Meaning
entities[].member_count	number	Addresses in the cluster.
entities[].cluster_type	string	How the cluster was formed, for example unnamed or deposit.
not_found[]	array	Ids that did not resolve, each with a reason.

Things that catch people out

entity_ids[] takes cluster ids such as "unnamed:eth:0x.." or "deposit:1:0x..", not wallet addresses. Passing an address returns not_found with reason entity_not_found and HTTP 200.
Get the id from cluster_id in a /v1/enrich response for the address you hold.
cluster_size counts addresses in the cluster. It is not a headcount of people or a measure of an entity’s size.

Try it

The interactive console runs this endpoint against live data from the browser, with no key and no signup.

Open the sandbox at intelapi.publicaml.org