Skip to main content
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. The credits required for each API request are visible in the Playground as well, so you know your potential consumption. Playground credit info

​
Usage Mechanics

​
1. Calculation Logic

Credits are deducted immediately upon the successful execution of an API call.
Example: If you make 10 calls to the Web Scraping API with JS Rendering, you will consume 20 credits (10 calls × 2 credits).

​
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 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