> 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/employee-data/clean-employee-data.md).
# Clean Employee Data
Clean Employee Data is designed to be used for **sales tech, HR intelligence, and investment.**
| **Spend fewer engineering resources** | Our Clean Employee data is cleaned, enriched, and ready to use. |
| -------------------------------------- | ------------------------------------------------------------------------------------------ |
| **Additional data fields** | Leverage additional data fields for more precise analysis. |
| **More formats and reduced size** | Download the data in JSONL, Parquet, and CSV formats in smaller files for faster download. |
| **Download flat files or use the API** | Choose the data retrieval method that fits you the most. |
***
## Summary
| Feature | Details |
| ------------------ | ------------------- |
| Available via | Flat files/API |
| Delivery frequency | Weekly and monthly |
| Available formats | JSONL, Parquet, CSV |
| Scraping since | 2016-07 |
## Related links
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.coresignal.com/employee-data/clean-employee-data.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.