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

# Introduction

- [Welcome to Coresignal](https://docs.coresignal.com/introduction/welcome-to-coresignal.md): Overview of available datasets and APIs. Select the right data solution for your use case and access fresh company, employee, and job posting data.
- [Data and Compliance](https://docs.coresignal.com/introduction/data-and-compliance.md): Learn how Coresignal collects fresh public web data ethically and in compliance with global privacy regulations.
- [Delivery Formats](https://docs.coresignal.com/introduction/delivery-formats.md): Access Coresignal's fresh B2B data via flat files (JSONL, Parquet, CSV) or APIs. Supports S3, Azure, GCS delivery.
- [Product Comparison](https://docs.coresignal.com/introduction/product-comparison.md)
- [FAQ](https://docs.coresignal.com/introduction/faq.md): Answers common questions about Coresignal data, pricing, compliance, API access, credits, and subscriptions.


---

# 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/introduction.md?ask=<question>&goal=<endgoal>
```

`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.