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 subscriber count, total views and video count for @MrBeast and @mkbhd, and tell me which has more views per video. Show me the price first.
Google's API resolves @handle directly. The scrapers vary; some need the UC id.
Profile and statistics are separate parts of the response. Name both.
Views per video and subscribers per video are one line, not a spreadsheet.
Your own Google connection is free and never metered.
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
ScrapeCreators at $0.00188
TikHub at $0.001
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% | 966ms | 358 calls | |
| 100% | 990ms | 10 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 | channel_id, continuation_token, language_code, country_code, need_format | 100% (10 calls) | 2026-07-28 | |
| $0.0015 per result | dataset_id, format, input | (1 calls) | 2026-07-30 | |
| $0.00188 per call | channelId, handle, url | 100% (358 calls) | 2026-07-28 | |
| free, your own account | part, mine, id, forHandle | (4 calls) | 2026-07-28 |
treg call brightdata.x.youtube-channels --query dataset_id=gd_lk538t2k2p1k3oos71 --query format=json --data '[{"url":"https://www.youtube.com/@YouTube"}]'Swap the id for any provider above. All 5 endpoints behind this job, with their parameters and captured responses, are on the YouTube shelf.
Two things stop people here, and neither is the price: how fresh the numbers are, and whether touching the API can hurt the channel they already run. From ~180 Reddit and X posts in August 2026, with the vendor clusters excluded.
“So one field in the response was stale while the other two were fresh.” r/googlecloud, 1 point
What this page can do about it: Documented day by day in that thread: lifetime viewCount frozen for over a day while subscriberCount and videoCount kept moving, inside Google's own API. Every provider on this page reads from the same well, so no comparison table can rank them on whether a number is today's. Record when you pulled and treat a flat total as suspect, not as news.
“Is there any risk that my main channel could be shadowbanned, restricted, or lose its algorithmic reach just by using the official API” r/youtube, 3 points
What this page can do about it: A fair question that almost nobody answers in writing. Reading public channel data through one of the paid providers here happens server side on a credential that has nothing to do with your creator account, so there is no account of yours in the request at all. If you use the free Google row instead, that is your connected account, by design.
“spending more api quota to start tracking a third channel from scratch” r/HiddenTrueCrimeChat, 20 points
What this page can do about it: A researcher dropped a control channel because a third one cost more quota than they had. A channel read is 1 unit, so the free cap is roughly 10,000 snapshots a day; what actually burns it is polling often. Paid rows have no daily ceiling, which is the whole difference for anything long running.
“Can I legally use YouTube channel profile pictures and public stats from the YouTube API in a collectible card game?” r/legaladvice
What this page can do about it: No comparison table can answer this and we are not going to pretend otherwise. Public and reusable are different things; storing, republishing and putting someone's avatar on a product are governed by YouTube's terms and by the law where you are. Read the terms, and take advice if money is involved.
“I want to archive everything from the videos, to the likes, view and comments on it, lives and the same for it” r/DataHoarder, 20 points
What this page can do about it: That is four jobs chained: the profile, the uploads list, per video stats, then comments. Asking Google for part=contentDetails hands you the uploads playlist id, which is the cheap way into the catalogue without spending a search. Your agent runs the chain; treg.to prices each step.
Google's API takes exactly one of mine, id or forHandle, so an @handle resolves in a single call; ScrapeCreators accepts a channel id, a handle or a URL; TikHub needs the UC channel id, so a handle costs you a lookup first.
Two providers reading the same channel will agree on the rounded figure and neither has the exact one, because the platform does not expose it.
It is the cheapest path from a channel to its catalogue by a wide margin.
The three totals a channel publishes about itself: subscribers, views across every video, and how many public videos it has. Alongside them come the profile fields: title, description, custom URL, country, keywords, banner and thumbnail. These are cumulative totals, not a time series, so measuring growth means reading them repeatedly and keeping your own history.
Not from any of these. They return the current totals, because that is all YouTube publishes. A growth curve means calling on a schedule and storing what you get.
Search for it first, then read the profile. Channel search is a separate job on this menu and returns the ids these endpoints take.
Yes. It runs on the Google account you connect, so treg.to relays the call and meters nothing. Only calls on treg.to's own provider keys are billed.
No, and no provider can. Watch time, traffic sources and audience data are visible only to the channel's owner through a connected account. Everything here is public.