planned
X is reserved as a direct source until a real path exists. Indexed posts arrive as web results with a domain today. Planned.
Today, use site:x.com in a web search or catch. Indexed posts arrive as web results with domain x.com. Coverage is real but thin because the web index only sees some posts. Direct X coverage is reserved until a real path exists. X is planned.
Today: posts the web index has picked up, as web results with domain x.com. Planned: direct coverage.
Through the web index for now, with site:x.com in the query.
One syntax for every source: quotes, AND, OR, NOT, site:, author:, lang:.
query
site:x.com "your product"One result, as a catch delivers it: source, author, the post, a prescore, thread context, and a suggested action your agent can act on.
Just got the email. Our social listening tool raised prices again. We pay for 10 keywords and barely use 3. Anyone know a tool that charges per use instead of per seat?
The web index sees some X posts but not all. Public posts from accounts that are indexed by search engines appear. Private accounts, posts behind login walls, and real-time conversation threads do not. This is real but thin coverage, and discatch says so rather than claiming full access.
Syften, Octolens, SnitchFeed, OpenScout, Replymer, Redmonitor, Fedica, and Twilert all have X or Twitter tool pages. This is the most saturated source in the category. discatch’s angle is not the source itself but the delivery: push to an agent, a quote before the call, and per-unit pricing instead of a monthly seat. No other tool in this set pushes to an agent or gives you a quote before the call.
Reserved means discatch does not claim direct coverage. It means the source is on the roadmap but the path to it is not cleared. For X, that path depends on API pricing and terms that are subject to change. Saying "planned" without a cleared path would be dishonest. Saying "reserved" tells an agent that it should use the web index with site:x.com today and not plan on X as a direct source until the doctor manifest says otherwise.
X is the most saturated source in this category after Reddit. Eight or more vendors have tool pages: Syften, Octolens, SnitchFeed, OpenScout, Replymer, Redmonitor, Fedica, and Twilert. None of them push to an agent. None of them give you a quote before the call runs.
Official X read access is pay-per-use and the filtered stream is enterprise-only. Every product in this category reaches X through some path. discatch says it plainly: today, indexed posts arrive through the web index with domain x.com. Direct coverage ships when a real path exists.
Today: indexed posts from X arrive as web results with domain x.com. Use site:x.com in your query. Coverage is real but thin. Planned: direct X coverage when a real path exists.
Your product on X
site:x.com "your product"Competitor complaints
site:x.com "competitor" AND (expensive OR "price increase" OR alternative)Official X read access is pay-per-use. The filtered stream, which is what you need for real-time monitoring, is enterprise-only. Every product in this category reaches X through some path. Some use the official API and pass the cost through. Some use the web index. Some scrape. discatch uses the web index today and will add a direct path when one is viable. This is an honest choice that prioritizes cost and reliability over speed.
People still search for "twitter keyword alerts" more often than "x keyword alerts." Both queries lead here. The product is the same regardless of what the platform is called. The domain in web results says x.com. Circleboom, Fedica, and Twilert all still use "Twitter" in their page titles. This is a naming transition that has not finished.
Partly. Use site:x.com in a web search or catch. Indexed posts arrive as web results with domain x.com. Coverage is real but thin. Direct X coverage is reserved until a real path exists.
Because the web index only sees some posts. discatch says so instead of claiming full coverage.
The same as any web search: one search unit per call, plus one result unit per matched item. You are searching the web index with a site: filter.
Not today. The web index lags. When direct X coverage ships, the freshness will depend on the path used.
Official read access is pay-per-use and the filtered stream is enterprise-only. discatch does not claim direct coverage until it has a real path.
No. discatch never posts on anyone’s behalf. Drafting is your agent’s job.
Syften, Octolens, SnitchFeed, OpenScout, Replymer, Redmonitor, Fedica, and Twilert all have X or Twitter tool pages. X is the most saturated source in this category after Reddit.
X results will move from web (with domain x.com) to a dedicated x source. Existing catches with site:x.com will keep working.
Name both sources in the catch. Today X goes through the web index; Bluesky is also planned. When both ship, a single catch can cover both.
X was formerly Twitter. The query "twitter keyword alerts" is common and maps to this source page. The product is the same.
Yes. Name both sources in the catch. Today X goes through the web index; Bluesky is also planned. When both ship, a single catch covers both platforms. Results carry the source field so you know which platform each came from.
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.