Skip to main content

​
How credits work

Every API key has a credit balance. Each scrape request deducts a fixed number of credits. Credits are deducted on both cache hits and fresh scrapes — you’re paying for the data, not the compute.

​
Credit costs

EndpointCreditsDescription
GET /v1/instagram/profile1Single profile lookup
GET /v1/instagram/user/posts2User’s recent posts
GET /v1/instagram/post1Single post by shortcode
GET /v1/instagram/post/comments2Comments on a post
GET /v1/credit-balance0Check your balance (free)

​
Checking your balance

curl -H "x-api-key: sk-your-api-key" \
  https://api.scraper.creatorlookup.com/v1/credit-balance
Every successful scrape response also includes credit info: 
{
  "data": { ... },
  "credits_used": 2,
  "credits_remaining": 9498
}

​
Insufficient credits

If your balance is too low for a request, you’ll receive a 402 error: 
{
  "error": {
    "code": "INSUFFICIENT_CREDITS",
    "message": "This endpoint requires 2 credits, you have 1"
  }
}
The request is not processed and no credits are deducted.

​
Credit deduction rules

  • Credits are deducted only on successful responses (HTTP 2xx)
  • Failed scrapes (502, 504) do not cost credits
  • Cached responses still cost credits (same rate as fresh scrapes)
  • The credit-balance endpoint is always free