Pay for live fetches, not for asking twice.

A cache hit costs zero credits on every plan, including the free one, which starts you with 1,000.

Free
$0
1,000 credits

Enough to finish an integration, not a toy.

  • All operations
  • 30 requests/min
  • No card required
Start free
Growth
$49/mo
25,000 credits / mo

$1.96 per 1,000 credits.

  • All operations
  • 240 requests/min
  • Cache hits free
  • Usage export
Choose Growth

Higher volume

Production workloads above 25,000 credits a month are priced per account so the rate matches your actual operation mix. Tell us what you are building and what volume you expect.

Talk to us

What spends a credit.

Every response carries X-Credits-Charged, including when it is zero. You are not billed for a resource that turned out to be private, deleted, or for an upstream that failed on us.

Read the billing docs →
ClassCostApplies to
Basic1–2 creditspost, profile, resolve
List2–3 creditsprofile/posts
Cached0 creditsAny operation served from cache
Unavailable0 creditsNot found, private or upstream failure

Questions worth answering properly.

PublicOnly public profiles and posts
CacheRepeated reads cost 0 credits
PrivateNo contact or login-walled data

Where does the data come from?

Publicly visible profile and post information from TikTok, Instagram and YouTube, retrieved through upstream data providers and normalized into a single schema. Nothing behind a login, nothing from a private account, and no contact details at any point.

What does a credit cost, and what uses one?

Credits are charged per operation. A simple profile or post lookup costs one; list operations such as recent posts cost two; heavier derived operations cost more. A cache hit costs zero. You are billed for live fetches, so repeated checks on the same resource are cheap.

How fresh is the data?

Every response carries source_timestamp, fetched_at and cache_age_seconds, so you can see exactly how old a figure is. Cached results are served within a short window that varies by resource type; you can force a live fetch when you need one. We do not advertise real-time, because upstream behaviour does not let us prove it.

Why is there no bio field?

Creator bios routinely contain email addresses, phone numbers and messenger handles. Returning them would mean storing contact details for people who never dealt with us, so the field is excluded from the schema entirely rather than filtered after the fact.

What happens when a profile or post no longer exists?

You get a typed availability status — not_found, private or unavailable — rather than an ambiguous error, and you are not charged. Our upstream bills us for those lookups; that cost is ours, not yours.

What if I run out of credits mid-integration?

Requests keep working and bill as overage at a higher per-credit rate — nothing gets cut off mid-run. Set a balance alert at a threshold you choose, or turn on automatic top-up so it never comes up.

Can I use this for anything I like?

Within the acceptable use policy. Building profiles of private individuals, contact enrichment, and redistributing bulk personal data are not permitted. The product is scoped to public metrics for business and campaign use.

Which platforms are coming next?

Coverage expands where upstream reliability supports it. We would rather do three platforms consistently than list ten and have half of them return partial data — so we announce a platform when the normalized response for it is stable.

Paste a URL. Get JSON back.

The free tier is sized to finish a real integration, not to tease one. No card required.