> For the complete documentation index, see [llms.txt](https://docs.coresignal.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.coresignal.com/company-data/overview.md).

# Multi-source Company Data Overview

Enriched fresh company data from multiple sources with firmographics, funding, workforce trends, and historical signals, available via flat files or API.

**Company data** consists of fresh, structured business records built by combining and reconciling data from business websites, professional networks, funding databases, review platforms, and other public sources into a single, clean profile per company. 

We provide company data as flat files or through the Company data API, with all fields pre-mapped to the corresponding company record. Our system matches records across sources and deduplicates them, so firmographics, financials, growth signals, workforce intelligence, and company intelligence all align under one profile.

| **Comprehensive multi-source dataset** | Multiple sources are integrated to provide a complete company overview.                                                                            |
| -------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Five data bundles**                  | Core company data covers the essentials, with additional enrichment available for financials, growth signals, workforce, and company intelligence. |
| **Save engineering resources**         | The dataset is cleaned, enriched, and ready for use, eliminating the need for deduplication, schema management, or source-by-source normalization. |
| **Leverage historical data**           | Track changes in company metrics over time with aggregated historical data.                                                                        |
| **Optimized file sizes and formats**   | JSONL and Parquet formats reduce file sizes, enabling faster downloads and simpler data loading into warehouses.                                   |

***

## Access and delivery

| Aspect             | Detail                          |
| ------------------ | ------------------------------- |
| Available via      | Flat files and Company data API |
| Delivery frequency | Daily, monthly and quarterly    |
| Available formats  | Parquet, JSONL                  |
| Scraping since     | 2016-07                         |

## Use cases

* **Sales tech** – enhance prospecting and enrichment workflows with firmographics, growth signals, and workforce data to prioritize and route accounts efficiently.
* **Market research** – compare companies to competitors using data on tech stack, product signals, web activity, and reviews.
* **Investment** – monitor funding history, financial performance, headcount trends, and leadership changes to aid due diligence and portfolio oversight.
* **Risk assessment** – observe ownership changes, attrition spikes, and financial indicators as early signs of potential instability.

## Related sources

<table data-card-size="large" data-view="cards"><thead><tr><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td>Company data dictionary</td><td><a href="/company-data/bundles.md">Company Data Bundles</a></td></tr><tr><td>Full company record sample</td><td><a href="/company-data/record-sample.md">Company Record Sample</a></td></tr><tr><td>Company flat files</td><td><a href="/company-data/dataset.md">Company Data Flat Files</a></td></tr><tr><td>Company API</td><td><a href="/company-data/api.md">Company API</a></td></tr></tbody></table>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.coresignal.com/company-data/overview.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.