# Company Data API: Firmographics, Funding & Hiring (`zaiq/company-data-api`) Actor

Build sourced company profiles from official websites and open registries. Get legal identifiers, dated headcount, filed revenue, funding, technologies and hiring. Bulk domain or name lookup, confidence, conflicts and weekly change monitoring. No accounts or AI key needed. $2.40 per 1,000 profiles.

- **URL**: https://apify.com/zaiq/company-data-api.md
- **Developed by:** [Zaiq](https://apify.com/zaiq) (community)
- **Categories:** Lead generation
- **Features:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.92 / 1,000 company profiles

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

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 Data API: sourced firmographics, funding and hiring

![Company Data API: Firmographics, Funding & Hiring](https://api.apify.com/v2/key-value-stores/4VJNANhwKgqPpXtAi/records/hero-company-data-api.jpg)

Turn company domains or names into sourced company profiles. Each row starts with a plain verdict, followed by legal identifiers, dated employee counts, filed revenue, funding evidence, technologies and hiring signals. Use up to **5,000 companies** in one run.

**$0.0024 per delivered profile**, plus **$0.0006 when funding evidence is returned** and **$0.005 when an open-jobs count is returned**. A full direct profile costs **$0.004**. Network recovery is **off by default**: turn it on and, when alternate network routes recover useful data for a profile, **$0.18 is added** to that profile only, and only when the complete price fits your spending limit. Unresolved names and failed profiles are free.

Sources include the company’s own public website, Wikidata, GLEIF legal-entity records, SEC filings, public job boards, domain registries and the daily Tranco list. No AI key or source account is needed.

### What you get

| Field | What it holds |
|---|---|
| Verdict | One readable line describing the facts that were found, with dated headcount and clear coverage notes. |
| Company identity | Name, legal name, domain, description, logo, stated founding year, headquarters, legal address, industry and company type. Unknown fields remain null. |
| Identifiers and relationships | LEI, CIK, ISIN, ticker, exchange, legal form, jurisdiction, registration status, direct parent, ultimate parent and subsidiaries when the matched sources provide them. |
| Employees and revenue | Employee count or derived size band with its source and date. Annual revenue only from filed XBRL facts, with currency, reporting period and accession number. |
| Funding | Dated announced rounds, explicitly named investor firms, totals by currency and last round. Form D sales and amendments are kept in a separate section. |
| Technology stack | Up to 25 detected technologies with categories, versions where visible, confidence and HTML, header or DNS evidence. |
| Hiring and useful links | Careers and contact URLs, organization social links, a public ATS job count and department counts where available. Vacancies are never presented as employee headcount. |
| Domain facts | Registration date, domain age, registrar and daily top-million rank. Domain registration is never used as a founding date. |
| Evidence and monitoring | Source URLs, field confidence, differing source values, module coverage and changes since the previous successful observations. |
| SUMMARY | Input outcomes, free notes, request counts, traffic, timing, route escalations and event counts. |

### What people use it for

- **CRM enrichment:** Add sourced company facts to a list of accounts and retain the evidence needed to check each field.
- **Account prioritization:** Look for recently announced financing, visible technology choices and active public hiring without collecting personal contacts.
- **Data maintenance:** Schedule the same companies weekly and see which reported employee bands, observed technologies, financing evidence or hiring counts changed.
- **Research pipelines:** Join records by domain, LEI or CIK and distinguish a brand, an operating company and its parent instead of silently merging them.

### How to use it

1. Start with one company domain or website URL. A name is accepted when the open sources identify one company and its official website; otherwise you receive alternatives.
2. Choose the modules you need. Set Maximum cost per run. Leave the company list empty to try one public organization with the default settings.
3. Open the Company profiles table. Read the verdict, then check modules, fieldConfidence and conflicts for facts that matter to your decision.
4. For repeat checks, turn on monitoring, choose a named store and use the same store on your schedule.

### Input

| Field | Example | Notes |
|---|---|---|
| companies | \["company-north.example"] | Domains or website URLs are preferred. Names are checked against open entity records. Maximum 5,000 unique inputs. |
| website | true | Bounded company-page crawl for identity, metadata and useful links. |
| technologies | true | Static HTML, header and DNS signatures. The bundle covers 6,088 technologies; a website will expose only some of its software. |
| registries | true | Open entity matching, legal identifiers, corporate records and filed financial data. Required for name-only inputs. |
| funding | true | Company newsroom announcements, recent public press feeds and verified Form D filings. Charged only when funding evidence is returned. |
| hiring | true | Public ATS count and available department breakdown. Charged only when a count is returned, including a verified zero. |
| domain | true | RDAP registration and a daily rank list cached once per run. |
| maxWebsitePages | 3 | 1–6 useful company pages, within a separate 15-request company-website limit that includes redirects and discovery. |
| maxFundingPages | 3 | 1–5 announcement pages. The output describes the window examined. |
| maxFormDFilings | 8 | 1–25 Form D documents, including amendments. History limits are explicit. |
| monitoring | false | Compare current observations with a named-store baseline. |
| monitorStoreName | company-data-monitor | Use one schedule per store. Different portfolios can use different stores. |

### Output

Each result is one row in the run's dataset (download it as JSON, CSV, Excel, XML or HTML, or read it through the API). An example row (values shortened):

```json
{
  "verdict": "Company · Technology · founded 2020 · Example City, Example Country · 120 employees (2026) · 61 open roles · announced $500M (currency not specified) series-f (2026-06)",
  "status": "complete",
  "name": "Company North",
  "legalName": "Company North Ltd.",
  "domain": "company-north.example",
  "foundedYear": 2020,
  "headquarters": {
    "city": "Example City",
    "country": "Example Country",
    "sourceUrl": "https://registry.example/company-north"
  },
  "employeeCount": {
    "value": 120,
    "asOf": "2026-09-25",
    "sourceUrl": "https://source-4.example/company-north",
    "definition": "Wikidata number of employees; may be historical"
  },
  "employeeBand": "51-200",
  "revenue": null,
  "funding": {
    "rounds": [
      {
        "id": "1b6158305e73d31e55b56365",
        "date": "2026-06-04",
        "stage": "series-f",
        "amount": 500000000,
        "currency": null,
        "amountText": "$500M",
        "amountQualifier": null,
        "amountBasis": "announced financing",
        "investors": [
          {
            "name": "Example Investment Firm",
            "role": "lead"
          }
        ],
        "sourceUrl": "https://source-1.example/company-north",
        "sourceHeadline": "Company North Series F",
        "notes": [
          "Dollar currency not specified; no USD conversion or amount-filter match assumed."
        ]
      }
    ],
    "totalAnnouncedByCurrency": {},
    "formDFilings": [],
    "formDAmountSoldUsd": null
  },
  "openJobsCount": 61,
  "hiring": {
    "provider": "Public ATS",
    "byDepartment": {
      "Business Operations": 2,
      "Data + Growth": 1,
      "Engineering": 30,
      "Marketing": 5,
      "Operations": 1,
      "Partnerships": 4,
      "Product": 4,
      "Sales": 1,
      "Success": 4,
      "Support": 9
    },
    "complete": true,
    "departmentsComplete": true
  },
  "technologies": [
    {
      "name": "Technology 1",
      "category": "DNS",
      "categories": [
        "DNS"
      ],
      "version": null,
      "confidence": 100,
      "detection": "observed",
      "evidence": [
        {
          "type": "dns",
          "sourceUrl": "https://source-2.example/company-north"
        }
      ]
    },
    {
      "name": "Technology 2",
      "category": "DNS",
      "categories": [
        "DNS"
      ],
      "version": null,
      "confidence": 100,
      "detection": "observed",
      "evidence": [
        {
          "type": "dns",
          "sourceUrl": "https://source-2.example/company-north"
        }
      ]
    },
    {
      "name": "Technology 3",
      "category": "Webmail",
      "categories": [
        "Webmail",
        "Email"
      ],
      "version": null,
      "confidence": 100,
      "detection": "observed",
      "evidence": [
        {
          "type": "dns",
          "sourceUrl": "https://source-3.example/company-north"
        }
      ]
    }
  ],
  "domainRegistrationDate": "2017-09-24",
  "trancoRank": 4956,
  "fieldConfidence": {
    "foundedYear": {
      "confidence": "medium",
      "sourceUrl": "https://source-4.example/company-north",
      "observations": [
        {
          "value": 2020,
          "sourceUrl": "https://source-4.example/company-north",
          "confidence": "medium"
        }
      ],
      "asOf": null
    }
  },
  "sources": [
    {
      "url": "https://source-5.example/company-north",
      "module": "website",
      "httpStatus": 200,
      "retrievedAt": "2026-10-26T09:23:47Z"
    },
    {
      "url": "https://source-6.example/company-north",
      "module": "website",
      "httpStatus": 200,
      "retrievedAt": "2026-10-26T09:23:47Z"
    },
    {
      "url": "https://source-7.example/company-north",
      "module": "website",
      "httpStatus": 200,
      "retrievedAt": "2026-10-26T09:23:47Z"
    }
  ]
}
```

This shortened example comes from an actual software-company run recorded on 26 October 2026. Company, investor, technology and location names, handles and site addresses have been replaced. Numeric facts and dates are retained. The announcement used an unqualified dollar sign, so its currency remains unknown and it is not added to a USD total. SUMMARY in the run’s key-value store records outcomes and charges.

### Pricing

- **Company:** $0.0024 for each delivered sourced profile. A registered domain or a technology signature alone is not enough to charge for a company identity.
- **Funding:** add $0.0006 only when matched announcement or Form D evidence arrives. Empty or unavailable searches add nothing.
- **Hiring:** add $0.005 only when a public ATS count arrives. Verified zero-job boards are valid results; unavailable boards are not.
- **Network recovery (off by default):** when you turn it on, add $0.18 if an alternate route returns useful sourced data in the delivered profile. The recovery traffic allowance is bounded. Public bulk reference files are fetched directly.
- **The same price on every Apify plan.** There is no separate AI-model bill.
- Apify’s **$0.00005 start charge** counts towards the buyer’s **Maximum cost per run**.
- Launch price on the main events. It may rise later; Apify emails every user 14 days before any price increase takes effect, and a rise can happen at most once a month.

What typical jobs cost at the list price:

| Job | Cost |
|---|---|
| One direct base profile | $0.00245 including the start charge |
| 100 direct base profiles | $0.24 including the start charge |
| An unresolved name or failed company lookup | No company, funding, hiring or recovery event; only the start charge |

Set Maximum cost per run before starting. The Actor checks that the base profile fits before fetching it, and checks the combined price before optional work or network recovery. If an optional module does not fit, it can still deliver the base profile. Free notes continue after the limit. The price is the same on every Apify plan.

### Tips

- Inputs that resolve to a company domain already delivered in the same run return a free duplicate note.
- Use domains for reliable matching, particularly for short names shared by several businesses.
- Read the date beside employee counts. Open knowledge records can be years behind a company’s current workforce.
- Use funding and hiring as separate signals. An exempt offering, a public announcement, a job opening and employee headcount describe different things.
- Keep source URLs and field confidence when exporting to another system. A null field means unknown, not zero.
- Run one monitoring schedule per named store. Concurrent runs against the same store can overwrite each other’s checkpoint.

### Use it through the API

**Python**

```python
from apify_client import ApifyClient

client = ApifyClient("<YOUR_APIFY_TOKEN>")
run = client.actor("zaiq/company-data-api").call(run_input={"companies": ["company-north.example"], "funding": true, "hiring": true, "monitoring": false})
for row in client.dataset(run.default_dataset_id).iterate_items():
    print(row)
```

**JavaScript**

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

const client = new ApifyClient({ token: '<YOUR_APIFY_TOKEN>' });
const run = await client.actor('zaiq/company-data-api').call({"companies": ["company-north.example"], "funding": true, "hiring": true, "monitoring": false});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
```

**HTTP (one call, results back)**

```bash
curl -X POST 'https://api.apify.com/v2/acts/zaiq~company-data-api/run-sync-get-dataset-items?token=<YOUR_APIFY_TOKEN>' \
  -H 'Content-Type: application/json' \
  -d '{"companies": ["company-north.example"], "funding": true, "hiring": true, "monitoring": false}'
```

### Integrations and schedules

- **Schedules:** run it every hour, day or week from the Apify Console (Schedules) and keep a history of results.
- **Make, Zapier, n8n, Google Sheets, Slack, Airtable:** connect it through Apify's integrations, or send each finished run to a **webhook**.
- **Datasets:** results stay in the run's dataset; export them or read them by API whenever you need them.

### Use it with AI agents (MCP)

Add Apify's MCP server with this Actor already pinned (`https://mcp.apify.com?tools=zaiq/company-data-api`) to Claude, ChatGPT, Cursor, VS Code or any MCP client. The agent can find this Actor and run it for you: ask it for "enrich these company domains with sourced firmographics and show changes since last week". AI agents can also pay for runs directly through Apify's agentic payments.

### Limits

- The result is a profile of facts returned by the selected public sources, not a complete commercial database entry. Private-company revenue, current headcount and a full funding history are often unavailable.
- Wikidata is community-maintained open data. Official filings and registry records have stronger evidence, but registered-agent addresses, foreign-filer addresses and operating locations are kept distinct.
- Short or ambiguous names may remain unresolved. Candidate results are shown, and a domain is never invented. Related companies sharing a website are not automatically merged.
- The website crawl is bounded and respects robots.txt. A login wall, bot check, empty application shell, rate limit or inaccessible page produces a coverage note. No browser is used.
- Hiring supports public boards from seven ATS systems. Custom careers systems may be unavailable. Some boards cap totals; partial department counts are marked, and incomplete hiring observations do not imply closed jobs.
- Announcement totals cover matched sources only. Currencies are not mixed. Form D amounts are cumulative sales as filed, and linked amendments replace earlier figures for the same offering.
- Detection means a public signature was observed. A technology disappearing from a later crawl does not prove it was uninstalled.
- Domain registration can change after a transfer or deletion. The ranking is a daily domain list, not a visitor count or revenue estimate.
- Funding announcement parsing works best with English announcements that state an amount, date and financing stage. Other languages or indirect descriptions may remain unavailable.
- Monitoring stores up to 10,000 company snapshots per named store. Source failures preserve earlier observations. Financing records disappearing from a bounded search are not reported as lost funding.
- A complete status means the requested checks completed within their stated bounds; it does not mean every field is known.

### FAQ

**Can I send only a company name?**

Yes. The Actor looks for a matching open entity with a sourced official website. If there is no confident selection, the note and alternatives are free.

**Is this a list of personal contacts?**

No. It returns company-level facts, company social links and hiring totals. It does not return people, individual emails or phone numbers.

**Can I turn modules off?**

Yes. Registry calls, domain checks, funding and hiring work are skipped when their modules are off. Technologies, funding and hiring may still need the public homepage to identify the company and discover their sources. A company identity must be established before a base profile is charged.

**Are empty funding and hiring results charged?**

An empty or failed funding search is free. Hiring is charged only for a returned count; a verified count of zero is still a result.

**Are funding and Form D totals combined?**

No. Announced rounds and official exempt-offering sales remain separate. Amendments are not counted as additional raises.

**Will a restart charge the same company twice?**

Delivered input keys are read from the dataset before work resumes. Their rows and optional events are skipped. A narrow interruption after the row but before an optional event can leave that optional result uncharged.

**How do weekly changes work?**

Enable monitoring and reuse the named store. The first run establishes a baseline; later rows identify changed employee bands, new funding evidence, observed technology additions or removals and hiring differences. Unavailable sources are not treated as disappearance.

### Related Actors from Zaiq

- [tech-stack-detector](https://apify.com/zaiq/tech-stack-detector): deeper website technology evidence
- [funding-rounds-tracker](https://apify.com/zaiq/funding-rounds-tracker): recent financing discovery across many companies
- [ats-jobs-scraper](https://apify.com/zaiq/ats-jobs-scraper): individual public job listings
- [sec-edgar-scraper](https://apify.com/zaiq/sec-edgar-scraper): deeper company filings and financial facts

### Support

Questions, a site that changed, or a field you need? Open an issue on this Actor's **Issues** tab: we answer there, usually within a day.

***

Also found as: company data API, firmographic data API, company enrichment, bulk company lookup, company profiles, company funding data, company hiring signals, company monitoring.

# Actor input Schema

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

Up to 5,000 companies. Domains give the most reliable identity match. Ambiguous names return free alternatives. Leave empty for one public nonprofit example. Duplicate inputs are delivered once.

## `website` (type: `boolean`):

Read a bounded set of company pages for its stated identity, description, address, social profiles and useful links.

## `technologies` (type: `boolean`):

Apply the bundled 6,088-technology engine to public HTML, response headers and DNS. At most 25 technologies are displayed, with evidence.

## `registries` (type: `boolean`):

Match Wikidata to the official domain, then read verified LEI and SEC records. Required to resolve name-only inputs. Missing fields remain unknown.

## `funding` (type: `boolean`):

Read linked company announcements and verified SEC exempt-offering filings. Adds a fee only if funding evidence is delivered. This is a bounded search, not lifetime funding coverage.

## `hiring` (type: `boolean`):

Count vacancies on a supported public ATS board linked by the company. Adds a fee only when a count is delivered. Jobs are never used as employee headcount.

## `domain` (type: `boolean`):

Read the IANA-selected RDAP registry and the daily top-million domain ranking, downloaded once per run. A registration date is not a company founding date.

## `maxWebsitePages` (type: `integer`):

Maximum home, about, contact and careers pages per company. Robots and redirects count towards a separate 15-request website safety limit.

## `maxFundingPages` (type: `integer`):

Maximum company funding announcements to examine after following a newsroom link.

## `maxFormDFilings` (type: `integer`):

Maximum original and amended Form D documents per verified SEC filer. The output states whether history was truncated.

## `networkRecovery` (type: `boolean`):

Off by default. When on, company sites and job boards that refuse a normal connection are retried through alternate network routes, and $0.18 is added only to a delivered profile where those routes returned useful sourced data. Traffic is bounded; public bulk reference files always load directly.

## `monitoring` (type: `boolean`):

Save a compact company snapshot in a named store and report changes in funding evidence, reported headcount band, detected technologies and hiring. Use one schedule per store; unavailable sources do not erase a baseline.

## `monitorStoreName` (type: `string`):

Use the same store name on each scheduled run. Each run still delivers current profiles. Avoid simultaneous runs against the same store.

## Actor input object example

```json
{
  "companies": [],
  "website": true,
  "technologies": true,
  "registries": true,
  "funding": true,
  "hiring": true,
  "domain": true,
  "maxWebsitePages": 3,
  "maxFundingPages": 3,
  "maxFormDFilings": 8,
  "networkRecovery": false,
  "monitoring": false,
  "monitorStoreName": "company-data-monitor"
}
```

# Actor output Schema

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

Dataset: the results.

## `summary` (type: `string`):

What each input returned, and notes.

# 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": [],
    "website": true,
    "technologies": true,
    "registries": true,
    "funding": true,
    "hiring": true,
    "domain": true,
    "maxWebsitePages": 3,
    "maxFundingPages": 3,
    "maxFormDFilings": 8,
    "monitorStoreName": "company-data-monitor"
};

// Run the Actor and wait for it to finish
const run = await client.actor("zaiq/company-data-api").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": [],
    "website": True,
    "technologies": True,
    "registries": True,
    "funding": True,
    "hiring": True,
    "domain": True,
    "maxWebsitePages": 3,
    "maxFundingPages": 3,
    "maxFormDFilings": 8,
    "monitorStoreName": "company-data-monitor",
}

# Run the Actor and wait for it to finish
run = client.actor("zaiq/company-data-api").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": [],
  "website": true,
  "technologies": true,
  "registries": true,
  "funding": true,
  "hiring": true,
  "domain": true,
  "maxWebsitePages": 3,
  "maxFundingPages": 3,
  "maxFormDFilings": 8,
  "monitorStoreName": "company-data-monitor"
}' |
apify call zaiq/company-data-api --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,zaiq/company-data-api"
        }
    }
}
```

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/eNofPU4Lh7lbh42xy/builds/6odpo3hmadXnFk4pd/openapi.json
