| Thanks a lot for your feedback! On the docs: you caught a real bug. There were some paginated Instagram endpoints that were inheriting TikTok data in the response examples because of a shared base schema, and the override was not being applied correctly. Already fixed and deployed now. On the architecture: I'm not wrapping any third-party API providers. I scrape directly from TikTok and Instagram with Puppeteer + Chromium running on Cloud Run, built from scratch. If I were buying from a third-party scraping API, the economics wouldn't work: those run for $1–3/1k, and I'm selling at $1.11–1.96/1k. The margins only make sense if you own the infra. The scraping challenges are very real: TikTok fingerprints headless browsers aggressively, signs all requests, rotates session requirements, and rate-limits by behavioral patterns rather than just request volume. This infrastructure is what makes it possible to offer no rate limits with great reliability. The added value is the normalization layer: every response follows ActivityStreams 2.0, so a TikTok user and an Instagram user come back with the same fields. You write your code once and it works across both platforms. Appreciate you taking the time to look closely enough to catch the response issue. |