> 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): An overview of Coresignal datasets and APIs. Select the data solution best suited to your use case and access up-to-date 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): Compare Coresignal products by record coverage, file formats, processing levels, and delivery options. - [Data for AI](https://docs.coresignal.com/introduction/data-for-ai.md): This page explains why Coresignal data is a good fit for AI pipelines and how to integrate it. - [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 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/introduction.md?ask=&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.