/v1/scrape/* endpoints that wrap the public-data surfaces of the major creator + ad platforms. You don’t manage a separate scraper account — we hold the upstream master credentials and meter the calls through your existing API key.
One key, one bill, one ToS. No ScrapeCreators / Apify / RapidAPI signup, no duplicate billing, no second rate-limit page to babysit.
When to use it
- Creator research — pull a profile + recent posts, then pipe each into
watchMediafor hook + format analysis - Ad research — sweep Meta / Google / LinkedIn / Reddit ad libraries for a competitor or keyword and score the creative
- Content repurposing — fetch a long-form YouTube video and run it through transcribe + watch to find clip-worthy moments
- Social listening — keyword-search across TikTok / IG / X, classify sentiment, rank by reach
- Influencer scouting — filter profiles by engagement rate, then watch their last 5 posts for fit
What you get
| Category | Endpoints |
|---|---|
| TikTok | profile, profile videos, video, video transcript, video comments, user search, trending |
| profile, user posts, post, post comments, user reels | |
| X (Twitter) | profile, user tweets, tweet, tweet transcript |
| YouTube | channel, channel videos, video, video comments |
| Ad libraries | Meta, Google, LinkedIn, Reddit |
download_media — the one flag that matters
Most endpoints accept an optional download_media: boolean (default false).
- Off (default) — Response contains raw source CDN URLs. Cheapest, but those URLs (e.g.
tiktokcdn-us.com,cdninstagram.com) are typically gatekept — you usually can’t fetch them from another tool without auth. - On — VidJutsu fetches every media URL in the response, stages it to our CDN, and replaces source URLs with VidJutsu URLs in the response. Now you can pipe directly into
watchMedia,transcribeMedia, or any external LLM video tool.
Cost
Every call counts as one request against the sharedscrape rate group: 500 calls / day across all 24 endpoints. Staging media with download_media: true does not consume extra quota — it is still a single request.
Recipe — research a creator end-to-end
- SDK
- CLI
- curl
Recipe — competitive ad teardown
- SDK
- CLI
Limits and caveats
- No private-content access. Scrape only resolves public posts, profiles, and ad-library entries. Anything behind a follower lock, age gate, or login wall is out of scope.
- Best-effort upstream. Platforms occasionally throttle or restructure their public surfaces; expect occasional
upstream_unavailableerrors and retry with a small delay. - Not legal advice. You’re responsible for how you use scraped public data — respect the source platform’s ToS for downstream uses, and never republish private personal data.
- No background polling. Don’t tight-loop the same endpoint; if you need fresh data, hit it at a sane interval (5+ minutes for the same key/handle).