# AI Company URL Lead Qualify

> This actor will use a company URL and return : The Value Proposal of the company, the industry, the target market and target profile. It will help marketing team qualifying leads on the fly.

Actor id `quaking_pail/ai-company-url-lead-qualify`. Index of all Epsimo actors: https://epsimo.org/llms.txt

## What it does

### Company Domain Info Actor

This Actor processes lists of company domains and enriches each domain by calling a proprietary external API (AlphaForH) via POST requests, performing domain normalization and URL cleaning, extracting and parsing JSON responses, and producing structured business profiles. Technical capabilities include domain preprocessing (protocol removal and normalization), secure API interaction with response validation, JSON parsing and data extraction, and per-domain error logging for HTTP and parsing issues. The Actor outputs, for each domain, a structured record containing the processed domain and extracted company attributes such as value proposition, industry classification, target audience description, and market segment.

### Use cases

- Enriching company domain lists with business attributes (value proposition, industry, target audience, market).
- Automated domain normalization and validation prior to enrichment.
- Building structured company profiles for market research and analysis.
- Lead or account enrichment workflows that require company-level metadata.
- Batch processing of domains with per-domain error handling and logging.

## Use cases and Limits

Not published.

## Input

| Name | Type | Required | Default | Allowed values / range | Description |
|---|---|---|---|---|---|
| `domains` | array | yes | - | - | List of company domain names (e.g., example.com) you want to scrape data from. |

## Example input

Built from the input schema prefill/default values (the actor publishes no example input).

```json
{
  "domains": [
    "danone.com",
    "epsimoai.com"
  ]
}
```

## Output

Not published.

The dataset view `overview` (Overview) shows these fields: `company_domain`, `value_proposition`, `industry`, `target_audience`, `market`. Their types and descriptions are not published.

## Example output item

Not published.

## Pricing

Pay per event, in effect since 2026-10-16 (as of 2026-10-18). Each event below is charged.

| Event | Title | Description | Price USD (FREE tier) |
|---|---|---|---|
| `apify-actor-start` | Actor Start (once per run) | Charged when the Actor starts running. Number of events charged depends on Actor memory (one event per GB, minimum one event). | $0.00005 |
| `apify-default-dataset-item` | Qualified company (primary) | One company domain qualified by AI and saved to the default dataset. Failed domains are never charged. | $0.011 |

Plan-tier prices for `apify-default-dataset-item`: FREE $0.011, BRONZE $0.01, SILVER $0.009, GOLD $0.008, PLATINUM $0.008, DIAMOND $0.008.

Prices are in USD at the Apify FREE plan tier; tiered events can cost less on paid Apify plans (plan-tier prices above). The [Apify Store page](https://apify.com/quaking_pail/ai-company-url-lead-qualify) is authoritative: read the current price there instead of hardcoding these values.

## How to run

Run the actor and get its dataset items in one HTTP call (needs an Apify API token in `$APIFY_TOKEN`, sent in the `Authorization` header as Apify recommends ([Apify API authentication](https://docs.apify.com/api/v2))):

```bash
curl -X POST "https://api.apify.com/v2/acts/quaking_pail~ai-company-url-lead-qualify/run-sync-get-dataset-items" \
  -H "Authorization: Bearer $APIFY_TOKEN" \
  -H 'Content-Type: application/json' \
  -d '{
  "domains": [
    "danone.com",
    "epsimoai.com"
  ]
}'
```

Apify also accepts `?token=$APIFY_TOKEN` in the URL, but avoid it: URLs end up in logs and shell history.

If the run takes longer than 300 seconds, this endpoint returns HTTP 408 (Request Timeout). For longer runs start the actor with the asynchronous [Run Actor endpoint](https://docs.apify.com/api/v2/act-runs-post) and read the dataset when the run finishes. The `maxTotalChargeUsd` query parameter caps the total cost of a run ([run-sync-get-dataset-items reference](https://docs.apify.com/api/v2/act-run-sync-get-dataset-items-post)).

## Apify MCP

Apify hosts an MCP server at https://mcp.apify.com. The actor id is `quaking_pail/ai-company-url-lead-qualify`; the `tools` query parameter loads only that actor as a tool ([Apify MCP server](https://docs.apify.com/platform/integrations/mcp)).

```json
{
  "mcpServers": {
    "apify": {
      "url": "https://mcp.apify.com?tools=quaking_pail/ai-company-url-lead-qualify",
      "headers": {
        "Authorization": "Bearer $APIFY_TOKEN"
      }
    }
  }
}
```

Replace `$APIFY_TOKEN` with your Apify API token. Without the `headers` entry the client signs in to Apify with OAuth in the browser instead.

## Links

- Apify Store: [quaking_pail/ai-company-url-lead-qualify](https://apify.com/quaking_pail/ai-company-url-lead-qualify)
- Sources: [actor API](https://api.apify.com/v2/acts/quaking_pail~ai-company-url-lead-qualify), [build API](https://api.apify.com/v2/acts/quaking_pail~ai-company-url-lead-qualify/builds/default)
- Data fetched from the Apify API on 2026-10-18
- Build: 0.0.31

## Do not

- Do not hardcode prices: read them on the Apify Store page before a large run.
- Do not put the Apify token in shared URLs, prompts or logs; prefer the `Authorization` header.
- Do not treat the output as verified: it is scraped from public pages and can be incomplete, outdated or wrong.