Which feeds have buyers in them.
And how to have every post judged.

Published 1 October 2026 · every feed URL fetched and checked the same day

Pick feeds where buyers complain

The most common way this goes wrong is a feed that talks about your category all day. Places like that are full of people who build what you sell, and SignalPipe correctly filters them out as sellers. Go where your buyer describes the problem instead: the community they ask for help in, the forum of the tool they want to leave, the Q&A site where people ask what to use.

Three to five well-chosen feeds beat twenty. Every feed is read on every cycle and sources rate-limit, so more feeds mostly buy more noise. Broad community feeds produce far more real leads than narrow keyword searches, which often produce none.

Feed URLs worth knowing

Replace the capitals with your own values. Each URL was fetched on 1 October 2026. Reddit serves Atom at its .rss addresses; SignalPipe reads RSS and Atom alike.

Before you start: the sites’ rules

Check that your use is covered. SignalPipe never sends anything on its own: every public reply and DM waits for your approval, and goes out from your own accounts.

1. Check a feed before you add it

preview_station over MCP, or POST /stations/preview, reads the feed, scores its fresh posts the way the scout would, and has the three-judge panel read the best-matching ones: eight by default, any number from 1 to 12. Nothing is saved. You get a verdict and the judged sample, each post kept or rejected with the judges’ stances.

curl -s https://api.signalpipe.io/stations/preview \
  -H "Authorization: Bearer $SIGNALPIPE_OPERATOR_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "product_id": "YOUR_PRODUCT_ID",
    "rss_url": "https://softwarerecs.stackexchange.com/feeds/tag/project-management",
    "sample": 8
  }'

{
  "verdict": "VIABLE",
  "explanation": "Real buyers post here. Worth adding.",
  "feed": {
    "url": "https://softwarerecs.stackexchange.com/feeds/tag/project-management",
    "read_by": "server", "http_status": 200, "entries_read": 25, "fresh": 18
  },
  "judged": 8,
  "kept": 3,
  "sample": [
    {
      "title": "Looking for a help desk for a 12-person team",
      "verdict": "kept",
      "panel": { "judges": { "skeptic": "convinced", "analyst": "convinced", "optimist": "convinced" }, "split": false }
    }
  ],
  "judgements_spent": 8
}

Add the VIABLE and MARGINAL ones. Each judged post costs one judgement, and previews are limited per day.

Reddit feeds are read on your machine, never by SignalPipe, so previewing one by rss_url over REST or remote MCP returns 409. Send its posts as entries instead: up to 50, each with a link, title, summary, author and published time. On OpenClaw, signalpipe_preview_station reads the feed on your machine and does this for you.

2. Add it as a station

add_station, or POST /stations/add, takes a name, the feed URL and a platform, which tells SignalPipe what kind of place the feed is and shapes the drafted reply:

• reddit: a subreddit feed. Drafts are written as in-thread comments.
• hn: a Hacker News feed.
• rss: any other RSS or Atom feed.

curl -s https://api.signalpipe.io/stations/add \
  -H "Authorization: Bearer $SIGNALPIPE_OPERATOR_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "product_id": "YOUR_PRODUCT_ID",
    "name": "r/smallbusiness new",
    "platform": "reddit",
    "rss_url": "https://www.reddit.com/r/smallbusiness/new/.rss"
  }'

# {"status": "ok", "id": "4b1a…", "read_by": "client"}

The reply says who will read the feed: read_by: client for Reddit, which your plugin or daemon reads, and server for feeds SignalPipe’s scout fetches itself. The URL must be http or https on a public host; anything else is refused with the reason. A fourth platform, twitter_search, reads nothing: it only routes outreach to X. The optional keyword is a note for you, not a filter. Posts are matched against your product’s anchor sentences, written in your buyers’ own words.

3. Let it run, then work the queue

Two kinds of reading, one pipeline. Feeds marked read_by: server are fetched by SignalPipe’s scout from its own servers, without credentials, every 30 minutes; for a fresh scan now, call scout_now or ask your agent, at most once every 15 minutes. Reddit feeds are marked read_by: client and are never fetched by SignalPipe: your OpenClaw plugin (signalpipe_read_feeds) or the daemon (signalpipe-daemon read) reads them on your machine and sends the entries to POST /scout/ingest. Keep one of them running, or those feeds go quiet.

Either way, each new post is scored the same way and the close calls go to the panel; one person posting the same question in several places becomes one lead. Leads that clear the gate arrive in your queue with a verdict and a drafted reply.

Approve the leads worth answering and reject the rest with a reason. The reason feeds back into how that feed is weighted the next time it is read, so a feed that keeps producing the wrong people is quietly demoted. Approved replies go out from your own accounts, by hand or through the plugin or daemon.

4. Keep the feeds that work

list_stations, or GET /stations/list, gives every feed a readout for the last two weeks: posts captured, how many reached your queue, empty or rate-limited fetches, and a plain-language verdict, such as posts arriving but none matching your product.

{
  "window_days": 14,
  "stations": [
    {
      "id": "4b1a…", "name": "r/smallbusiness new", "platform": "reddit",
      "leads_captured": 11, "surfaced": 3, "empty_fetches": 2, "rate_limited": 0,
      "verdict": "Working — 3 of 11 captured posts reached your queue."
    }
  ]
}

Pause or re-point a feed with update_station. remove_station deletes a feed that never produced a lead; one that did is switched off instead, so its history stays.

On OpenClaw, Claude Code or any MCP client

The OpenClaw plugin has the same tools with a signalpipe_ prefix: signalpipe_preview_station, signalpipe_add_station, signalpipe_list_stations, signalpipe_update_station and signalpipe_remove_station. Over remote MCP, in Claude Code, Cursor or Windsurf, the names carry no prefix. Either way, ask in plain language:

Preview https://softwarerecs.stackexchange.com/feeds/tag/project-management
for my product. If it comes back VIABLE or MARGINAL, add it as an rss station
named "Software Recommendations: project management". Then list my stations
with their health.

On OpenClaw, start with openclaw plugins install signalpipe; the install guide covers the environment variables and the first scan. For Claude Code, the Claude Code recipe connects the MCP server in one command.

Already reading the feeds yourself?

If your own reader, script or workflow already pulls the posts, you do not need stations. Send the text to POST /signal/score_batch, up to 25 posts per call, and get a verdict on each. The Reddit recipe has the code in Python, JavaScript and curl; the same call takes posts from any feed.

What it costs

One judgement is one run of the three-judge panel. A preview spends one per judged post. Once a feed is added, posts that are clearly noise, or clearly a buyer, are decided without the panel and cost nothing, so a month of judgements covers far more posts than the number suggests. Plans start at $29 a month for 3,000; see pricing.