Skip to main content
ScrapeBadger uses a simple credit-based pricing model. Pay only for what you use with transparent, predictable costs.

​
How Credits Work

Purchase Credits

Buy credit packages from your dashboard. Larger packages offer better value per credit.

Make API Calls

Each API request deducts credits from your balance. Each endpoint’s cost is shown on its page.

Track Usage

Monitor your credit usage in real-time from your dashboard. Set up alerts for low balance.

​
Credit Costs by Endpoint

​
Web Scraping

Web scraping retries are free — you only pay for the engine that produces the final result. Failed requests cost 0 credits.

​
Twitter

Twitter/X is billed per item. Each request costs 1 base credit plus 1 credit for every item (tweet, user, etc.) in the response — so a request that returns N items costs N + 1 credits. For example, an advanced_search call returning 20 tweets costs 21 credits. The exact amount charged for any request is returned in the X-Credits-Used response header.
Failed requests (4xx/5xx errors) do not consume credits. You are only charged for successful responses.

​
Repeated requests are free for 60 seconds

If you send the same request again within 60 seconds, the cached response is returned and you are charged 0 credits. “The same request” means the same API key, endpoint, query parameters (in any order) and request body. This covers accidental retry loops and duplicate calls from your code.
  • A cached response has the X-Cache: HIT header, an Age header (seconds since the original call) and X-Credits-Used: 0.
  • If identical requests are sent at the same time, only the first one runs and is billed. The others wait for it and get its result for free.
  • Only successful responses that cost credits are cached. Errors and empty results that cost 0 credits are not cached, so retrying them still makes a real request.
  • To force a fresh result, send Cache-Control: no-cache. That request is billed as normal.
  • Cached responses still count toward your rate limit.

​
Free Credits

New accounts receive free credits to get started. Use them to test the API and build your integration before purchasing more.

Create Free Account

Sign up and get free credits to start building.

​
Credit Packages

We offer a range of credit packages to suit different needs. Larger packages offer better value per credit.

View Pricing Plans

See all available credit packages and pricing.

​
FAQ

Credits are the unit of measurement for API usage. Each API call consumes a certain number of credits based on the endpoint.
No, credits never expire. Once purchased, they remain in your account until you use them.
When your credit balance reaches zero, API requests will return a 402 Payment Required error. You can purchase more credits at any time.
Credits are non-refundable once purchased. However, if you experience technical issues, contact support and we will work with you.
No, not if you repeat it within 60 seconds. An identical request (same API key, endpoint, parameters and body) in that window returns the cached response at 0 credits, marked X-Cache: HIT. See Repeated requests are free for 60 seconds.
No. Google endpoints cache successful responses for 5 minutes. A repeat of the same endpoint with the same query parameters within that window — or sent while an identical request is still running — is served from the cache at 0 credits and marked with an X-Cache: HIT or X-Cache: COALESCED response header. See Google — Response Caching.
Yes! Our larger credit packages offer significant discounts. Check the pricing page for current rates.
Need help with billing? Contact us at support@scrapebadger.com.

​
Review request charges

Use Usage & Logs to review recorded API requests. Choose dates and a scraper, then click Download CSV to export matching request metadata and credit charges. See Download usage logs for the columns, date handling, and export limit.