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 comments on https://www.youtube.com/watch?v=dQw4w9WgXcQ sorted by relevance. Show me the price first, then group them into the five things people complain about.
A URL or a video id, depending on the provider. Both are one field.
Relevance surfaces the comments people upvoted. Time gets you the newest.
A thousand comments is not an answer. Ask for the themes.
Replies are nested and paginated. Top-level threads are usually enough.
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 |
|---|---|---|---|
| 97% | 1.9s | 65 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, country_code, sort_by, continuation_token, need_format | (3 calls) | 2026-07-28 | |
| $0.0015 per result | dataset_id, format, input | not yet measured | unverified | |
| $0.00188 per call | url, order | 97% (65 calls) | 2026-07-28 | |
| $0.0148 per found | videoId, cursor, languageCode, countryCode, sortBy | (1 calls) | 2026-07-28 | |
| free, your own account | part, videoId, order, maxResults, pageToken, textFormat | not yet measured | 2026-07-28 |
treg call brightdata.x.youtube-comments
Swap the id for any provider above. All 5 endpoints behind this job, with their parameters and captured responses, are on the YouTube shelf.
The people doing this job are not chasing volume, they are chasing the forty comments that matter. From ~180 Reddit and X posts in August 2026, with the vendor clusters excluded, these five are what they actually complain about.
“a video with 3,000 comments might have 40 that are actually useful to me and the rest is noise” r/claude, 3 points
What this page can do about it: The most useful document in the whole research pass. They are on version six of that filter and get about 50% agreement with their own judgment. No provider on this page fixes that, and any that claims to is selling you something: getting the comments is the cheap half.
“I find myself wanting to search youtube comments all the time. Because youtube lacks this feature (for some reason)” r/SideProject, 2 points
What this page can do about it: True, and it is the whole reason this job exists. Every provider here hands back the comments as records with author, likes and timestamps, so searching, sorting and grouping them becomes something your agent does rather than something the site has to offer.
“it would also mean 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 dropping a control channel because a third one costs more quota than they have is the clearest argument on this page. Google's route is free and rationed; the paid rows have no daily ceiling, and you can mix them, spending quota first and paying past it.
“How has youtube given me the wrong comments section on a video bro ๐” r/Quadeca, 19 points
What this page can do about it: Comment sections move: held-for-review, author-deleted and creator-hidden comments differ between two calls minutes apart, and the sort you ask for changes which arrive first. No provider here, and no comparison table, can tell you that you got all of them. Pin the sort order and record when you pulled.
“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 several jobs chained, not one call: list the channel's videos, then pull comments per video, then paginate each. Your agent can run that loop and treg.to prices every step, but it does not run the loop for you, and on a large channel the bill is the sum of the parts.
Past that you fetch the rest by parent id, so a thread with hundreds of replies is a second and third call rather than a deeper response.
Treat that as a distinct outcome; the scraping providers signal it differently, and on a per-call biller you have still paid for the attempt.
On a heavily commented video that is a materially different bill from a per-call provider, in either direction depending on how many you actually pull.
The public comment threads on a video: each comment's text, author name and channel, like count, published and updated times, and the replies underneath it. Comments are paginated, so a video with tens of thousands of them is many calls, and the order you ask for changes which ones arrive first.
Yes, by paginating. It is one call per page on every provider here, so a heavily commented video costs proportionally more. The comparison shows the per-call and per-record rates side by side.
Top-level threads come back with their first replies attached. Deeper replies are a further call per thread, which is worth knowing before you ask an agent for everything.
The comments are public and Google's own API serves them, which is the route this page recommends first. The third-party providers read the public page; you are responsible for what you do with the data, including the privacy law that applies to you.
Not in one call. List the channel's videos first, then fetch comments per video. Your agent can chain that; treg.to prices each step but does not run the loop for you.