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

# Credits

## Overview

Your unique API Key has a set number of credits. Credits are deducted for each successful (200) request when using the collect or enrich endpoints. Each successful request deducts a set number of credits, which you can find on the Pricing page under the [Credit usage per endpoint](/pricing/pricing.md#credit-usage-per-endpoint) topic.

[Search Preview costs](/pricing/pricing.md#search-preview) apply per query returning up to 20 results and depend on the processing level used to retrieve the data.

## Credits in Bulk Collect requests

For Bulk Collect requests, the number of credits deducted from your account depends on the data records count and the used endpoint. For instance, collecting 100 job postings will consume 100 credits.

Read more about Bulk Collect requests in [Bulk Collect requests](/api-introduction/requests/bulk-collect.md) topic.

Discuss your credit needs with your account manager or explore available plans in the [self-service platform](https://dashboard.coresignal.com/sign-in).

## FAQ

<details>

<summary>Where can I see my credit balance?</summary>

Responses contain an `x-credits-remaining` header that shows the number of credits left in your account.

<figure><img src="https://archbee-image-uploads.s3.amazonaws.com/iNaodsHbfav9t72Jx5JdM/Xh3fndrpyjUGXyoMs7qm2_image.png" alt=""><figcaption></figcaption></figure>

**Example of remaining credits header:**

```json
x-credits-remaining: 9973
```

</details>

<details>

<summary>What happens if I don't have enough credits?</summary>

If you don't have enough credits, the request will return error `402` and the following response:

{% code title="Insufficient credits" %}

```json
{
    "detail": "Insufficient credits"
}
```

{% endcode %}

You can repurchase more credits to continue.

</details>

<details>

<summary>What happens if I submit duplicate requests?</summary>

We validate your search and Elasticsearch POST requests in Bulk Collect to prevent duplicate submissions. If you submit duplicate POST requests using search or Elasticsearch filters, you will see the following error message:

{% code title="409" %}

```json
{
    "detail": "Identical data request is already in progress."
}
```

{% endcode %}

</details>


---

# 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/api-introduction/credits.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.