domains / families / data / scrapecreators-api

scrapecreators-api

combined

Scrape and extract public data from 27+ social media platforms using the ScrapeCreators REST API. Covers TikTok, Instagram, YouTube, LinkedIn, Facebook, Twitter/X, Reddit, Threads, Bluesky, Pinterest, Snapchat, Twitch, Kick, Truth Social, TikTok Shop, Google, and link-in-bio services (Linktree, Komi, Pillar, Linkbio, Linkme, Amazon Shop). Use when the user asks to scrape, fetch, extract, search, or look up social media profiles, posts, videos, reels, comments, transcripts, followers, ads, hashtags, trending content, or engagement metrics from any social platform. Also use when user mentions ScrapeCreators, social media API, ad library, or creator data. Provider reference for collecting public profiles, posts, comments, transcripts, trends, and ad-library data from major social platforms through ScrapeCreators. Use as a dependency of research workflows, not as the final user-facing deliverable.

When to use

Skill page

Conflict

The two copies describe the same ScrapeCreators API but with materially different procedures and constraints. The gooseworks copy is a provider-agnostic wrapper that prioritizes a managed MCP/CLI runtime, forbids using Orthogonal for discovery, and defines a normalized output contract for parent workflows. The ScrapeCreators copy is a direct REST client that requires a user-owned key, mandates fetching per-endpoint OpenAPI specs before calling, and provides a much larger, explicit endpoint routing table. Neither copy is a strict reproduction of the other; crowning one would hide the alternative runtime strategy and the detailed endpoint routing.