# Lead Profile DomainScope (`domainscope/domainscope-lead-profile`) Actor

Categorize and enrich a list of domains in one pass — industry, business model, and target market plus DNS/TLS/tech-stack signals.

- **URL**: https://apify.com/domainscope/domainscope-lead-profile.md
- **Developed by:** [Florin Badita](https://apify.com/domainscope) (community)
- **Categories:** Lead generation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$3.00 / 1,000 domain profileds

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/platform/actors/running/actors-in-store#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.
Actors are written with capital "A".

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## DomainScope Lead Profile — Apify Actor

Take a list of domains and get back a combined profile — category,
industry, business model, target market (via `POST /categorize` /
`/categorize/bulk` / `/jobs/bulk-categorize`) **plus** DNS/TLS/tech-stack
enrichment (via `GET /domains/{url}/enrichment`, public) — in one Actor
run instead of chaining
[URL Categorizer](https://apify.com/domainscope/domainscope-url-categorizer)
and
[Company Enrichment](https://apify.com/domainscope/domainscope-company-enrichment)
by hand.

This is the classic "take my list, give me back everything about it"
pattern — built for cold-email/SDR teams and list brokers who don't want
to run two Actors and join the results themselves.

### Input

See [`.actor/input_schema.json`](.actor/input_schema.json): `domains`
(required). Same sync-single / sync-bulk / async-job cutover as URL
Categorizer for the categorization step (`jobThreshold`, default 25).
`apiKey` is required for more than one domain.

### Output

One row per domain: the categorization fields, plus `enrichment_available`
and a flattened enrichment summary (registrar, domain age, email
provider, TLS issuer, HTTP security score, detected SaaS vendors, trust
grade/score) when enrichment data exists — enrichment coverage is
partial across the corpus, so `enrichment_available: false` is expected
for some domains and doesn't affect billing.

### Billing

Charges one `domain-profiled` event per domain that was successfully
**categorized** (the core, always-available value). Enrichment is a
best-effort bonus layered on top and does not gate the charge, since its
coverage is partial. `Actor.charge()` is a documented no-op outside a
pay-per-event-enabled run, so local development works without any
billing setup.

### Local development

```bash
npm install
echo '{"domains": ["stripe.com"]}' > storage/key_value_stores/default/INPUT.json
npm run start:dev
```

### Deploying

```bash
apify login
apify push
```

# Actor input Schema

## `domains` (type: `array`):

URLs or bare domains, e.g. "stripe.com". One dataset row per domain.

## `apiKey` (type: `string`):

Bearer token for the DomainScope API. Required for more than one domain (categorization of multiple domains requires auth). Leave blank only for a single-domain run, which falls back to the anonymous tier (10 requests/hour).

## `apiBaseUrl` (type: `string`):

Base URL of the DomainScope API, including the /api/v1 path. Change only for staging/testing.

## `jobThreshold` (type: `integer`):

Lists longer than this many domains are categorized via an async job instead of one synchronous call, so large runs cannot time out.

## `pollIntervalSecs` (type: `integer`):

How often to poll GET /jobs/{id}/status while an async categorization job is running.

## `maxPollMinutes` (type: `integer`):

Abort and fail the run if the async categorization job has not finished within this many minutes.

## Actor input object example

```json
{
  "domains": [
    "stripe.com"
  ],
  "apiBaseUrl": "https://domainscope.scrapetheworld.org/api/v1",
  "jobThreshold": 25,
  "pollIntervalSecs": 5,
  "maxPollMinutes": 30
}
```

# Actor output Schema

## `leadProfiles` (type: `string`):

No description

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "domains": [
        "stripe.com"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("domainscope/domainscope-lead-profile").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = { "domains": ["stripe.com"] }

# Run the Actor and wait for it to finish
run = client.actor("domainscope/domainscope-lead-profile").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "domains": [
    "stripe.com"
  ]
}' |
apify call domainscope/domainscope-lead-profile --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,domainscope/domainscope-lead-profile"
        }
    }
}

```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/mahucJCyfsyHwsoBm/builds/qbR1xldNR6w5glQns/openapi.json