rumoro
Lantern
+ sdk+ typescript− camping
Name your product
Your product, API or SDK, a competitor or the problem you solve. When the name is a common word, add words developers write with it.
DEV.to monitoring for the tutorials that mention your product
Rumoro reads every new DEV Community article every hour, finds the tutorials, comparisons and bug write-ups that name your product or competitors, and sends them to Slack, a webhook or your AI agent.
$5.80 of free credit · no card · no subscription
- Every article
Each new DEV article is read once, and all your keywords are matched against it.
- Every hour
Over a hundred articles an hour appear on DEV. One hourly read covers them all.
- Title + tags
The title, the summary and the tags are matched. The body and comments aren't read.
- Cross-posts
An article first published on a blog keeps the address of the original.
How it works
How DEV monitoring works in Rumoro
Add a keyword in the dashboard or with one API call. From the next hour on, new articles come to you.
GET /articles/latest → title · description · #tags ∋ "Lantern"- 09:00
- 10:00
- 11:00
- 12:00
Rumoro reads DEV every hour
Every new article, from where the last read stopped, matched on its title, summary and tags and scored against how you describe your company.
- Lantern SDK on a Cloudflare Worker?…89
- Our lantern-lit camping trip, in photos…2
- Tracing a Next.js app with Lantern…78
The articles worth a reply reach you
Each alert sets its own relevance bar and filters on sentiment and intent, such as praise, questions, comparisons, bug reports, churn or buying intent, then posts to Slack, Telegram, email, a webhook or your agent.
For DevRel teams
DEV monitoring for DevRel teams, and the tutorials you didn't write
Developers write about the tools they build with, and DEV is where many of those articles appear first. For developer relations, each one is a chance to thank, correct or learn.
- Tutorials built on your API, to link from your docs and share
- Articles that got something wrong, to correct before others copy them
- Comparisons and round-ups, to see where you’re listed and how you’re described
How we moved our billing webhooks to Rumoro
Tutorial · link it from the docsRumoro vs rolling your own scraper, a month in
Comparison · check the factsRumoro's Python SDK times out behind our proxy
Bug report · reply with the fixFive tools I use for social listening this year
Listed · see how you're described
DEV alerts
Four recipes for DEV.to keyword alerts
What to follow, what Rumoro matches and the alert your team gets. Pick one.
Search or monitor
DEV search, the Forem API, or monitoring
DEV has a search box and an open API, but neither tells you when a new article names you. Here is what each one leaves to you.
QuestionDEV searchBuilding on the Forem API
Rumoro
RumoroWho keeps checkingDEV searchYou, each time you searchBuilding on the Forem APIYour code, on a schedule you hostRumoroRumoro, every hour, for every keyword at once
Keyword searchDEV searchDEV's search, sorted by newest when you lookBuilding on the Forem APINone to poll. /articles/latest lists every new article and leaves the filtering to youRumoroEvery new article read once and matched against all your keywords
Busy hoursDEV searchWhatever is on the pageBuilding on the Forem APIA single page can miss articles when many arrive at onceRumoroPages are read back until they meet the last article seen
Rate limitsDEV searchNot a concern while you browseBuilding on the Forem APILimits per IP address, and an API key to manageRumoroRumoro runs the polling and stays within DEV's limits
Cross-postsDEV searchShown as DEV articlesBuilding on the Forem APIThe original address is in the data if you read itRumoroThe original blog address kept on each mention
NoiseDEV searchEvery article with the wordBuilding on the Forem APIEvery article with the wordRumoroScored 0–100 against your company, bots flagged and muted authors kept out for good
AlertsDEV searchNoneBuilding on the Forem APIPolling, storage, deduplication and alerts are yours to build and runRumoroSlack, Telegram, email digests and signed webhooks
AgentsDEV searchCopy and pasteBuilding on the Forem APIYour own MCP server on topRumoroMCP with scored, source-linked mentions from every platform
What you get
What Rumoro keeps from each DEV article
Enough to know what the article is and who wrote it before you open it, and plainly what isn't read.
The article
The title, the summary, the tags, the link, when it was published, its cover image, and its reaction and comment counts.
The author
The DEV username, name and avatar, linked to their profile, with every other article they wrote about you.
The original
When an article was first published on a blog, the address of that original, so you know where the author keeps writing.
Not read
The body and the comments. Rumoro matches what DEV shows in its feed, so a name that appears only deep in an article won't arrive.
Beyond alerts
DEV Community tracking beyond the alert
See how often DEV writes about you, get to know the authors and keep every keyword worth its cost.
Your share of voice
Track competing tools next to yours and see who DEV writes about more, week by week.
The authors behind the mentions
Each author who writes about you becomes a person with your tags, your notes and every article they published about you.
Articles that link to you
Links in a matched article's summary are kept. Filter by your domain to find the posts sending readers to your docs.
Cross-posts traced
Articles first published on a personal blog keep that address, so you can thank the author where they actually write.
Keyword health
See which keywords bring real tutorials and which mostly bring namesakes, with suggestions on what to exclude.
Needs attention
An hourly check for sudden spikes, a run of negative articles, noisy keywords or a channel that stopped delivering.
Digests for quieter keywords
One daily or weekly round-up in Slack, Telegram or email, which suits a platform where articles stay relevant for weeks.
Views, filters and export
Filter by sentiment, intent or author, save the view for your team and download it as CSV.
MCP, API, SDKs and CLI
DEV articles about you, in your agent and your code
Rumoro's MCP server gives Claude, Cursor or Codex the DEV articles that name you, scored and linked. Your agent sorts tutorials from bug reports and drafts the replies for you to check.
DEV articles praising you, with a relevance of at least 60.
curl --get 'https://api.rumoro.dev/v1/mentions' \
--header "Authorization: Bearer $RUMORO_API_KEY" \
--data-urlencode 'platform=devto' \
--data-urlencode 'minRelevance=60' \
--data-urlencode 'intent=praise'200Response · REST, SDKs and CLI
{
"data": [
{
"id": "d81c…",
"keyword": { "term": "rumoro" },
"post": {
"platform": "devto",
"url": "https://dev.to/ana_k/brand-alerts-in-discord-…",
"title": "Brand alerts in Discord with Rumoro and 40 lines of TypeScript",
"text": "Brand alerts in Discord with Rumoro and 40 lines of TypeScript\n\nA small bot that posts new mentions to a channel.\n\n#webhooks #typescript #discord"
},
"author": { "handle": "ana_k", "followers": null },
"classification": {
"relevance": 91,
"sentiment": "positive",
"intents": ["praise"],
"note": "A tutorial built on your API. Link it from your docs and thank the author."
}
}
],
"nextCursor": null
}Coverage, alerts and cost
DEV.to monitoring questions
How do I monitor DEV.to for mentions of my product?
Add your product name as a keyword. Rumoro reads every new DEV Community article every hour, matches its title, summary and tags against your keywords, scores each match for relevance, sentiment and intent, and sends the ones that matter to Slack, Telegram, email, a webhook or your AI agent.
Does the DEV.to API (Forem) have keyword search?
Not one you can monitor with. The Forem API that runs DEV lists the latest articles, newest first, and leaves the filtering to you. Rumoro reads that feed once an hour and matches all your keywords against the same articles, so another keyword costs no extra requests.
How often does Rumoro check DEV?
Every hour. Over a hundred articles an hour appear on DEV, and one hourly read covers every one of them for every keyword. Checking more often would find the same articles slightly sooner.
Will I see older DEV articles when I add a keyword?
No. DEV has no search Rumoro can run per keyword, so a new keyword matches articles published from that day on. Platforms with search, such as Reddit, Hacker News and GitHub, also bring the newest 10 mentions from the last 30 days.
Does Rumoro read the whole article and its comments?
No. It matches the title, the summary and the tags, which is what DEV shows in its feed. A product named only deep in an article's body, or only in the comments, won't arrive. Most tutorials about a tool name it in the title or tags.
How do I search DEV for articles about my product?
Use the search box on dev.to and sort the results by newest, or follow the tag pages that fit your product. Both show what's there when you look. Rumoro checks every new article for you and only sends the relevant ones.
Is there a DEV RSS feed for keywords?
DEV publishes RSS feeds per tag and per author, such as dev.to/feed/tag/webdev, but not for a keyword. Rumoro covers the keyword across every tag and scores what it finds before anything reaches you.
What happens with articles cross-posted from a blog?
They're matched like any other DEV article, and each mention keeps the address of the original post, so you can see where the author first published and keeps writing.
Why do DevRel teams monitor DEV?
Because developers write tutorials, comparisons and bug write-ups about the tools they use, usually without telling anyone at the company. Developer relations teams use them to thank authors, link good tutorials from the docs, correct the ones that went wrong and learn which features people actually build with.
Can I get DEV alerts in Slack?
Yes. Connect Slack once and each alert rule posts matching articles to a channel with the title, the author, the tags, the AI relevance score, a note on why it matters and buttons to open it, mark it handled or mute the author.
Do I need a DEV account or an API key?
No. Rumoro reads DEV with its own access. You don't connect an account or create a DEV API key, and nothing is posted in your name.
Can my AI agent read DEV mentions over MCP?
Yes. Rumoro's MCP server gives Claude, Cursor, Codex or any MCP client your DEV mentions next to every other platform, so an agent can list this month's tutorials about you and draft the replies.
Is there a free DEV monitoring tool?
Every Rumoro account starts with $5.80 of credit and no card, enough for your first keyword for a month and 100 mentions on top. After that it's $5 a keyword a month and $0.008 per match, with no subscription.
How much does DEV.to monitoring cost?
$5 per keyword a month, charged by the day, plus $0.008 per matched article, with DEV included next to every other platform the keyword listens on. There's no subscription, and a new account starts with $5.80 of credit and no card.
Learn more
More on DEV.to monitoring, MCP and the API
- Cursor MCP setupConnect Cursor, sign in once and ask about your DEV mentions in plain words.
- API referenceEvery endpoint and filter the DEV feed takes, in one OpenAPI document.
- Pricing calculatorEstimate a month from your keywords and the mentions you expect.
- Instagram monitoringThe same alerts and agent access for Instagram posts and reels that name you.
One keyword, every platform
DEV is one of 16 sources
Add a keyword once and it listens everywhere you choose, scored the same way and sent to the same alerts, API and agent.
Thank the author while the article is still new
Your first keyword is on us. $5.80 of credit, no card.