Tools/zhuyansen/new-term-radar

new-term-radar

Daily radar for new AI terms: names of new models, products and repos, caught on X, Hugging Face, GitHub and sitemaps before keyword tools list them.

1.7k ★+739/wkemergingPythonMIT License →new this week

The Lens

By Erik Loyd, SaaS CEO and former COO/CFO of an AWS Premier Partner.

Updated Oct 2026

new-term-radar catches the names of new AI models, products and repos the day they surface, before keyword tools list them. It reads X accounts you pick, Hugging Face trending, fast-rising GitHub repos and AI directory sitemaps, then a small model filters out common words. Built for SEO sites, newsletters and directories. The code is MIT.

Setup is a clone, a config file, one API key and python -m radar daily. A bundled GitHub Actions workflow runs it on a schedule. The three agent skills and MCP server are wrappers around that CLI.

The code is free; the data isn't. X posts, Google Trends, search volumes and the judging model all run through AIsa, a pay-per-call reseller, and the README estimates about $15 a month on the example config. Without the key you get Hugging Face, GitHub and sitemaps, unsorted. Solo and small teams doing new-term SEO: worth $15. Larger teams on Semrush or Exploding Topics: this finds terms earlier, not instead.

The catch: the README's AIsa links carry the author's referral code (disclosed), and your pipeline depends on a reseller keeping X and Google feeds alive. One signal is already broken upstream. Hit rates are unproven; the author says so.

Free vs Self-Hosted vs Paid

fully free

Free: All code is MIT: the CLI, the GitHub Actions workflow, three agent skills and the MCP server. Without any key the free signals still run (Hugging Face trending, GitHub breakouts, sitemaps, and Search Console with your own Google token), but nothing judges which terms are names, so the report is unsorted.

Self-hosted: Python 3.10+, standard library only (the MCP server needs the mcp package, email needs markdown). Runs from cron or the bundled Actions workflow, which is off until you set RADAR_ENABLED. State lives in a local SQLite directory. Optional Resend key for emailed reports.

Paid: No paid tier from the project, but the useful signals need an AIsa key, billed per call. The README's October 2026 figures: X reads $0.003 per account per run, the keyword table about $0.18 a day for 5 names, new-site queries about $0.13 each weekly; about $15 a month total with the example config (35 X accounts read three times a day). An optional GoAnyAPI key adds about $0.07 a day. TrustMRR revenue data needs its own key and its terms forbid republishing.

Free code, but the signals worth having run through AIsa at roughly $15 a month on the example config; cut the X account list to cut the bill.

What to do by team size

Solo
free code plus about $15/month of AIsa calls if new-term SEO is your business
Small team
same setup; one shared config and Actions schedule covers the team
Medium team
run it alongside Semrush or Exploding Topics as an early-warning feed
Large team
early-warning feed only; validate hit rates on your own data first
Self-hosting ops:moderate

Get tools like this every Wednesday

One featured tool, three on the radar. No fluff.

Score
68/100 · B
Adoption13/30
Maintenance25/25
Community5/20
License15/15
Analysis10/10

A low score is not a verdict on quality. Young and niche tools start low by design. How we calculate scores

License: MIT License

Use freely, including commercial. Just keep the license.

Commercial use: ✓ Yes

About

Owner
JasonZhu (User)
Stars
1,719
Forks
533

Explore Further

More tools in the directory