Subscription figures are provider list prices recorded in treg.to’s own catalog grid; per-call prices are what treg.to charges today, with $0.000 added.
set up treg — https://treg.to/llms.txt
Using treg, get the view count, like count and publish date for these 30 YouTube video ids and put them in a table sorted by views. Show me the price first.
The v= parameter of the watch URL. Most providers take the id, not the URL.
Google's API takes 50 ids in one call for the price of one.
Views, likes and duration live in different parts of the response.
Your own Google connection is free; the paid providers need no account.
treg.to holds the provider keys. Neither you nor the agent sees them.
The provider's own rate, $0.000 markup, from a prepaid balance.
Charged per call. $1.00 free per new team, no card to start.
Already pay Hunter? Register it and those calls are never metered.
Another provider is a different word in the prompt, not a new integration.
No SDK, no OAuth dance per vendor, no seats.
treg.to does not choose for you. It hands ChatGPT this comparison, with the price shown before any call, and ChatGPT picks. Or you tell it how: "cheapest", "most reliable", "the one that takes what I have", or a provider by name.
Bright Data at $0.0015
TikHub at $0.001
ScrapeCreators at $0.00188
Those units are not interchangeable: one call can return many results, so compare on the unit you will actually be billed in.
| Provider | Success | Median | Sample |
|---|---|---|---|
| 100% | 1.6s | 80 calls | |
| 100% | 2.1s | 40 calls |
Measured on treg.to traffic: real calls, real inputs, and sample sizes differ by provider. Live reliability, not a controlled benchmark.
| Provider | Price | Accepts | Success rate | Verified |
|---|---|---|---|---|
| $0.001 per found | video_id, language_code, need_format, video_url | 100% (40 calls) | 2026-07-28 | |
| $0.0015 per result | dataset_id, format, input | not yet measured | unverified | |
| $0.00188 per call | url | 100% (80 calls) | 2026-07-28 | |
| $0.0148 per found | videoId | (1 calls) | 2026-07-28 | |
| free, your own account | part, id | (4 calls) | 2026-07-28 |
treg call brightdata.x.youtube-videos
Swap the id for any provider above. All 7 endpoints behind this job, with their parameters and captured responses, are on the YouTube shelf.
Almost nobody complains about the price of this call. They complain about the daily cap, and about whether the number they got is today's number. From ~180 Reddit and X posts in August 2026, with the vendor clusters excluded, these five recur.
“i exceeded youtubes API quota. womp womp. Anyway, it should be back and updating properly at midnight pacific time.” r/Destiny, 575 points
What this page can do about it: The daily budget resets at midnight Pacific, so a bug in the morning costs the rest of the day. Reading a video costs 1 unit of 10,000 and batches 50 ids into that one unit, so most people who hit the wall were spending it on search. The paid rows have no daily ceiling; treg.to shows you both and you pick, it does not switch over on its own.
“The strange thing is, my daily usage counter (which I'm tracking in the script) shows that I'm nowhere near the daily quota limit.” r/pythontips, 2 points
What this page can do about it: The recurring complaint is not running out, it is not knowing why. We cannot fix Google's quota accounting. What a metered call gives you instead is a definite price before it goes and a definite outcome after, so the ambiguous middle disappears.
“Apparently that IP address is for AWS.” r/MailChimp, 6 points
What this page can do about it: The error underneath that thread is API_KEY_IP_ADDRESS_BLOCKED, and it is the same story as the transcript job: it worked until it was deployed. A call through treg.to leaves the provider's infrastructure, not your host's. Whether your own host is blocked is a property of your host, and no comparison table has that column.
“during certain intervals, views increase without likes/comments scaling proportionally, while at the hourly aggregate level everything looks perfectly normal” r/HiddenTrueCrimeChat, 23 points
What this page can do about it: This is the honest limit of every row on this page. View counts are aggregated and sometimes revised downward by YouTube itself, and every provider here is downstream of that. A table can compare price and measured success rate; it cannot tell you whose number is right, because on some hours no number is.
“Google youtube API has a quota limits, so I added over 45 API” r/MetaRayBanDisplay, 4 points
What this page can do about it: Forty-five keys is a lot of Google projects to own, and it is the shape people reach for when the only lever is a daily cap. The alternative here is a per-call price with no cap and no rotation to maintain. Spend the free quota first if you have it.
Batching is not an optimisation here, it is a fifty-fold difference in what a day's quota buys you.
Bright Data bills per record delivered, TikHub and Just One API bill per successful call, ScrapeCreators bills the call whether or not it found the video. A run over a list with dead ids costs differently on each.
Treat a missing field and a zero as different answers when you aggregate.
One video's public record: the snippet (title, description, tags, channel, publish date), the statistics (view count, like count, comment count) and the content details (duration, definition, caption availability). It is the same data the watch page shows, as JSON. Watch time, impressions, click-through rate and audience retention are not here; those are YouTube Analytics, and only the channel owner can read them.
Yes, on your own Google account, and treg.to never meters a call on your own key. What it is not is unlimited: 10,000 quota units a day by default, which this method spends 1 at a time. The paid providers exist for when that runs out.
No. Those are YouTube Analytics numbers and only the channel's owner can read them, through a connected account. Everything on this page is the public record of the video.
Only for the free row. The other providers are called on treg.to's keys and billed per call from your prepaid balance, so you can read a video's stats with no Google project at all.
They are what the platform is publishing at the moment of the call. YouTube itself updates public view counts on its own schedule, so two providers reading a minute apart can legitimately disagree on a fast-moving video.