> 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/data-introduction/data-overview.md).

# Data Overview

Browse Coresignal datasets on fresh, regularly updated public web data.

All datasets listed below come from public web sources and are regularly updated, so you always have access to current records when building enrichment pipelines, scoring leads, or tracking market signals.

## Company data

<table data-view="cards"><thead><tr><th></th><th></th><th></th><th></th></tr></thead><tbody><tr><td><a href="/company-data/overview.md"><strong>Company Data</strong></a></td><td>Get a full view of any company – data from multiple sources reflects the latest firmographics, headcount changes, and funding activity</td><td><a href="/company-data/bundles.md">Data dictionary</a></td><td><a href="/company-data/record-sample.md">Data sample</a></td></tr></tbody></table>

## Employee data

<table data-view="cards"><thead><tr><th></th><th></th><th></th><th></th></tr></thead><tbody><tr><td><a href="/employee-data/overview.md"><strong>Employee Data</strong></a></td><td>Unlock updated employee insights with enriched records that include career history, skills, and education from multiple public networks</td><td><a href="/employee-data/bundles.md">Data dictionary</a></td><td><a href="/employee-data/record-sample.md">Data sample</a></td></tr></tbody></table>

## Jobs data

<table data-view="cards"><thead><tr><th></th><th></th><th></th><th></th></tr></thead><tbody><tr><td><a href="/jobs-data/overview.md"><strong>Jobs Data</strong></a></td><td>A unified, deduplicated feed of job postings sourced from multiple sources – fresh data for the most current hiring signals</td><td><a href="/jobs-data/data-dictionary.md">Data dictionary</a></td><td><a href="/jobs-data/record-sample.md">Data sample</a></td></tr></tbody></table>

## Social Posts data

<table data-view="cards"><thead><tr><th></th><th></th><th></th><th></th></tr></thead><tbody><tr><td><a href="/social-posts-data/company-posts.md"><strong>Company Posts Data</strong></a></td><td>Explore the latest public company communication – from product launches to strategic announcements</td><td><a href="/social-posts-data/company-posts/data-dictionary.md">Data dictionary</a></td><td><a href="/social-posts-data/company-posts/record-sample.md">Data sample</a></td></tr><tr><td><a href="/social-posts-data/employee-posts.md"><strong>Employee Posts Data</strong></a></td><td>Track employee engagement: posts, reactions, and comments to surface emerging trends</td><td><a href="/social-posts-data/employee-posts/data-dictionary.md">Data dictionary</a></td><td><a href="/social-posts-data/employee-posts/record-sample.md">Data sample</a></td></tr></tbody></table>

## Discover next

<table data-view="cards"><thead><tr><th></th><th></th></tr></thead><tbody><tr><td><a href="/api-introduction/apis-overview.md"><strong>APIs Overview</strong></a></td><td>Data available via APIs</td></tr></tbody></table>

{% hint style="success" %}

#### Start a free trial

All new users can test data quality with free **API credits**. After the trial, select an API subscription plan based on your business needs

<a href="https://dashboard.coresignal.com/sign-up" class="button primary">Start now</a>
{% endhint %}


---

# 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/data-introduction/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.