DEV Community

Wei Bin
Wei Bin

Posted on

I mapped a YouTube channel's entire catalog in two runs — for under a cent

Competitor research on YouTube usually dies in one of two places: you click through forty videos by hand and give up, or you start writing a scraper and give up slightly later, somewhere around the third rate-limit.

I needed a channel's full catalog — titles, URLs, and the view numbers that show which topics actually land — for a content teardown. Instead of building anything, I ran two existing tools back to back. Total elapsed time: under a minute. Total compute cost: less than a cent. Here's the exact pattern, with the real output.

Step 1: Enumerate the catalog (fast, cheap, deliberately shallow)

The first run takes a channel handle and returns its video catalog as structured rows. I pointed it at @OpenAI with a 30-video cap:

  • Wall time: about 7 seconds
  • Rows back: 30
  • Compute cost: $0.001

Each row carries the skeleton: videoId, title, url, channel name and channel ID. What it deliberately does not carry: view counts, durations, publish dates. Those fields come back null, and that's a design choice worth understanding — enumerating a catalog and enriching a catalog are different jobs with different costs. The enumeration pass is built to be nearly free, so you can afford to run it on every competitor you have.

Step 2: Enrich only what you'll actually read

From the 30 rows, I fed 3 video URLs into the companion details tool. Now the expensive fields show up:

Video Views Duration Likes
How Mozilla uses GPT-6 Cyber to find and fix Firefox vulnerabilities 14,565 20:19 160
Cyber at the Frontier: Introducing Daybreak Red Team & Daybreak Defense Factory 51,193 34:36 —
What Codex Unlocks for Holiday Extras 6,772 2:26 70
  • Wall time: seconds
  • Compute cost: $0.0024 for the 3 videos

Notice the honest gaps: one row came back without a like count. Per-video enrichment reads public pages one by one, and public pages don't always expose every counter. A tool that returns a confident number for every field on every video is inventing some of them; I'd rather get a null I can see.

Why the two-step split matters

If you enrich inline during enumeration, a 500-video channel costs 500 detail fetches before you know whether you care about 490 of them. Split the steps and the economics flip:

  1. Enumerate everything — pennies, seconds. Now you have the full topic map: what they publish, how often, how they title.
  2. Sort and filter locally — by title keywords, by series, by recency.
  3. Enrich the shortlist — pay the per-video cost only for the rows that will actually feed a decision.

The same pattern works for TikTok profiles, playlists and search results — enumerate wide and cheap, enrich narrow and deep. It's also how I'd advise evaluating any data tool: ask what the enumeration pass costs before you ask what the detail pass returns.

Running it yourself

Both tools are public Apify actors, no code required — paste a channel handle, set a cap, download JSON or CSV:

If you'd rather automate it, both run through the Apify API with the same inputs, so the two-step pattern drops straight into a script or a scheduled job — a weekly competitor-catalog diff is about twenty lines.

The teardown I built on top of this took an afternoon. The data collection took a minute. That ratio is the whole point: the analysis is the work; the gathering shouldn't be.

Top comments (0)