Pulse
+ sdk+ api− heart
Name your project
Your package, SDK or product name, or a competitor’s. Add words that must or mustn’t appear when the name is common.
Where we listen
Where it lands
Developer tools
Rumoro searches every public repository for your project, SDK or competitors every 15 minutes and sends the issues and pull requests that need you to Slack, a webhook or your AI agent.
$5.80 of free credit · no card · no subscription
Titles and descriptions across every public repository, not only yours.
Each keyword is searched again, inside GitHub's search limit.
New issues can take a while to reach GitHub's search. Each check re-reads the last hour.
A new keyword reads back the newest 10 from the last 30 days straight away.
Notifications, search or monitoring
GitHub tells you about your own repositories and direct @mentions. Most of what developers write about your project happens somewhere else.
Activity in repositories you watch, threads you take part in and @mentions of you or your team. A bug report about your SDK in someone else's repository stays silent.
Finds issues and pull requests across public repositories when you look, with qualifiers like is:issue, is:open or repo:owner/name. It doesn't tell you when something new appears.
Searches every public repository for your keywords every 15 minutes, scores what it finds and sends new matches to Slack, Telegram, email, a webhook or your agent.
How it works
Set it up once in the dashboard or with one API call. After that, new issues come to you.
Pulse
+ sdk+ api− heart
Your package, SDK or product name, or a competitor’s. Add words that must or mustn’t appear when the name is common.
q="Pulse" created:>=… sort=created order=descPublic issues and pull requests through GitHub’s search API, re-reading the last hour so late issues aren’t missed.
Each alert sets its own relevance bar and filters on sentiment and intent, such as questions, comparisons, bug reports, churn or praise, then sends the match to Slack, Telegram, email, a webhook or your agent.
GitHub alerts
What to follow, the search it becomes and the alert your team gets. Pick one.
Search or monitor
They read the same public index. They differ in who keeps checking, how GitHub's limits are handled and what reaches you.
Search limits from GitHub’s REST API documentation.
Beyond alerts
See how your project compares, who keeps writing about it, and which keywords are worth their cost.
See how often your project comes up on GitHub compared with competing libraries, week by week.
Each GitHub user who mentions you comes with their profile, company, location and linked accounts, plus your tags and notes.
Links in matched issues and pull requests are kept, so you can see which ones point to your docs, examples or pricing.
Skip your own repositories, where GitHub already notifies you, or any noisy ones, for the whole workspace.
Look at bug reports and questions on their own, or only at pull requests that add or replace your project.
Issues opened by bots and automation are flagged, so you can keep them out of alerts with one filter.
See which keywords bring real issues and which mostly bring noise, with suggestions on what to exclude.
An hourly check for sudden spikes, a run of negative issues, noisy keywords or a channel that stopped delivering.
MCP, API, SDKs and CLI
Rumoro's MCP server gives Claude, Cursor or Codex the public issues and pull requests that mention you, with scores and links. Your agent groups them and drafts replies for you to check.
Bug reports on GitHub with a relevance of at least 60.
curl --get 'https://api.rumoro.dev/v1/mentions' \
--header "Authorization: Bearer $RUMORO_API_KEY" \
--data-urlencode 'platform=github' \
--data-urlencode 'minRelevance=60' \
--data-urlencode 'intent=bug_report'200Response · REST, SDKs and CLI
{
"data": [
{
"id": "e7a0…",
"keyword": { "term": "tidequeue" },
"post": {
"platform": "github",
"url": "https://github.com/acme/billing-service/issues/482",
"text": "tidequeue worker stops processing after a Redis reconnect"
},
"author": { "handle": "ttal", "followers": null },
"classification": {
"relevance": 90,
"sentiment": "negative",
"intents": ["bug_report"],
"note": "A user hit a reconnect bug in their own service. A maintainer comment with a fix or workaround helps."
}
}
],
"nextCursor": null
}Coverage, alerts and cost
Add your project, package or SDK name as a keyword. Rumoro searches the titles and descriptions of public issues and pull requests every 15 minutes, scores each match for relevance, sentiment and intent, and sends the ones you care about to Slack, Telegram, email, a webhook or your AI agent. Lower-volume keywords can arrive as a daily digest instead.
Yes. The search covers every public repository, so a bug report about your SDK filed in a customer's repository reaches you with the repository, the author and a link to the issue.
No. Rumoro searches GitHub with its own access. You don't connect a GitHub account or create a token, and nothing is posted in your name.
GitHub notifies you about repositories you watch, threads you take part in and @mentions of you or your team. When someone names your project in their own repository without tagging you, nothing reaches you. Rumoro searches for the name itself.
GitHub search and its advanced search page find them when you look. In GitHub's search syntax, put the name in quotes and add qualifiers such as is:issue, is:open or sort:created-desc to see the newest first. Rumoro runs that search for you every 15 minutes and only sends what's new and relevant.
No. Rumoro matches the titles and descriptions of public issues and pull requests. Comments under them and code in repositories aren't covered, so a mention that only appears in a reply won't arrive.
Each keyword is searched every 15 minutes. A new issue can take a while to show up in GitHub's search, so each check re-reads the last hour and late issues still arrive, once. A new keyword also reads back the newest 10 from the last 30 days.
Yes. GitHub's own Slack app posts activity from repositories you subscribe to. Rumoro posts something different, the issues and pull requests anywhere on GitHub that mention your project, with the repository, the AI relevance score, a note on why it matters and buttons to open it, mark it handled or mute the author.
The GitHub search API allows 30 requests a minute with a token and 10 without, and returns at most 1,000 results for one search. If you build your own polling, every term you watch shares that budget. Rumoro spaces its searches to stay inside it.
Not in the sense of GitHub's own MCP server, which lets an AI tool work in repositories you have access to. Rumoro's MCP server gives Claude, Cursor or Codex the public issues and pull requests that mention you, scored and linked, next to every other platform.
Yes. Add them to the excluded repositories in your workspace settings and their issues and pull requests are dropped before they're stored or billed. Most teams leave out repositories where GitHub already notifies them.
Each mention is checked for whether it reads as machine-made, such as a bot account or a scheduled post, and flagged. Filter the feed or an alert to people only and bot activity stays out of the way.
No. Only public repositories are searched.
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.
$5 per keyword a month, charged by the day, plus $0.008 per matched issue or pull request. There's no subscription. You top up a balance, and a new account starts with $5.80 of credit and no card.
Learn more
One keyword, every platform
Add a keyword once and it listens everywhere you choose, scored the same way and sent to the same alerts, API and agent.
Your first keyword is on us. $5.80 of credit, no card.