Describe it once. Never hunt for it again.
Write what you want to follow in plain language — "vintage synthesizer restorations and new Eurorack module releases" — and emit builds the feed: it discovers matching sources, watches them on your cadence, scores every new item against your prompt, and emits only what clears your bar. The output is a durable, standards-compliant RSS/Atom feed. Read it anywhere. Pipe it anywhere.
Feeds people actually run
- "Recall notices and safety bulletins for the equipment we operate" → a compliance email digest.
- "New self-hosted app releases and breaking changes in the ones we run" → one RSS feed in the reader you already use.
- "City planning agendas and zoning notices for our neighborhood" → an email alert the day they post.
- "Security advisories affecting Postgres, Redis, or nginx" → straight into the on-call Slack channel.
- "Competitor pricing or packaging changes" → filtered from their blogs and changelogs, summarized, emailed Monday morning.
Each of these is one API call — and each ends in a plain RSS feed URL, so it also works with every reader, dashboard, and automation tool that already speaks RSS.
The sources are yours to see
Every feed shows you exactly what it watches and why — each source carries its discovery rationale, last-check status, and how many items it has actually contributed. Prune what doesn't earn its keep, add sites by URL (pages without feeds are watched too), and re-run discovery when your prompt evolves. No black box.
The filter shows its work
Every item gets a relevance score and a one-line reason, carried on the feed itself. Filtered-out items stay in an audit view — when you wonder "why didn't I see X," the answer is one click away. Tap more like this or less like this and the threshold tunes itself. Borderline items get their full page fetched and re-judged, not guessed at from a headline.
Already know your sources? Skip discovery.
The same primitive filters feeds you already have: paste your feed URLs, add a prompt, get one merged, de-duplicated, filtered feed back. The same story syndicated by five outlets collapses to one item. Turn on summaries and every item arrives pre-digested.
One call to make it a newsletter
curl -X POST https://api.rssemit.com/v1/watchers \
-H "Authorization: Bearer $EMIT_KEY" \
-d '{"prompt": "security advisories affecting postgres, redis, or nginx"}'
# → { "atom_url": "https://api.rssemit.com/w/wf_…/atom.xml", … }
curl -X POST https://api.rssemit.com/v1/watchers/$ID/pipe \
-H "Authorization: Bearer $EMIT_KEY" \
-d '{"from_email": "digest@yourdomain.dev", "schedule": "daily"}'
# → a daily email digest of everything the feed emits
The output is just a standard feed, so everything emit already does — scheduling, templates,
delivery from your own domain — works on it unchanged. (In the API these are
watcher objects — hence /v1/watchers.) So does everything else
that speaks RSS: your reader, n8n, Zapier, a Slack channel via a
chat broadcast.
Pricing
Feeds meter the same prepaid balance as emails: 1 credit per 5 items the filter judges, 1 credit per item summarized ($1.60 per 1,000 credits). Polling and the output feed are free — and the feed is never gated, because a platform that traps your data isn't one you can trust with your attention.