# Coresignal

> Coresignal is a public web data provider that maintains three large refreshed datasets, roughly 70 million company records, over 900 million employee profiles, and more than 475 million job postings, plus a newer social posts feed, delivered through search and lookup APIs, an agentic natural-language search endpoint, an MCP server, and flat file exports in CSV, JSONL, or Parquet, with a 7-day free trial and API plans from $49 per month.

- Category: Buying Signals & Intent (https://saastracker.org/categories/intent-signals)
- Website: https://coresignal.com
- Starting price: $49 per month (Mini, 2,500 credits)
- Free plan: No
- Free trial: 7 days with 2,000 credits
- Founded: 2016, HQ: Vilnius, Lithuania, Ownership: Privately held
- Profile last reviewed: 2026-08-22
- Canonical profile: https://saastracker.org/products/coresignal

## Overview

Coresignal is the layer underneath a lot of the tools in this category. It does not try to be a sales application: there is no scoring, no sequencing, no CRM sync, and nothing that resembles a dashboard for a rep. What it sells is refreshed public web data at scale, and the buyers are usually people building something on top of it, whether that is an internal account-scoring model, a recruiting product, an investment screen, or a Clay table.

The signals it carries are the institutional ones: who works where, when that changed, which companies are hiring for what, how headcount is trending, and which firmographic attributes describe a company today. Job changes and hiring surges are the two that a go-to-market team cares about most. A person moving into a new role at a target account, or a company suddenly opening eight roles in a function, are both textbook buying triggers, and Coresignal carries the records that make either detectable at scale.

The company was founded in 2016 in Vilnius, Lithuania and has grown from a single data source to fifteen or more public web sources, serving several hundred organisations across sales technology, HR technology, investment, and market research. Its compliance posture is better documented than most of this category: GDPR and CCPA alignment plus certification by the Ethical Web Data Collection Initiative, which is a meaningful thing for a company whose entire business is collecting public web data about people.

For a small business the entry point is genuinely reachable. A 7-day trial gives 2,000 credits, and the Mini plan is $49 a month for 2,500 credits. That is enough to enrich a couple of hundred company records or pull a few thousand job postings, which is a real test rather than a teaser. What it is not is a finished product. If you want somebody to hand you a list of accounts to call this week, buy something else; Coresignal hands you a firehose and a documented schema.

## How it works

1. Coresignal continuously collects from fifteen or more public web sources and normalises what it finds into three primary datasets plus a newer social posts feed. Company records carry hundreds of fields, employee profiles carry hundreds more, and job postings carry dozens including salary, seniority, and location. Company and employee history runs back to 2016 and job data to 2020.

2. You reach the data three ways. Search and filter endpoints return record identifiers matching a query, collect endpoints return the full record for an identifier, and an Agentic Search API accepts a natural-language description and resolves it into a query, which is the newest surface and the one aimed at agent builders. An MCP server exposes the same capability to Claude, Cursor, and other assistants directly.

3. Credits are the meter and they are consumed per record retrieved rather than per query. A company or employee record costs roughly 10 to 20 credits, a job posting costs 1, and contact enrichment costs 20. That asymmetry matters enormously when you are sizing a plan: job posting work is cheap and people work is not.

4. For teams that want the data in bulk rather than through calls, flat files ship as CSV, JSONL, or Parquet, and there are delivery paths into AWS S3, Google Cloud, Azure, Snowflake, and Databricks. Lighter-weight integrations exist for Zapier, n8n, and Clay, which is how most small teams actually consume it without writing a pipeline.

## Best for

Technical go-to-market operators building their own account scoring or job-change alerting, recruiting and HR tech builders, investment analysts screening private companies at scale, and anyone already running Clay who wants a cheaper, deeper source behind their enrichment waterfalls.

## Not the right fit for

- Salespeople who want a tool to open in the morning. There is a self-service dashboard, but the product assumes you are building something; a rep with no engineering support will not get value from it.
- Teams that need signals delivered as tasks. Coresignal has no scoring, no routing, no sequencer, and no CRM integration; every one of those is your build.
- Buyers who need website technographics or storefront data. Coresignal covers people, companies, and jobs, not what software renders on a domain.
- Anyone who assumed the headline record counts equal usable volume for $49. Employee records at 10 to 20 credits each mean the Mini plan buys you a couple of hundred profiles, not thousands.
- Organisations uncomfortable with public web data collection as a category. The compliance documentation is better than most, but the underlying activity is scraping public profiles and some legal teams will not sign off on it regardless.

## Features

### The datasets

Scale and history, which is the entire proposition.

- **Company data**: Roughly 70 million company records with over 500 fields covering firmographics, headcount trends, funding, industry, and location, with history since 2016.
- **Employee data**: Over 900 million employee profiles with 300-plus fields including current and past roles, tenure, skills, education, and location, which is the raw material for job-change detection.
- **Job posting data**: More than 475 million postings with 85-plus fields, going back to 2020, and priced at just 1 credit per record, which makes hiring-signal work dramatically cheaper than people work here.
- **Social posts data**: A newer feed of company and employee posts, which brings a community and activity signal into a dataset that was previously purely structural.
- **Fifteen or more public web sources**: Multi-source collection rather than dependence on a single site, which reduces exposure to any one platform changing its access rules.
- **History since 2016**: Longitudinal records mean you can detect that something changed, which is what separates a signal from a snapshot.

### Access surfaces

Several ways in, aimed at different levels of technical appetite.

- **Company, Employee, and Jobs APIs**: Search, filter, and collect endpoints per dataset, with documented schemas and a published response time target.
- **Agentic Search API**: Accepts a natural-language description of what you want and resolves it into a structured query, aimed at teams building agents rather than writing filters by hand.
- **MCP server**: Exposes the datasets through the Model Context Protocol so Claude, Cursor, or a custom assistant can query them conversationally.
- **Elasticsearch DSL queries**: Included on all paid plans, which gives far more expressive filtering than a fixed set of dropdowns and is the reason technical buyers prefer this over consumer-facing tools.
- **Webhooks**: Included on every paid plan for push-based delivery rather than polling.
- **Self-service dashboard**: A web surface for browsing and pulling records without code, adequate for evaluation and light use.

### Bulk delivery and pipelines

For teams loading the data rather than calling it.

- **Flat files in CSV, JSONL, or Parquet**: Bulk datasets delivered in warehouse-native formats rather than only through an API.
- **Cloud destination delivery**: AWS S3, Google Cloud, and Azure as delivery targets for scheduled dataset drops.
- **Warehouse integrations**: Snowflake and Databricks paths for teams that want the records queryable next to their own data.
- **Clay integration**: Coresignal is available as a provider inside Clay, which is how most small go-to-market teams should consume it: the orchestration comes from Clay and the depth comes from here.
- **Zapier and n8n**: No-code automation paths for teams that want records to trigger actions without writing a service.

### Plan mechanics and governance

The details that determine what the bill actually looks like.

- **Credit-based metering**: Credits are consumed per record retrieved: roughly 10 to 20 for a company or employee record, 1 for a job posting, and 20 for contact enrichment.
- **Rate limits by tier**: Throughput rises with plan size from a few requests per second at the bottom to over a hundred at the top, which matters if you are enriching in bulk against a deadline.
- **Three-month credit rollover**: Higher tiers let unused credits carry forward, which smooths out lumpy usage rather than punishing it.
- **Ethical Web Data Collection Initiative certification**: Third-party certification of collection practices, which is more documentation than most vendors in this category publish and is worth having when a customer's legal team asks.
- **GDPR and CCPA alignment**: Published compliance posture covering the personal data in the employee dataset.

## Use cases

- **RevOps lead building job-change alerts**: Former customers and champions move to new companies constantly, and the CRM has no way to notice. Outcome: A scheduled job matches the CRM's contact list against employee profiles, flags anyone whose current employer changed, and drops the match into Slack, which is the single highest-converting outbound trigger most teams have.
- **Recruiting product founder**: The product needs a company and talent graph underneath it, and building the collection layer would consume the whole roadmap. Outcome: Employee and job posting datasets deliver as Parquet into the company's warehouse, and the product ships against a maintained source instead of a scraper the founder has to babysit.
- **Investment analyst screening private companies**: Headcount growth is the best available proxy for traction in companies that publish nothing, but tracking it manually across a watchlist is impossible. Outcome: Company records with headcount history and job posting volume produce a monthly growth screen across several thousand private companies, surfacing outliers before a round is announced.
- **Small team already running Clay**: Enrichment waterfalls keep failing on mid-market European companies where the usual providers have thin coverage. Outcome: Coresignal is added as a provider in the waterfall, coverage improves on exactly the segment that was failing, and the team pays credits only for the records the earlier providers missed.

## Pricing

Credit-based API subscriptions billed monthly or annually, with credits consumed per record retrieved; bulk datasets are quoted separately by contract length and scope.

- **Free trial**: $0 7 days. 2,000 credits; API access to evaluate coverage; No credit card commitment beyond the trial window. 2,000 credits buys roughly 100 to 200 employee or company records, or 2,000 job postings. Test on job data if you want a broad read on coverage.
- **Mini**: $49 per month for 2,500 credits. Multi-source endpoints; Agentic Search API; Elasticsearch DSL queries; Webhooks; Roughly 2 cents per credit. Realistically 125 to 250 people or companies a month, or 2,500 job postings. Fine for a targeted motion, useless for bulk enrichment.
- **Starter**: $199 per month for 12,000 credits. 12,000 credits monthly; Roughly 1.7 cents per credit; Faster rate limits than Mini; All API surfaces included.
- **Pro**: $499 per month for 35,000 credits. 35,000 credits monthly; Roughly 1.4 cents per credit; Three-month credit rollover; Higher throughput for bulk enrichment.
- **Growth and above**: $1,000 per month for 150,000 credits. Scales through Premium at $1,500 for 1M credits; Scale at $3,000 for 4M credits; Elite at $5,000 for 10M credits; Rate limits above 100 requests per second at the top. The per-credit price collapses at the top of the range, from around 2 cents on Mini to a small fraction of a cent on Elite.

Add-ons:

- Bulk datasets (Quoted, starting from around $1,000): Priced by contract length and dataset scope rather than by credit; this is the flat-file and warehouse delivery path.

Billing notes:

- Prices are published as of August 2026. Annual plans carry a 10 percent discount against monthly.
- Credit consumption is wildly uneven across datasets: a job posting costs 1 credit while an employee or company record costs 10 to 20 and contact enrichment costs 20. Sizing a plan on the headline credit number without accounting for this is the most expensive mistake a buyer makes here.
- Three-month credit rollover on higher tiers means unused balance is not simply lost, which materially improves the economics of lumpy project work.
- Rate limits scale with plan, so a cheap plan with enough credits can still be too slow for a same-day bulk enrichment run.
- Bulk file and warehouse delivery is a separate commercial motion starting around $1,000, so the self-serve API tiers and the dataset product are effectively two different purchases.

Value assessment: Model it at two volumes. A small team on Mini at $49 pulling 2,500 job postings a month is paying about 2 cents a posting for hiring signal, which is excellent; the same $49 spent on employee profiles buys around 150 people, or roughly 33 cents each, which is expensive against a general contact database. That asymmetry is the whole story. At Pro, $499 for 35,000 credits gets you around 2,000 enriched people or 35,000 job postings a month at 1.4 cents a credit. Coresignal is outstanding value for hiring and company data and merely competitive for people data, and the right way to buy it is to be very deliberate about which dataset you are actually consuming.

## Strengths

- Genuine scale across three datasets with history back to 2016, which makes change detection possible rather than just snapshots.
- Job posting records at 1 credit each are the cheapest hiring signal in this category by a wide margin.
- Developer surfaces are unusually complete: Elasticsearch DSL filtering, webhooks, an Agentic Search API, and an MCP server, all included on the $49 plan rather than gated to enterprise.
- Delivery options span the full range from an API call to Parquet files landing in Snowflake, so the same vendor works for a two-person team and a data platform.
- Compliance documentation is better than the category norm: GDPR and CCPA alignment plus Ethical Web Data Collection Initiative certification.
- Available as a provider inside Clay, which lets a non-technical team use the depth without building anything.
- Nine years old, independently operated, and serving several hundred organisations, so the dataset is not a weekend project.

## Limitations

- This is infrastructure, not a product. There is no scoring, no routing, no sequencing, and no CRM integration, so a go-to-market team needs either engineering support or Clay sitting on top.
- Credit costs differ by an order of magnitude between datasets, and the pricing page's headline credit counts make plans look far more generous than they are for people data.
- No website technographics or storefront data at all, so it complements rather than replaces the crawler-based tools in this category.
- Employee profile freshness depends on people updating their own public profiles, which means a job change can be weeks or months old before it becomes detectable, and some never surface.
- Public web data collection is a category that some legal teams will refuse on principle regardless of certification, particularly for EU employee data.
- Rate limits at the bottom tiers are modest, so a plan sized correctly on credits can still be wrong on throughput.
- Bulk dataset delivery starts around $1,000 and is sales-quoted, so the friendly self-serve pricing does not extend to the flat-file product.

## Comparisons

- **Coresignal vs TheirStack**: TheirStack takes job postings and does the extraction and intent work for you, with a web app a salesperson can use, from $49 a month with the API included in the same credits. Coresignal sells the underlying records across jobs, companies, and people, and expects you to build the interpretation. Buy TheirStack if you want answers; buy Coresignal if you want records to build on, or if you need employee and company data alongside the hiring signal.
- **Coresignal vs Crunchbase**: Crunchbase owns funding rounds and investor relationships with an editorial layer, from $29 to $49 per user per month, and is usable by a non-technical person on day one. Coresignal owns headcount, hiring, and employment history at far greater scale but hands you raw records. For a founder tracking who just raised, Crunchbase. For a system that scores accounts on growth signals continuously, Coresignal.
- **Coresignal vs PredictLeads**: PredictLeads bundles job openings, technographics, funding, and news into one source-linked API with a free tier of 100 calls a month. Coresignal goes deeper on employee and company records and offers warehouse-native bulk delivery, but carries no technographics. PredictLeads is the better single API for signal variety; Coresignal is the better foundation when depth of people and company data is what you are missing.
- **Coresignal vs Clay**: These are complements, not competitors, and the pairing is the standard recommendation. Clay orchestrates enrichment waterfalls, applies logic, and pushes into sequences but relies on providers for data. Coresignal is one of those providers and is available inside Clay directly. A small team should buy Clay for the workflow and add Coresignal when the default providers keep missing their segment.
- **Coresignal vs LeadMagic**: LeadMagic is a lean, credit-priced API for contact and company enrichment including job-change detection, aimed squarely at small teams who want one call and one answer. Coresignal is a broader and deeper dataset with warehouse delivery and far more fields, at more setup cost. Pick LeadMagic for simple enrichment on a budget; pick Coresignal when you need the underlying graph rather than a lookup.

## Implementation

- Setup time: A day for a working API integration if you have an engineer, and about an hour if you are consuming it through Clay or the self-service dashboard. The trial credits are enough to validate coverage on your specific segment before you commit.
- Learning curve: Moderate to steep depending on your route in. The Elasticsearch DSL filtering is powerful and not immediately obvious, and understanding the credit model well enough to avoid a surprise bill takes a careful read of the documentation.
- Onboarding: Self-serve for the API tiers with no sales call required, including the trial. Bulk dataset delivery is a quoted commercial conversation rather than a checkout.
- Migration: Nothing to import. Because delivery is raw records rather than a stateful application, everything you have pulled is already in your own systems and there is no lock-in beyond your integration code. Moving to a different data provider means rewriting field mappings, which is real but bounded work.

## Platform, API & security

- Platforms: REST APIs for companies, employees, and jobs, Agentic Search API, MCP server, Self-service dashboard, Flat files in CSV, JSONL, and Parquet
- API: Search, filter, and collect endpoints per dataset with Elasticsearch DSL query support and webhooks on all paid plans, plus a natural-language Agentic Search API and an MCP server for AI assistants. Rate limits scale from a few requests per second to more than a hundred by tier.
- Compliance: GDPR aligned, CCPA aligned, Certified by the Ethical Web Data Collection Initiative
- Data residency: Not published per region; delivery targets include AWS, Google Cloud, and Azure of your choosing for bulk files.
- SSO: Not advertised on the published self-serve tiers.
- Security notes: The employee dataset consists of personal data drawn from public web sources, which places real obligations on the buyer as a controller when it is used for outreach into the EU. The Ethical Web Data Collection Initiative certification and published GDPR and CCPA posture are more documentation than most competitors offer, but they do not remove the buyer's own compliance responsibility.

## Support

- Channels: Email support, Account contact on higher tiers
- Documentation: Extensive API documentation covering every endpoint, the credit model, Elasticsearch DSL query syntax, webhooks, and the flat-file schemas, plus dataset field references.
- Community: No formal user forum; the company publishes technical and market research content alongside the documentation.

## Company

- Founded: 2016
- Headquarters: Vilnius, Lithuania
- Ownership: Privately held
- Employees: Not disclosed
- Funding: No major venture round publicly disclosed; the company reports serving several hundred organisations across sales, HR, investment, and research.

Timeline:

- 2016: Coresignal starts in Vilnius with a single public web data source covering companies, jobs, and employees, which is also where the historical record begins.
- 2020: Job posting data collection begins in earnest, establishing the corpus that now runs past 475 million records.
- 2022: Collection expands to fifteen or more public web sources, reducing dependence on any single platform's access policy.
- 2024: Bulk delivery into Snowflake, Databricks, and the major cloud object stores makes the datasets viable for teams that want records in a warehouse rather than through an API.
- 2026: An Agentic Search API and an MCP server ship alongside a new social posts dataset, and self-serve API plans start at $49 per month for 2,500 credits.

## Integrations

Clay, Zapier, n8n, Snowflake, Databricks, AWS S3, Google Cloud, Microsoft Azure, MCP server for Claude and other assistants, Webhooks

## FAQ

### What is Coresignal?

Coresignal is a public web data provider. It maintains roughly 70 million company records, over 900 million employee profiles, and more than 475 million job postings, plus a newer social posts feed, collected from fifteen or more public web sources and delivered through APIs, an MCP server, or bulk files in CSV, JSONL, and Parquet. It is data infrastructure rather than a sales application.

### How much does Coresignal cost?

A 7-day trial includes 2,000 credits. Paid API plans run $49 a month for 2,500 credits, $199 for 12,000, $499 for 35,000, $1,000 for 150,000, $1,500 for 1 million, $3,000 for 4 million, and $5,000 for 10 million. Annual billing saves 10 percent. Bulk file and warehouse delivery is quoted separately starting around $1,000.

### Which signal does Coresignal own?

Job changes, hiring and job postings, and headcount growth. Employee profiles with employment history make job-change detection possible; the job posting corpus makes hiring surges detectable; company records with headcount history make growth trends visible. It does not carry website technographics, funding-round curation, or website visitor identification.

### How fresh is the data and how stale do the worst records get?

Job postings are the freshest layer, since a posting either exists or it does not and collection is continuous. Employee profiles are the weakest, because their freshness depends on individuals updating their own public profiles: a job change typically becomes visible somewhere between a few days and a few months after it happened, and a person who never updates their profile never surfaces at all. Company records sit in between. Design any job-change alerting around the assumption that you are seeing a lagging indicator.

### How does credit pricing actually work out per record?

A job posting costs 1 credit, a company or employee record costs 10 to 20, and contact enrichment costs 20. So $49 for 2,500 credits is either 2,500 job postings at 2 cents each, which is excellent, or roughly 125 to 250 people at somewhere near 20 to 40 cents each, which is not. At Pro, $499 for 35,000 credits, the per-credit rate falls to about 1.4 cents. Decide which dataset you are consuming before you pick a plan.

### Could I get this signal free from a public source?

For a handful of accounts, yes. Job postings are public, company career pages are public, and public professional profiles show employment history to anyone who looks. Checking twenty accounts by hand each week costs nothing but time. What is not free is doing that across hundreds of thousands of records, keeping a longitudinal history since 2016 so you can detect what changed, or getting it in a schema you can join against your own data. Coresignal sells the scale and the history, not the underlying facts.

### Is the output a dashboard or a routed task?

Neither, by design. The output is records: API responses, webhook payloads, or files. There is a self-service dashboard adequate for browsing and light pulls, but nothing scores, ranks, or routes anything. If you want a signal to become a task in front of a rep, that logic is yours to build, or you consume Coresignal through Clay and let Clay do it.

### Are exports limited, and does the API cost extra?

The API is the product, so it does not cost extra: every plan from $49 upward includes the full set of endpoints, Elasticsearch DSL filtering, webhooks, the Agentic Search API, and the MCP server. What is limited is credits and rate limit throughput, both of which scale with plan. Bulk flat-file export is the exception: that is a separate commercial product starting around $1,000, not something included in the self-serve tiers.

### Is Coresignal compliant, given it collects data about people?

Coresignal publishes GDPR and CCPA alignment and holds certification from the Ethical Web Data Collection Initiative, which is more third-party documentation than most vendors in this category offer. That said, when you use employee data to contact people in the EU you become a controller with your own obligations, and no vendor certification transfers that to them. Some legal teams decline public web data as a category regardless of paperwork.

### Should I buy Coresignal or use it through Clay?

If you do not have engineering time, use it through Clay. Coresignal is available as a provider there, so you get the depth without building a pipeline, and Clay handles the waterfall logic, deduplication, and routing that Coresignal deliberately does not. Buy Coresignal directly when you are building a product on the data, need bulk delivery into a warehouse, or are consuming enough volume that Clay's own pricing becomes the constraint.

## Editorial verdict

Coresignal is the best-documented raw data source a small technical team can buy in this category, and it is priced so that job posting and hiring signal work is genuinely cheap while people data is merely fair. The developer surfaces are the giveaway about who it is for: Elasticsearch queries, webhooks, an MCP server, and Parquet files in your warehouse are not features aimed at a sales rep. Buy it if you are building something, whether that is a job-change alerting job, an account growth score, or a product with a talent graph underneath it. Buy it through Clay if you want the depth without the pipeline. Do not buy it expecting a tool that tells you who to call today, and do not size a plan on headline credit counts without checking that an employee record costs twenty times what a job posting does.

---

Source: SaaSTracker (https://saastracker.org), an independent editorial project. This profile is compiled from public information, carries no peer reviews or paid placement, and was last reviewed 2026-08-22. Awards are judged on published criteria: https://saastracker.org/methodology