planned
Video titles, descriptions, and comments through the official Data API. Planned.
When YouTube ships as a source, discatch will read video titles, descriptions, and comments through the official Data API. Comment reads are quota-expensive and the quote reflects it honestly. Videos matching your query and comments mentioning your product are separate results, each with view and comment counts that feed the prescore. YouTube is planned.
Videos whose title or description match, and comments that mention you, with view and comment counts.
The official Data API within its daily quota. Video search maps through; comments are matched locally.
One syntax for every source: quotes, AND, OR, NOT, site:, author:, lang:.
query
"your product" review OR tutorialOne result, as a catch delivers it: source, author, the post, a prescore, thread context, and a suggested action your agent can act on.
In this video I compare your-product, Octolens, and Syften. your-product was the only one where I could set up alerts from my terminal without logging into a dashboard.
Video search finds reviews, tutorials, and demos by title and description. Comment reads find mentions buried in discussions. Both are results with different prescores. A video result carries view and comment counts; a comment result carries the parent video URL. The prescore weights engagement differently for each.
The YouTube Data API quota is a hard daily limit that resets at midnight Pacific. discatch tracks usage across all catches on the account and prices remaining quota into each quote. If the quota is tight, the quote is higher. If the quota is gone, the call is refused with source_unavailable. This is a real constraint that discatch prices honestly rather than hiding behind a "fair use" clause.
A YouTube review ranks in YouTube search and sometimes in Google search. A mention in a review with 10,000 views is a durable surface, not a one-time conversation. Catching it the day it publishes lets you comment with corrections if needed, thank the creator, or share it with your team. Reviews that get the pricing wrong or compare against a discontinued product version are the ones worth catching early.
The "monitor YouTube comments" query is vendor-heavy: Brand24, Awario, Octolens, MediaWatcher, and Redmonitor all have tool pages. On the "YouTube keyword alerts" phrasing, a labnol.org Google Script tutorial ranks number one, followed by vidIQ (a creator tool), Syften, and Mentionkit. None of these push to an agent. The Data API quota is the honest constraint, and discatch says so.
YouTube is planned. No results arrive from YouTube today. Some YouTube video pages may appear as web results if the index has picked them up, but comment content does not appear in web results. When YouTube ships, discatch will use the Data API to search videos and read comments, pricing the quota into the quote.
Reviews and tutorials
"your product" review OR tutorialCompetitor demos
"competitor" demo OR walkthrough OR "how to use"Video titles and descriptions catch reviews and tutorials. But the real mention surface on YouTube is comments. Someone watches a competitor review and asks in the comments whether your product does the same thing. Someone watches your tutorial and reports a bug. Comment reads are quota-expensive on the Data API, and discatch prices that honestly into the quote. The alternative is missing the comments entirely, which is what most web-index-based tools do.
The YouTube Data API gives 10,000 units per day. A video search costs 100 units. A comment list costs 1 unit per call but returns 20 comments. For a catch that watches 10 queries at 1-hour intervals, the daily cost is about 2,400 units for search plus comment reads. This leaves room for other queries. discatch manages the quota across all catches on the account and prices it into the quote so you never run out silently.
The honest constraint: if your account runs many YouTube catches at tight intervals, the quota runs out. The quote tells you before the call runs. If the quota is exhausted, the call returns source_unavailable with a next_action that says when the quota resets.
No. YouTube is planned. It is behind the same gate as the other planned sources.
Planned, yes. Comment reads are quota-expensive and priced accordingly. The quote tells you the cost before the call runs.
More than free sources because the Data API has a daily quota and comment reads consume it quickly. The quote reflects this honestly.
Planned, yes. Use the channel name or ID in your query to narrow results to one channel.
Not in the initial plan. Titles, descriptions, and comments are covered. Transcript analysis is post-v1.
As fresh as the Data API indexes a video. New videos typically appear within minutes. Comments may lag depending on quota.
Not directly. Some YouTube pages may appear as web results if the index has picked them up, but comment content does not appear in web results.
Brand24 has a blog guide. Awario has /youtube/. Octolens, MediaWatcher, and Redmonitor have tool pages on the "monitor" phrasing. Syften and Mentionkit have pages on the "alerts" phrasing.
The Data API gives 10,000 units per day. Video search costs 100 units per call. Comment reads cost 1 unit each but add up fast. discatch prices quota into the quote so you know the cost before the call runs.
No. YouTube uses the Data API, not a firehose. The catch interval determines how often discatch checks.
Yes. Name multiple sources in the catch. A catch on your product name across youtube, hackernews, and web would find reviews, HN threads, and blog posts all delivered to the same destination.
Last reviewed by Parsa Khazaeepoul, founder, dcouple. Facts from docs/data-sources.md and docs/coverage-matrix.md; status from docs/api.md; the search landscape from docs/seo/keyword-map.md.