employeeAt) and which domains they appear to be
customers/users of (clientAt), plus an industry-category map for those
domains. Useful for scoping the blast radius of a stealer-family outbreak —
e.g. “which of our partner companies have employees infected with LummaC2?”
Request
POST /v1/search/categorize-domains · Required scope: search:stealer (all tiers) · Not paginated
| Parameter | Type | Required | Default | Description |
|---|---|---|---|---|
stealer | string | Yes | — | Stealer family name to categorize co-occurring domains for, e.g. "LummaC2" |
agg_per_min limit — see Rate Limits & Tiers.
Example request
Response
200 OK — a single CategorizeDomainsResult object. nextCursor is not
present — this endpoint is not paginated.
| Field | Description |
|---|---|
employeeAt | Domains where matched victims appear to be employees, based on corporate email match |
clientAt | Domains where matched victims appear to be customers/users |
categories | Map of domain → industry category label, derived from VantaPrism’s domain category taxonomy |
Not paginated
This endpoint always returns a single object.cursor/limit/sort_direction
do not apply.
Errors
| Status | code | Cause |
|---|---|---|
| 400 | VALIDATION_ERROR | stealer is missing |
| 403 | FORBIDDEN_SCOPE | Key lacks search:stealer |
| 429 | RATE_LIMIT_EXCEEDED | Exceeded your tier’s agg_per_min |