Data transparency / October 4, 2026

What a real response sample contains.

Five live searches. 500 returned rows. 421 distinct creator records. This is a small, query-selected snapshot—not an estimate of the entire directory.

Field presence across 421 distinct records
Profile ID421 / 421 · 100.0%
Username421 / 421 · 100.0%
Follower count421 / 421 · 100.0%
Country421 / 421 · 100.0%
Email on file394 / 421 · 93.6%

The exact sample

Each query used page 1, limit 100 and the default API sort, without an email filter. These popular topics and the first-page ranking can bias coverage upward. Repeating the requests later may return different records.

fitness

100 rows

84 with email

beauty

100 rows

94 with email

skincare

100 rows

98 with email

gaming

100 rows

98 with email

fashion

100 rows

93 with email

79 rows overlapped across queries. The overall field counts above use distinct profile IDs, not all 500 rows.

Measured, not estimated

All five search requests returned HTTP 200 and consumed 10 credits each. One follow-up profile read returned HTTP 200 and consumed 1 credit. Free balance checks confirmed 51 credits in total on an isolated internal verification account. Its key was revoked after the run; no customer balance was used.

What this does not establish

A populated field is not proof of accuracy, freshness, email deliverability, consent or campaign fit. We did not send email, verify identities, check audience demographics or independently validate these values. Zero followers counts as a populated field.

Reproduce with your own criteria

GET /v1/creators/search?q=fitness&page=1&limit=100

Record your filters and collection date, then inspect the response in your browser. Your own niche and geography may have different coverage.