New Term Radar

MCP地图位置

提供方 未标注

地图位置 stdio · 本地进程 未标注 社区 / 第三方 Claude DesktopClaudeCursorVS Code
查看接入方式

在关键词工具收录之前,捕捉X、Hugging Face、GitHub和网站地图上新增的AI模型、产品和仓库名称,并评估每个名称背后的搜索词规模。

一句话选型结论

按资料字段整理

New Term Radar 属于地图位置类 MCP 服务器,stdio · 本地进程,鉴权方式未标注,可直接接入 Claude Desktop、Claude、Cursor 等,有可直接执行的安装命令。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

分类地图位置 传输方式stdio · 本地进程 鉴权未标注 部署方式本地部署
GitHub 星标 未标注 仓库热度,无公开仓库时显示未标注
工具数 未标注 暴露给模型的工具数量
资源 / 提示词 0 / 0 资源与提示词模板数量
维护方 社区 / 第三方 核验等级 仅资料核对

工具与能力

地图位置
数量来自来源目录的标注,具体工具清单以官方文档为准
工具数量未标注暴露给模型可调用的工具个数
资源数量0可读取的资源条目
提示词数量0内置提示词模板数量

能力标签

支持客户端

适用场景

营销

安装与配置

stdio · 本地进程 未标注
客户端在本机拉起子进程,数据不出本机
uvx

这条命令只是入口,具体启动参数请按官方文档补齐,不要直接照搬到别的服务器。

  1. 1
    准备运行环境

    stdio 服务在本地起进程,需要先装好 Node.js 等运行时,再按安装命令拉取依赖。

  2. 2
    安装服务

    复制上面的安装命令执行;命令里带占位符的位置,换成自己的密钥或路径。

  3. 3
    写入客户端配置

    在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,让新配置生效。

  4. 4
    验证是否可用

    连接成功后随便调一个只读工具,确认能返回结果,再接入正式流程。

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
地址与路线

查地址、算路线、找附近地点。

位置检索

按区域筛门店、站点与设施。

地理数据

拉取经纬度、行政区等地理信息。

选择建议

选之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 有现成的安装命令,不用自己找入口,照着跑就能起服务。
  • 已适配 Claude Desktop、Claude、Cursor,换客户端不用重新研究配置。

先想清楚的地方

  • stdio 方式要求本地装好运行时(如 Node.js),换机器要重新装一遍。
  • 资料没标注工具数量,实际能力要装好后确认。
  • 版本更新与行为细节以官方仓库为准。

更适合

  • 需要在地图位置场景里让模型直接调用外部能力的人。
  • 已经在用 Claude Desktop、Claude 的用户,接入路径最短。
  • 想先快速试一下、能接受在本地或自有环境跑服务的人。

不太适合

  • 完全不想在本地装环境的人。
  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
New Term Radar当前 未标注 stdio · 本地进程 本地部署 有 2026-11-20
MCP Server C2f246e3 20 stdio · 本地进程 本地部署 有 2026-05-17
OpenStreetMap MCP Server 12 stdio · 本地进程 本地部署 有 2026-05-18
Baidu Maps 10 stdio · 本地进程 本地部署 有 2026-05-17
Google Maps (google-maps-aa2563d3) 7 未标注 未标注 无 2026-05-17
generative-ai 未标注 stdio · 本地进程 本地部署 有 2026-04-17

服务器档案

地图位置
字段来自项目仓库与公开索引,中文说明由本站标注
提供方未标注上游标注的维护方 未标注
分类地图位置本站按上游分类展示
连接方式stdio · 本地进程客户端在本机拉起子进程,数据不出本机
鉴权方式未标注远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时未标注 · 未标注本地安装时用到的包标识与运行时
部署类型本地部署上游给出的部署形态
最近核验2026-11-20上游最后核验时间

详细介绍

50.6 KB
来自项目仓库与上游目录的原文,未做删改

new-term-radar

Catch the names AI people are about to search for, the day they appear, before keyword tools list them.

⭐ 700+ stars on its first day, 1,000 in just over three · on PyPI, the official MCP Registry, Cursor Directory, LobeHub, Tessl, ClawHub and skills.sh

A daily report of the names that are starting to surge in AI: new models, products, tools and repos, caught where they are said first, before they show up in keyword tools.

Built for people who make pages, posts or products around new terms: SEO for AI tool sites, newsletters, directories, anyone who wants to know about "Strata" or "Seedance" the day it appears and not two weeks later.

Why

A new name leaves a trail, in this order:

  1. A lab or a well-followed account says it on X; a model enters Hugging Face's trending list.
  2. One GitHub repo takes off on its own.
  3. Directories and competitors add pages for it; someone registers a domain for it and the site starts to rank.
  4. Your own site gets its first search impressions for it.
  5. Google Trends shows the curve, days or weeks later.

Keyword tools read step 5. This radar reads steps 1 to 4 every day and uses step 5 only to check itself.

One example it was built around: Niko1221/Strata was created on 2026-09-24 and had 7,700 stars nine days later. People were searching "niko strata" from 9/26, while no second repo carried the name and no keyword tool listed it. A single repo gaining 800 stars a day is the whole signal, and it is public.

What it reads

Purple, tagged NEW: what 0.6.0 added. On the keyword table: word age, markets, page-one shape, the twelve months, your own rank, what else holds page one (threads, an AI overview) and the exact-match .com. The first words ③'s new sites rank for, what ChatGPT recommends for ⑦'s asks, three more payment platforms and the builders on ⑧, ⑨ just listed, ⑩ money and the evidence beside the names. All of it is in CHANGELOG.md.

Signal What it catches Needs Cost
① X Names the accounts in your list used for the first time in 60 days AIsa key $0.003 per account per run
① Hugging Face Models and Spaces (the demos people try) new to the trending top 50; quantised copies and a model's own demo grouped under the base name nothing free
② GitHub breakout A repo under 14 days old averaging 200+ stars a day, or +400 since yesterday; adds the search variants people use ("niko strata") nothing (a GitHub token raises the rate limit) free
③ Sitemaps Words that several new URLs on a site share and its older URLs rarely carried. The example config watches eight AI tool directories (toolify, aixploria, ai-bot.cn, opentools, dang.ai, clipfly, aitoptools, futurepedia) and four MCP and skill directories the sitemaps you list free
③ New sites Domains registered and first indexed in the last 90 days that already rank for 20+ keywords, each new one with the first words it ranks for in Google's top 20, in any country: searches a site that new already reached AIsa key about $0.13 per query, weekly; about $0.013 a new site for its words
⑦ Asks What people ask for on Reddit ("is there an AI tool that…", twelve phrasings), X, Stack Exchange (Software Recommendations and three more) and Freelancer.com: a model keeps the requests and complaints an AI tool could answer and writes each job as people would search it; jobs with searches get the page-one check AIsa key about $0.12 a week, plus a few cents for X
⑧ Sellers Sites that just put up their first payment link (Stripe Payment Links, Polar, Lemon Squeezy, Gumroad, Creem, Paddle, Dodo Payments, Waffo Pancake), from the public link graph with the day each site first linked; new pages of old sellers, platform pages, forums and one link shared by several new sites (a network's) left out; the site's own description goes to the keyword table, and with GoAnyAPI its visits, its domain's registration and where its visitors come from (the AI share) AIsa key; GoAnyAPI optional about $0.50 a week
⑧b Builders Sites just built with Lovable or v0 and newsletters just started on beehiiv, read off their badges; only the software among them becomes a lead AIsa key about $0.15 a week
⑨ Just listed New on Product Hunt, Show HN, OpenRouter, Civitai, the App Store's top-grossing charts and awesome lists (free); weekly, the pages Google indexed under Figma plugins, There's An AI For That and the Chrome Web Store, trending searches on Douyin, TikTok and Reddit, and rising searches next to root words ("ai generator") nothing for the free lists; AIsa and GoAnyAPI keys for the rest free; about $0.02 a path, $0.001 a trending list, 6 GoAnyAPI credits a root word
⑩ Money The other sites on a paying tool site's AdSense account (its owner's other niches), and the advertisers new on your own terms (Google Ads Transparency) GoAnyAPI key 3 credits a site each way, 4 a term; weekly
Beside the names For the day's strongest new names: new domains carrying the name (whois, or crt.sh certificates), Wikipedia views, what Google knows it as, Discord servers; for paying products, the "alternative", "vs", "free", "pricing" and "review" searches AIsa key; GoAnyAPI for Discord about $0.12 a name read by whois, $0.09 for the searches
⑥ Revenue Products people pay for, from TrustMRR's verified revenue: the fastest growing ($500+ in 30 days) and the newest listings; one at $0 last time and earning now is called out first. Its own description goes to the keyword table as evidence TrustMRR key free, 6 requests, weekly
④ Search Console Queries your site got impressions for, for the first time (fresh data) your own Google token free
⑤ Review Each lead checked in DataForSEO Trends 14 days later, against its own baseline; hit rate and days ahead per signal AIsa key $0.0012 per search variant
Keyword table For the day's new names: the generic search terms behind them (what people do with the new thing), each sized, checked for room on page one, and given a decision AIsa key; GoAnyAPI key optional about $0.18 a day for 5 names, $0.30 with GoAnyAPI
Name judge A small model scores every term: the name of one specific thing, or a common word? AIsa key a fraction of a cent per run

Prices are what AIsa charged in October 2026. With the example config (35 X accounts read three times a day, the keyword table for 5 names a day) a month costs about $15: $10 for the X reads, $5 for the keyword table. Read fewer accounts, or read them once a day, and it drops in proportion.

The keyword table

A name is half of what you need. "SynthID Detector" has a short life as a keyword and belongs to Google; the job it does, "ai image detector", is what people keep searching, and nobody owns it. Each day the radar reads the new names once more and writes one table with both:```
| Keyword | Type | Behind | New? | Est. searches/day | Started rising | Peak vs gpts | Peak day | Last 7 days vs the 7 before | Now | First searched | Markets (searches/KD) | Page one | Page-one shape | Decision |
| photocraft 🖼 | name | — | yes | 12747 | 2026-10-05 | 97 vs 3.1 | 2026-10-09 | — | still rising | 2026-10-04 🆕 | best US · US 110/0 · DE 20/0 · FR 20/0 · JP 10/31 | — | beatable · 1 home / 6 inner · 2 platform · exact title ×6 | prioritize |
| ai image detector 🖼 | generic | synthid detector | no | 2537 | — | 87 vs 31.6 | 2026-10-04 | ×1.2 | flat | 2023-02-19 | best US · US 74k/37 · DE 3.6k/48 · FR 2.9k/47 · JP 720/31 | — | — | watch |
| photoshop alternative ⚠ | generic | photocraft | no | 244 | — | 61 vs 61.7 | 2026-10-08 | ×1.8 | flat | — | — | — | — | skip |


(a real run, 2026-10-12, shortened; the Page one column came later, and First searched, Markets and Page-one shape in 0.6.0, from a run of 2026-10-18, see below. 0.6.0 also adds a `12 months` column after `Now` and an action after the decision, `→ update yours`, `→ improve yours` or `→ new page`: 10 to 13 below.)

How it is made (`radar/usecases.py`):

1. **Evidence**: the most-liked posts that mention the name (X advanced search) and, for a repository, its README.
2. **Phrases**: a model reads the evidence and writes the keyword an ordinary person would type for each job it sees people doing, with a quote that backs it. A phrase built on another product's name ("photoshop alternative") is kept and marked ⚠: demand often hangs on the incumbent, and whether to use someone's brand is your call.
   With a GoAnyAPI key (optional, below) the radar also takes **Google Trends' related queries** for the name: what people really searched together with it. For SynthID Detector that gave "ai photo detector", "google ai detector" and "ai detector"; these rows carry 🔎. Queries that hold the name are listed as its long-tails ("photocraft download", "nano banana 2.1 vs pro"). Queries that are themselves the names of other rising things ("gpt image 2.5" beside "nano banana 2.1") are kept as leads of their own.
3. **Screen**: a second call scores how well the name answers each phrase, marks brands, and spots the names of other things; the loosely related ones are dropped. For Claude Haiku 5.5 it dropped all six proposed ("ai coding assistant", "github copilot alternative"); for SynthID Detector it kept all five.
4. **Volume**: Google Ads monthly searches for the rest, one batch call. Phrases under `min_volume` are dropped; most are.
5. **Trends**, twice per row: the term alone gives the shape (new or not, the day it started rising, the peak, the last week against the week before, what it is doing now); the term beside a benchmark keyword (`gpts` by default) gives the size.
6. **Page one**, for the rows that would be acted on (eight at most): Google's first page (about $0.002 a keyword), the rating of each site on it (GoAnyAPI, $0.002 a site, kept 30 days) and the keyword difficulty ($0.012 a call). With a GoAnyAPI key also who already builds for the term and who pays for it: the pages Google holds with it in the title from the last month (`pages built`), the **KGR** (`KGR = pages built / monthly searches`: `< 0.25` great, `<= 1.0` watch, `> 1.0` skip) and the domains running Google ads on it (`advertisers`, from Ads transparency), $0.008 a row. `open` = three or more of the ten results sit on sites rated under 30, or difficulty under 20; `crowded` = none does and difficulty is 40 or more; `mixed` in between. Under the table it names the weakest site on page one, where a new page can get in, and what kinds of pages hold it (tools, lists, articles, videos, forums). Ads on the page mean someone pays for that click. Recorded only, in report.json as `page_age` and not used in any decision yet: how old the sites on page one are (each domain's registration, from RDAP, free) and which results entered the top 10 since the reading before, to check later whether a page one with young sites on it is one a new site gets onto.

7. **Word age**, for the prioritize and watch rows: the term's Trends interest over five years (one point a week); the first week with any interest is `First searched`, and 🆕 marks a term first searched in the last 180 days. A new term's page one is read one step easier (crowded → mixed, mixed → open): difficulty scores and site ratings are made from pages written for something else and lag a word nobody searched half a year ago. The week still running and Trends' unsettled last two days are left out, so a "0, 100" tail cannot make an old word look new. One Trends task a row, $0.0012. A term made of words people searched before ("nano banana" reads a little interest in 2021) is dated by those older searches.
8. **Markets**, for the same rows: Google Ads monthly searches in each market of `markets.codes` (US, DE, FR, JP by default; all languages) and, with `difficulty` on, the keyword difficulty there, in one compact cell: `best DE · US 5k/50 · DE 900/5 · FR 300 · JP 0 · top Germany`. `best` = the most searches per point of difficulty when every market with searches has a difficulty, else the most searches. `top` = the country where Trends interest is highest, among the major markets (Trends measures a share of local searches, and on its own puts Sint Maarten first). About $0.41 a run with the defaults (a $0.09 volume call per market, about $0.012 a difficulty call), plus $0.0024 a row for the top region.
9. **Page-one shape**, for the prioritized rows: the live top ten (US / en / desktop by default; the page-one check's own results are reused, so it usually costs nothing extra, otherwise about $0.002 a term) read as homepages against inner pages, results on high-authority platforms (`serp_shape.platforms`: github.com, medium.com, sites.google.com, `*.github.io`, reddit.com, youtube.com, wikipedia.org) and titles that hold the keyword. `platform-held` = half or more on platforms; `beatable` = mostly inner pages and no exact-match homepage (a homepage titled with the term, or whose domain spells it); `contested` otherwise. Under the table it lists the URL and title of #1 and #2.

Each of the three has `"enabled": false` in its config block to turn it off. On 2026-10-18, for "photocraft" (prioritize) and "ai image detector" (watch), they read: first searched 2026-10-04 🆕 and 2023-02-19; best market US for both (74k searches and KD 37 for "ai image detector"); page one of "photocraft" `beatable · 1 home / 6 inner · 2 platform · exact title ×6`, held at #1 by the GitHub repository. The run cost $0.42.

Four more readings came in 0.6.0 too. None of them buys anything: they read what the volume call and the page-one check already brought back, your own Search Console, and the .com registry.

10. **12 months** (`year_curve`), every row with Google Ads data: the volume call already carries each phrase's last twelve months. The column draws them as bars on the term's own scale from zero and adds a word: `new since` (barely searched a year ago), `peaked` (a burst past its top: twice its median month or more, at half of it or less now), `falling`, `rising` (the last three months against the three before, ±30%) or `steady`; under 50 searches in its best month it says `few searches`, since Google Ads rounds small volumes. The newest month is one to two months behind. On 2026-10-20 "claude skills" read `peaked 2026-03, now -80%` (90,500 a month at the top, 18,100 in 2026-09), "best claude skills" `new since 2026-01 · falling, -47% in 6 mo`, and "skill md" `steady`.
11. **Your rank** (`yours`), for the prioritize and watch rows: your sites (`yours.domains`, else the domain of the Search Console property in `gsc.site`) looked for in the page-one check's ten results and, with `gsc` set, in Search Console (average position, impressions and clicks for the exact query over 28 days, one call for all rows). The decision cell then says what to do: `→ update yours` (on page one by either), `→ improve yours` (a Search Console average of 11 to 30), `→ new page` (not found, or further down), and your pages are listed under the table. A rising term you already rank for is an update, not a new page. On 2026-10-20 one of our sites showed for one term at an average of 23.5 (improve that page) and for another at 89 with one impression, on its homepage (a new page).
12. **What else holds page one**, from the page-one check: its cell now names an AI overview, an answer box, a forums block, videos or news, and under the table come the forum threads on page one, best-of searches first: an answer there reaches the people searching. When Google shows an AI summary, people click a result about half as often (Pew Research Center, 2025: on 8% of visits against 15%). All five "claude skills" terms read on 2026-10-20 had an AI overview.
13. **Exact-match .com** (`dot_com`), for the prioritized rows, names first: the joined and hyphenated forms asked of the registry's RDAP (Verisign), free. Not registered is not always the usual price: registrars hold some names back or sell them as premium. Of the ten forms of five "claude skills" terms, one was free on 2026-10-20.

Each has `"enabled"` in its own config block; the page-one marks come with the page-one check. On 2026-10-20 five terms cost $0.11 in all, which was the volume call and the page-one check.

Searches a day are estimates. A generic term's come from its own Google Ads volume, moved to today along its own Trends curve. The benchmark is then sized from those terms, and a name, which has no volume data yet, is sized against the benchmark.

Decision: **prioritize** = rose in the last 30 days, still up, at least `min_daily` searches a day. **watch** = rose but smaller, too early to read, or flat with steady demand of that size. **skip** = fading, or flat and small. A `prioritize` whose page one is `crowded` becomes `watch ↓`: still rising, but page one belongs to strong sites. In a name's first week page one is still forming (news, the maker's own pages); the second reading three days later is the one to trust.

Marks: 🎬 video, 🎙 voice, 🖼 image says what the thing makes, the usual order of what visitors pay for (video > voice > image > text); leads of equal standing are sorted by it. ⚡ = a post with 1,000 or more likes walks through a manual workflow or rides a trend: a one-click tool nobody has built yet. Both come from keyword rules over the lead's own words and posts; on six known names (Nano Banana, Veo 3.1, Seedance 2.5, Claude Opus 5.5, ElevenLabs v4, Qwen Image 2.1) the format came out right for all six and ⚡ fired once, on a widely shared Opus 5.5 + Blender + Unreal walkthrough. Read the posts before acting on a mark.

Each name is read twice, the day it appears and three days later, because on announcement day the posts are announcements and no use shows yet. The generic terms are kept as leads and reviewed after 14 days like the names.

What to expect from it, from the first eight names we ran it on:

- **The names rose; most generic terms did not, within five days.** PhotoCraft, Claude Haiku 5.5 and SynthID Detector all climbed clearly. Of the generic terms behind them, one moved: "photoshop alternative" ran about 80% above its level in the US for five days after PhotoCraft appeared. The worldwide daily series the table reads showed almost nothing of it (2, 1, 1, 2, 4, 2); a US daily series from another source showed it plainly. So a flat reading from the worldwide series does not prove a term did not move. With a GoAnyAPI key the bigger rows are read from the one-country series instead, where a rise is 1.5 times the earlier level held for three days; the same run then shows "photoshop alternative" as `still rising (US)`.
- The table's dependable use today is to tell you **which existing demand a new thing serves and how big it is** ("ai image detector", about 2,500 searches a day). Whether generic terms follow the names is what the 14-day review will show, and we have no result yet.
- For pure model releases (Claude Haiku 5.5, Nano Banana 2.1) the evidence was announcements and benchmarks, and the phrases proposed were weak ("ai coding assistant"). It works better for products and repositories that do one job.
- **The worldwide Trends series' last two days are not settled.** For unrelated terms they came back as 0 and then 100, which reads as a spike. Our first pass was fooled by exactly this; every reader in the code now drops those two days, and a rise must last two days to count.
- Google Ads volumes run about two months behind. Trends reads nothing reliable for terms under a few hundred searches a month.

### When a source is missing or down

The table is still written, but it gets thinner, and it says which part is missing:

| What happens | What the table loses | The line it prints |
|---|---|---|
| No `GOANYAPI_API_KEY` (the default) | The 🔎 rows, each name's long-tails, the other names searched alongside, and the `(US)` readings. Phrases come from the model alone and every curve from the worldwide series, where a real move can read flat | "Related queries are off: set GOANYAPI_API_KEY…" |
| GoAnyAPI's Trends is down (seen on its first day in use, 2026-10-12) | The same as having no key, for that run | "Related queries failed for: …" and "Country series failed, worldwide data used instead: …" |
| AIsa's post search fails for a name (timeouts seen twice on 2026-10-13) | That name's posts. A repository still has its README; a model or product without one is left with the related queries only, and with no GoAnyAPI key it gets no generic terms that day | "The post search failed; this run used READMEs and related queries only: …" |
| Neither posts nor a README for a name | Its generic terms; the name's own row stays | "No posts or README found for: …" |
| No lead that day is a thing with a name score of 0.8 or more | The whole table | "Nothing to read today…" |
| AIsa's search-volume or Trends lookup fails | The whole table: these two are not replaceable | the error, in place of the table |

A thin table is not a quiet day. Read the lines under it before you conclude that nothing moved.

Set `"usecases": {"per_day": 0}` or pass `--skip usecases` to turn it off.

### ⑥ Revenue: what people already pay for

A product that makes money proves the demand behind it. With `TRUSTMRR_API_KEY` set (from TrustMRR's developer dashboard), the radar reads once a week (`revenue.weekday`, Monday by default) the 30 fastest-growing products with at least `min_revenue_usd` ($500) in the last 30 days and the 30 newest listings, and keeps what it saw. The newest listings mostly earn next to nothing yet; they are read to record where they start, so a product at $0 last time that earns past the floor now is called out first. Hidden listings ("Anonymous startup") are left out, and a company's legal name gives way to its site's name ("Talent Tech Global Limited" is read as gptproto). Each product's own description goes to the keyword table as evidence, so the table reads the job people pay for, not only the brand. Growth above 1,000% reads "up from near $0": on the first run most of the fastest growers had started from almost nothing.

TrustMRR's API terms forbid republishing its data and building public SEO pages from it. Use the leads for your own research; do not publish the list.

### ⑦ Asks: demand said out loud

Once a week the radar searches Reddit for a dozen ways people ask for a tool ("is there an AI tool", "I wish there was a tool", "how do I automate", in `asks.patterns`), keeps the posts of the last week with a score of 2 or more, and has a small model sort them: a request, a complaint, a shared solution, or other. For requests and complaints an AI tool could answer, it writes the job the way a person would search it ("add b roll automatically", "convert slides to notes"). Jobs with at least 50 searches a month are listed with their posts and get the page-one check; each becomes a lead. Most asks are too specific to have searches yet: the first real week, 84 posts held 43 asks and only two had 50 searches a month ("best ai tool for research", from a 1,034-point r/PhD thread, and "best ai tool for coding"). So the best-scored of the others are listed too, as ideas rather than keywords. A month of posts read in a trial held a request for "an AI tool to convert PowerPoint lecture slides into notes", the same job a tool-site course uses as its worked example.

With `ai_answers` on (off by default; about $0.004 an answer), the jobs with searches are also put to ChatGPT, as the answer its own interface gives with search (DataForSEO's LLM scraper), and with `"engines": ["chatgpt", "google"]` to Google's AI Mode, as "What is the best tool to {job}?". A column says which tools the answers name (and which tool came first as `first_pick`), or with `"runs": 3` (or more) aggregates the tool and site frequency across runs (`Tool (2/3)`), marking a job as a `gap` when at least 80% of runs name no tool; under the table come the sites they cite, and ✅ when one is yours. An answer that names no tool is a gap a new tool can fill in AI search; the cited sites are the pages AI search reads for the job: get listed there, or write the comparison against them. On 2026-10-20, for "convert powerpoint slides to notes", ChatGPT named Google NotebookLM, ChatGPT and Microsoft Copilot, and AI Mode listed Knowt, NoteGPT and Microsoft Copilot among others.

Posts are for your own research: quote them, do not republish them.

### ⑧ Sellers: who just started taking money

A product's first payment link says more than its launch post: someone built a thing and asked for money for it. whoismaking.money used to rank sites by the traffic they sent to Stripe's checkout (clickstream data; its last real page in the Internet Archive is from September 2025, and by March 2026 the domain served a parked page with a hidden redirect). The same kind of data is on sale through AIsa's Similarweb at about $6 for 20 rows: too dear to cover the long tail. Payment links are a cheap stand-in. They are ordinary links on the seller's own page, so the public link graph shows them with the day each first appeared. Stripe has 143,000 linking sites and Polar 1,900 (every link a payment link); for Lemon Squeezy, Gumroad and Creem only store checkouts, `/l/` products and `/payment/` pages count, since their other links point at their own marketing sites and, for Gumroad, at profile pages spam networks use.

Once a week the radar reads, for each platform, the newest 100 payment links and the newest 100 sites to link to it for the first time (about $0.06 a platform), keeps the links of those new sites, and lists the sellers with their visits (GoAnyAPI) and their own home-page title and description, which also go to the keyword table as evidence. The first real run put janitorai.com, framer.com, pub.dev, Flathub and an n8n forum thread on top: user pages on big platforms that link to someone's payment link. So the linking page must be the site's own home, pricing or product page, not a post, thread or listing; the site must rank 350 or lower on DataForSEO's 0 to 1,000 scale; and above 300,000 visits a month it counts as a platform. A small model then sorts the new sellers by kind from their own words (keyword rules when it cannot), and AI and software come first, then templates, courses and the rest; within a kind the busiest first. On the first sorted run all twelve listed were software (a live-captions app for the Mac, a chat-with-PDF tool, an AI writing app for macOS, an MCP catalog, a Japanese audit SaaS among them), where traffic alone had put a Blender add-on site, a recipe blog and a design gallery first. A payment link means the site sells, not that it sells well, and checkouts made by code at payment time are not seen.

A new link is not a new seller. A first version took the newest links for new sellers; on 2026-10-14 we checked them against the day each site first linked to the platform. A site that has sold for years puts the same link on every new page it makes (one carries its Stripe link on each of its well-permit pages), and two thirds of the 2,000 newest Stripe links came from such sites: of the 60 Stripe sellers that day's list showed, 17 had just started. So a seller is new by the day its site first linked to the platform (DataForSEO's referring domains), and the report says how many links came from sites that sold already.

### History: every seller back to 2019```bash
python -m radar history pull            # every site linking to the five platforms today: about $18
python -m radar history read            # their home-page titles and descriptions, free
python -m radar history sort            # their kind, by a small model: about $0.005 for 60 sites (--rules: keywords alone, free)
python -m radar history update          # weekly: the sellers that appeared since the newest day, about $0.5
python -m radar history --out sellers.csv

history pull reads every site that links to each platform today, one row per site with the day it first linked: DataForSEO's one-per-domain backlinks, oldest first, 1,000 a call ($0.06). On 2026-10-14 that day matched the referring-domain first-link day for all 1,704 Polar sites both lists name alike. It stops at --max-usd (default 20) and resumes where it stopped. history alone counts sellers per month, platform and kind; --out writes them all to a CSV. The rows are DataForSEO's: for research, not to republish.

How far back it goes, from the link graph's monthly count of sites linking for the first time (2026-10-14; one call per platform, $0.03):

Platform Counted from Sites since 2019 New sites a month, May to September 2026 Linking today
Stripe June 2021 (a few dozen a month before) 306,000 6,500 to 8,200 (14,200 in June) 143,000
Gumroad 2019 530,000 4,200 to 5,700, while 6,400 to 9,400 drop their links 140,000
Lemon Squeezy 2023 34,000 600 to 1,100 18,000
Polar 2024 2,285 109 to 268 1,943
Creem 2025 1,708 74 to 268 1,449

Two cautions. In October 2023 Stripe's count jumped from 3,216 to 16,206, and new links from 1.2 million to 20 million the month after: the crawler grew, not the sellers. And a pull holds only sites that still link, so the older the month, the more of its sellers are missing. For Gumroad, Lemon Squeezy and Creem the monthly counts also include links to their own sites and to profiles; the pull keeps those apart (only payment links count as sellers).

⑧b, ⑨, ⑩ and the evidence beside the names

  • ⑧b Builders (weekly, with ⑧): the badge an AI app builder puts on what it made ("Edit with Lovable", "Built with v0") and the "Powered by beehiiv" link of a new newsletter, read from the same link graph. Most of what people build with an app builder is a business's website (a pizzeria, a lawn service); only the software among them becomes a lead, the rest says what the builder is used for.

…(正文过长,页面只展示前面部分,完整内容见仓库)

常见问题

8 问
答案由本站依据条目字段整理,不引用上游原文
New Term Radar 怎么安装?

在客户端按下面的安装命令接入:uvx。装完在客户端配置里引用同一个包或端点。

New Term Radar 怎么在 Claude Desktop、Claude、Cursor 里配置?

它的传输方式是stdio · 本地进程,在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,配置才会生效。

New Term Radar 收费吗?

本站不代收费用,也没有标注具体价格。是否收费取决于服务本身和背后的接口额度,正式使用前按官方说明确认。

New Term Radar 需要 API Key 吗?

资料没有标注鉴权方式,是否需要密钥取决于服务本身,接入前按官方文档确认。

New Term Radar 支持哪些客户端?

资料标注支持 Claude Desktop、Claude、Cursor、VS Code、Gemini CLI、Codex;其他客户端只要能配置 MCP Server,也能用同样的命令或地址接入。

New Term Radar 能提供哪些能力?

资料显示能力标签包括 营销。具体工具清单以官方文档为准。

New Term Radar 需要什么运行环境?

属于本地进程,需要在本机装好运行环境。

New Term Radar 是本地还是远程?

它是本地进程(stdio),由客户端在本机拉起。传输方式为stdio · 本地进程。

热门专题

按标签挑服务器
全部专题 →

服务器信息以作者仓库与官方文档为准;分类、传输方式与鉴权方式的中文说明为中文整理,最近核验 2026-11-20。