Eight developer feeds to start with.
Real RSS/Atom URLs, each published by the project or organization that owns it. Copy one into a feed or a chat broadcast and you are monitoring something useful in a minute. Emit does not own or operate any of these feeds.
The catalog
Every entry was fetched on , returned HTTP 200 and parsed with Emit's own feed parser. Upstream feeds can move or change; if one stops working, check its source link.
-
CPython releases
Release updateshttps://github.com/python/cpython/releases.atom -
Node.js releases
Release updateshttps://github.com/nodejs/node/releases.atom -
PostgreSQL news
Release updateshttps://www.postgresql.org/news.rss -
CISA cybersecurity advisories
Security advisorieshttps://www.cisa.gov/cybersecurity-advisories/all.xml -
Go blog
Engineering newshttps://go.dev/blog/feed.atom -
Rust blog
Engineering newshttps://blog.rust-lang.org/feed.xml -
Kubernetes blog
Engineering newshttps://kubernetes.io/feed.xml -
GitHub Changelog
Engineering newshttps://github.blog/changelog/feed/
Use the runtime releases recipe
Open the dashboard feed composer with the CPython and Node.js release feeds above already filled in as a merged feed list. Nothing is created until you press Create feed; the first check records current releases as a silent baseline. If you sign in with an emailed link, open it in the same browser you started from. Delivery setup is optional afterwards.
Route one: a complete example
This creates a feed from the Rust blog URL above, then sends its new items to Slack as one
daily digest. Replace the Slack URL with your own incoming webhook; the sink works the same
for discord, teams, telegram,
google_chat or a JSON webhook.
# 1. Create a feed from an explicit source (the API calls it a watcher)
curl -X POST https://api.rssemit.com/v1/watchers \
-H "Authorization: Bearer $EMIT_KEY" \
-H "Content-Type: application/json" \
-d '{"name": "Rust blog",
"sources": ["https://blog.rust-lang.org/feed.xml"],
"discover": false}'
# → { "id": "…", "atom_url": "https://api.rssemit.com/w/…/atom.xml", … }
# 2. Send that feed to Slack once a day, 09:00 New York time
curl -X POST https://api.rssemit.com/v1/sinks \
-H "Authorization: Bearer $EMIT_KEY" \
-H "Content-Type: application/json" \
-d '{"kind": "slack",
"url": "https://hooks.slack.com/services/T000/B000/XXXX",
"feed_url": "<atom_url from step 1>",
"schedule": "daily",
"digest_hour": 9,
"digest_tz": "America/New_York"}'
You can also point a sink straight at any catalog URL and skip step 1; create a feed when you want to merge several sources, filter with a prompt or read the result in Reader.
What to expect
- Silent baseline. The first check of a source, and the first poll of a sink, records what already exists without delivering it. A daily sink also skips its first digest boundary, so nothing arrives until something new is published after you connect. Quiet feeds stay quiet for days.
- Free: creating the feed, polling its sources, serving the Atom/JSON feed and Slack, Discord, Teams, Telegram and Google Chat sinks or JSON sinks.
- Costs credits: email sends (1 credit per recipient), prompt-based relevance filtering (1 credit per 5 items judged), summaries (1 credit per item), source discovery (25 credits) and rendered-page checks. The example above uses none of them. See pricing.
-
Two different "webhooks". A
kind: "webhook"sink is a per-feed JSON post, unsigned. The account-wide event endpoints are a separate, HMAC-signed and retried integration.