DomainScope Similar Domains Finder — Apify Actor

Find similar/competitor domains for a list of anchor domains, via GET /api/v1/domains/{url}/similar — public, no DomainScope account or API key required. Uses HNSW/cosine nearest-neighbour search over DomainScope's stored domain embeddings.

Coverage caveat — embeddings are not computed for every domain

Embedding coverage across the ~12M-domain corpus is partial: it's populated per-domain only when explicitly triggered (via POST /search/update-embedding or an internal backfill job), not automatically on categorization. An anchor with no embedding on file returns anchor_not_embedded rather than a 500, so this Actor reports it as a clean per-anchor error ("No similar domains found...") instead of failing the whole run — but expect some anchors, especially newer or less mainstream domains, to come back empty.

Input

See .actor/input_schema.json:

• domains (required) — anchor domains to find neighbours for.
• k — max neighbours per anchor (default 20, ceiling 100).
• minScore — cosine similarity floor, 0–1 (default 0, no floor).

Output

One dataset row per (anchor, similar domain) pair: anchor, url, score, industry, country, business_model, category, shared_signals. Anchors with no results get a single row with an error field instead, and are not charged.

Billing

Charges one similar-domain-returned event per neighbour delivered (not per anchor) — the value delivered is the result rows. Actor.charge() is a documented no-op outside a pay-per-event-enabled run, so local development works without any billing setup.

Local development

npm install
echo '{"domains": ["asana.com"], "k": 10}' \
  > storage/key_value_stores/default/INPUT.json
npm run start:dev

Or: apify run --input '{"domains": ["asana.com"]}'

Deploying

apify login
apify push