- Features
- Free cached results
Free cached results
Say how old an answer you accept. A fresh-enough copy costs nothing.
How it works
Add max_age_days, 0 to 30, to any request. If we hold a copy that young, you get it and the response says "cached": true with credits_charged: 0. A miss fetches fresh and charges as usual.
1curl -G "https://api.socialscrape.dev/v1/tiktok/profile" \2 -H "x-api-key: $SOCIALSCRAPE_API_KEY" \3 --data-urlencode "handle=khaby.lame" \4 --data-urlencode "max_age_days=7"Calls use
api.socialscrape.dev and return the shapes in the reference.The rules
- Nothing is served from the cache unless you ask with
max_age_days. - Results are kept at most 30 days; an endpoint page states its own limit.
- The key is the endpoint plus its parameters, shared across customers.
- Your balance, usage and monitors are never cached.
- The ScrapeCreators spelling
cache_max_age=7dalso works.
Others that say so
| Service | What its page says |
|---|---|
| ScrapeCreators | A result already in their cache costs 0 credits. Source |
| SocialPipe | Cache hits and failed calls cost 0 credits. Source |
Retrieved 2026-10-29 from each service's own pages.
Full guide: caching.
Related
Questions
Can a cached result be wrong?
It is as old as cached_at says. Use a small max_age_days, or none, when freshness matters.