> ## Documentation Index
> Fetch the complete documentation index at: https://docs.geekflare.com/llms.txt
> Use this file to discover all available pages before exploring further.

# API Credit Consumption

We utilize a flexible Credit System in Geekflare API. Instead of limiting you to a specific number of requests per endpoint, your subscription provides a pool of credits that can be used across our entire suite of APIs.

Different API endpoints consume different amounts of credits based on the computational resources and bandwidth required to process the request.

## Credit Usage

The table below outlines the credit cost for a single successful request to each endpoint.

| API Endpoint                    | Credits Per Request |
| :------------------------------ | :------------------ |
| **DNS Lookup**                  | 1                   |
| **Site Load Time**              | 1                   |
| **URL Redirection**             | 1                   |
| **TLS Scan**                    | 1                   |
| **Web Scraping (Lite)**         | 1                   |
| **Web Scraping (JS Rendering)** | 2                   |
| **Port Scanner**                | 2                   |
| **Meta Scraping**               | 2                   |
| **Broken Link Checker**         | 2                   |
| **Search**                      | 2                   |
| **Search with Scrape**          | 4                   |
| **Search with Grounded Answer** | 5                   |
| **Proxy**                       | 5                   |
| **Screenshot**                  | 5                   |
| **PDF Generator**               | 5                   |
| **Lighthouse Audit**            | 10                  |

The credits required for each API request are visible in the [Playground](https://docs.geekflare.com/api/api-playground) as well, so you know your potential consumption.

<img src="https://mintcdn.com/geekflare/P7koTDQgBS90E0ID/images/playground-credit-info.png?fit=max&auto=format&n=P7koTDQgBS90E0ID&q=85&s=b495ea94a60d21c266aa616b383597c7" alt="Playground credit info" width="2506" height="1852" data-path="images/playground-credit-info.png" />

## Usage Mechanics

### 1. Calculation Logic

Credits are deducted immediately upon the successful execution of an API call.

<Note>
  {" "}

  Example: If you make 10 calls to the **Web Scraping API with JS Rendering**,
  you will consume `20 credits` (10 calls × 2 credits).{" "}
</Note>

### 2. Failed Requests

We value fairness. You are generally **not charged** for API errors caused by our infrastructure (HTTP 5xx status codes).

* **4xx Errors:** Requests that fail due to invalid user input (e.g., specific bad URLs, missing parameters, or unauthorized access) generally do not consume credits.

### 3. Proxy Usage (Add-on Cost)

The **Premium Proxy** feature costs **5 credits per request**. This is an additional cost applied on top of the base API endpoint.

The proxy feature can be enabled on various HTTP-based APIs (such as Web Scraping, Screenshot, and Headers). Please refer to our [Using Proxies](https://docs.geekflare.com/api/using-proxies) documentation for the full list of supported endpoints.

**Calculation Example:**
If you make a **Web Scraping** request and enable the Proxy feature:

* **Web Scraping with JS Rendering Cost:** 2 Credits
* **Proxy Add-on Cost:** + 5 Credits
* **Total Consumed:** **7 Credits**