# Company Name to Domain and Tech Stack (`leadharbor/company-domain-tech-lookup`) Actor

Company names in, official website domain and detected tech stack (CMS, e-commerce, analytics, CRM, hosting) out. Unresolved companies are not billed.

- **URL**: https://apify.com/leadharbor/company-domain-tech-lookup.md
- **Developed by:** [Mohammed Samaan](https://apify.com/leadharbor) (community)
- **Categories:** Lead generation, Developer tools
- **Security:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

Pay per event

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/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
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.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## 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.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## Company Name to Domain and Tech Stack

Give it company names. For each one you get the official website domain and the technologies that homepage uses, grouped as CMS, e-commerce, analytics, CRM and hosting.

**Price:** $0.004 per company whose domain was found, plus $0.001 per run start. Companies with no match are returned with an error and are **not billed**.

### How it works

1. Looks the company up in Bing search results, then in Wikidata (the public "official website" field), then tries a guessed domain (`name.com`, or the country ending you give).
2. Opens each candidate homepage and keeps it only if the page matches the company name (all distinctive words of a one or two word name must appear on the page, or the domain must equal the full name). This is a name check, not a guarantee: `verified: true` means "the homepage matched the name".
3. Reads that same homepage's response headers, cookies, meta tags, script URLs and HTML markers for 100+ known technologies.

Plain HTTP only. No browser, no proxy, no AI model, no login. Technologies that are injected only by JavaScript at runtime (some tag-manager-loaded tools) can be missed. "CRM" means the marketing/CRM and support tools visible on the page (HubSpot, Pardot, Marketo, Mailchimp, Klaviyo, Zendesk, Freshdesk); it cannot see a CRM that has no script on the public homepage. "Hosting" means hosting, CDN and web-server signals (for example Cloudflare, Vercel, Nginx).

Search engines can change their pages or block requests, and very small or non-English-named companies may not resolve. Check the `verified` and `domain` fields before relying on a row.

### Input

| Field | Type | Notes |
|---|---|---|
| `companies` | list of text | Required. Up to 2,000 per run. Duplicates removed. |
| `country` | text | Optional hint, e.g. `UAE`, `Oman`, `Germany`, `UK`. |
| `concurrency` | integer | 1 to 20, default 5. |

#### Example 1: global companies

```json
{ "companies": ["Stripe", "Shopify", "Notion"] }
```

#### Example 2: Gulf companies with a country hint

```json
{ "companies": ["Emaar Properties", "Damac Properties", "Almarai"], "country": "UAE" }
```

#### Example 3: a mixed list (unresolved names are free)

```json
{ "companies": ["Basecamp", "Some Made Up Company Zzyzx", "Mailchimp"], "concurrency": 3 }
```

### Output (one row per company)

```json
{
  "company": "Stripe",
  "domain": "stripe.com",
  "website": "https://stripe.com",
  "verified": true,
  "matchedBy": "search",
  "techStack": { "cms": [], "ecommerce": [], "analytics": [], "crm": [], "hosting": ["Nginx"], "other": ["Next.js", "React"] },
  "technologies": [{ "name": "Nginx", "category": "Web server", "version": null }],
  "error": null
}
```

An unresolved company has `domain: null`, `verified: false` and an `error` message, and is not charged. `matchedBy` is `search`, `wikidata` or `guess`.

# Actor input Schema

## `companies` (type: `array`):

One company name per line, e.g. Stripe or Emaar Properties. Duplicates are removed.

## `country` (type: `string`):

Helps with local companies, e.g. UAE, Oman, Germany, UK. Adds the country to the search and tries its domain ending (.ae, .om, .de, .co.uk) when guessing.

## `concurrency` (type: `integer`):

How many companies are processed at the same time (1-20). The default is fine for most lists.

## Actor input object example

```json
{
  "companies": [
    "Stripe",
    "Almarai",
    "Emaar Properties"
  ],
  "concurrency": 5
}
```

# Actor output Schema

## `results` (type: `string`):

One row per company: domain, verified flag and detected tech stack.

## `resultsUi` (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 = {
    "companies": [
        "Stripe",
        "Almarai",
        "Emaar Properties"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("leadharbor/company-domain-tech-lookup").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 = { "companies": [
        "Stripe",
        "Almarai",
        "Emaar Properties",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("leadharbor/company-domain-tech-lookup").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 '{
  "companies": [
    "Stripe",
    "Almarai",
    "Emaar Properties"
  ]
}' |
apify call leadharbor/company-domain-tech-lookup --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,leadharbor/company-domain-tech-lookup"
        }
    }
}
```

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/yzuqza0qnKTm0V0yC/builds/M72kq0BNoS8DmfkiC/openapi.json