> 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/self-service/features-and-tools/ai-data-search/lists-pricing.md).
# Lists Pricing
Understand AI Data Search credit costs for list previews, enrichment, and exports.
Pricing is based on the same credit logic used for multi-source data across the Coresignal self-service platform and APIs.
### Search and preview list
The maximum preview list size is 20 records, and each preview costs 20 credits. The prompt itself is free, and the credits are only used once a list preview is generated. If a search returns zero results or requires clarification, no credits are used.
This model keeps search predictable while allowing users to preview meaningful result sets before moving to enrichment.
### Enrichment price
Enrichment is charged per data record, not per action.
* Enriching a single row costs 1-20 credits, depending on the requested data (see the [Pricing](/pricing/pricing.md#credit-usage-per-endpoint) page).
* You can enrich anywhere from one record to 10,000.
* The maximum number of profiles you can enrich is 10,000. This means that the enrichment cost is capped at 200,000 credits if you have a full preview list and all preview data is enriched.
Each data record is charged for enrichment only once. After that, you can apply additional enrichments or adjust fields without using extra credits.
### Export cost
CSV and JSONL exports are free because they export data you already see in your list. You can generate and download as many files as needed, and the exported data will exactly match what you see in your list.
Full JSONL file generation costs 1-20 credits per record, depending on the requested data. The full file is paid because it includes all record data fields, showing more information than the previously mentioned CSV and JSONL exports. The estimated cost is shown before creating a JSONL file.
If you do not have sufficient credits to export the full dataset, a partial JSONL file will be generated instead. You can download the number of records that corresponds to your available credits.
---
# 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/self-service/features-and-tools/ai-data-search/lists-pricing.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.