AI tool sites and agent directories after Meta Muse and Manus Cue: what is still buildable

0. Bottom line

• A generic AI agent directory / navigation site: KILL. Most of the 11 directories in §3.3 already list Muse or Manus 2.0, or run dedicated agent directories (TAAFT had renamed its page to "Manus v2" within 24 hours of the Manus 2.0 launch; AgentFilter claims 1,420 agents; Enterprise DNA claims 6,761 entries). A new site cannot win on listing speed or listing count.
• Brand pages around the two launches (invite codes, alternatives, "vs", pricing, running locally): mostly KILL. Each type filled up within 0–3 days, and exact-match domains were grabbed on launch dates: museaicode.cc, cuebymanus.com and manuscue.com were all registered on 2026-09-28, and muse-invite-code.com on 2026-09-27 (RDAP).
• The only small bet worth trying (BUILD-lite): a task × capability × region verification table for personal agents, organized by task rather than by brand. Examples: "which agent can make a phone call for me / book a flight / buy on Amazon", "is Muse available in Canada, the UK or India". Three reasons: autocomplete has deep task long-tails ("best ai agents for X", "ai agent that … for you"); the results for those queries are vendors' own landing pages, with no neutral verification page; and the facts themselves change quickly and contradict each other (§3.1). That is exactly the "unique data + ongoing maintenance" entry point.
• Carried over and strengthened: C4 from today's report (agent permission and risk self-check) stays BUILD. Muse produced 4 more permission-related incidents in the past 10 days (§3.2), which can serve as C4's first real cases. No new site is needed.

1. Background on the two events (verified)

1.1 Meta Muse (personal AI agent)

What changed since 09-28: the 09-28 report killed "meta muse" outright as a brand term. This round's autocomplete shows something more important: "Muse" is an umbrella brand at Meta. Autocomplete mixes Muse Spark 1.1/1.2/1.3 (models; 1.3 shipped 2026-09-02, HN 691 points), Muse Glimmer 30B (open-weight on-device model, 2026-08-10, HN 1,209 points), Muse Code (a coding agent), Muse Image (since 2026-07, with an opt-out controversy), Muse Video, and the Muse agent itself. Under the single "muse" root, tool demand is split across four lines (models, coding, images and the agent), so intent is very mixed.

1.2 Manus Cue (cue.im)

2. Candidate keyword pool (24 clusters)

"Autocomplete" is how rich the long-tail is in Google suggestions on 2026-09-29 (suggestqueries, default hl=en, gl=us; some seeds tested in 11 extra locales). The stars are a qualitative read, not a volume measure. This round made 459 autocomplete requests and collected 2,194 unique suggestions; 101 requests returned nothing. Search volume, KD and CPC are all unknown and not repeated in the table.

3. Deep dives and verdicts

3.1 "Which agent can do X": task × capability × region verification table — BUILD-lite (1–2 page experiment)

• Demand signals (autocomplete, qualitative):
• Task long-tail: best ai agents for {personal use, email management, online shopping, booking flights, outbound calls, job applications, home use, daily use…}, with all 10 slots filled for every letter a–z; ai agent for booking {flights, appointments, restaurants, hotels, tickets}; ai agent that {calls for you, takes calls, makes phone calls}; ai agent to make phone calls for you; which ai agent is best for ….
• Region: is meta muse available in {canada, india}, meta muse {canada, uk, india, australia, germany, 日本}, meta ai available countries (list), whatsapp meta ai available countries in europe / in india.
• SERP proxy:
• "best ai agents for personal use": vellum.ai, mastra.ai, get-alfred.ai, nombo.ai, fliiq.ai — all vendors ranking themselves;
• "ai agent that books flights": roamx.ai and oerno.com (consumer apps) plus travelandz, reservations.ai and liteapi (developer APIs) — no neutral verification page;
• "ai agent that makes phone calls for you": trysabit.com (RDAP 2026-01-02), getosmo.app, voyp.app, fazier — also all vendor pages.
• The facts are moving and contradictory (the key point):
• Region: Meta officially says only "US"; invite-code sites say "US and Canada"; ddewhurst and ai.nl say "US and UK". Three versions coexist in the top results.
• Capability: Forbes (2026-09-21) reported that "Amazon blocks Meta's new Muse AI agent from shopping on amazon.com" (HN 152 points). 404 Media (2026-09-22) reported that Meta is testing Muse calls that are actually made by humans in a call center (HN headline). Answers to "can Muse buy on Amazon?" or "is it a human on the Muse call?" can change at any time.
• That is the "unique data" framework.md asks for: each cell is "agent × task × region × check date × source link". Vendor listicles cannot provide it.
• User job: "I want AI to do X for me (call to book, book a flight, unsubscribe, shop online). Which agent can really do it today, does it work in my country, and do I have to pay?"
• Minimum product: one static (SSG) page. Rows are agents (Muse, Cue, Grok Bot, ChatGPT agent, Gemini, Manus, OpenClaw, Hermes), columns are 8 tasks plus an "available regions" column. Each cell reads can / cannot / partial / unknown, with a source link and a check date. Add a filter (pick a task and a country, get the answer) built in plain HTML/CSS, with the key content in static output. Start with just 2 inner pages: which ai agent can make phone calls for you and is meta muse available in my country.
• Exact-match domains (RDAP, 2026-09-29): whichagentcan.com, agenttaskmatrix.com, aiagentavailability.com, isagentavailable.com, personalagentdirectory.com and bestpersonalagents.com all return 404 (unregistered); canmyagent.com was registered on 2026-09-20.
• Monetization (assumptions, no promises): weak, and that is the biggest issue. Muse is free or subscription, Cue is free, and Manus has no affiliate program (today's report found /affiliates returns 404). The options left are affiliates of consumer calling apps (not verified), display ads (RPM unknown), an email list ("this agent just opened in your country" alerts) and vendor sponsorships. This conflicts with the "aggregate money, not traffic" preference set on 09-07, so it gets BUILD-lite only.
• Risks: the data needs weekly re-checks, and that cost falls on a person. The pages must not pose as official Meta or Manus pages, and must not teach VPN or APK workarounds for the region lock (the reason #16 is KILL).
• Deciding variables: ① there is no neutral page in the top results, and real check-dated, sourced data is possible; ② monetization is weak, so GSC impressions and email sign-ups must show up within 14 days or the experiment stops.

3.2 Agent permission and risk self-check (C4 in today's report) — BUILD carried over, with new Muse evidence

Muse permission-related incidents found this round in HN headlines and reporting (all headline-level; bodies not checked one by one): - 2026-09-22 mouse.dev, "I asked Meta's Muse for its filesystem and it sent me 6.8GB" — HN 357 points / 171 comments; - 2026-09-22 Inc., "Meta's New Muse AI Agent Read My Private Messages. I Never Asked It To"; - 2026-09-28 AppleInsider, "Meta's new AI agent blatantly ignores users permissions"; - 2026-09-25 mouse.dev, "Meta's Muse appears to use an OpenAI model labeled muse-special" (HN 143 points); - Third-party (shipwithmuse.live) account of a zero-day in the Muse Mac app (found by Patrick Wardle, reported by Malwarebytes) that could redirect voice prompts and the auth token to an attacker's server (original not checked). On HN, an Ars Technica headline from 2026-09-22, "Meta’s Muse has a serious 0-day" (122 points), points to the same class of issue; its body was not fetched. - Autocomplete: meta ai agent {incident, data leak, breach}, meta muse spark ai breach, meta muse security, ai agent permissions (management).

Conclusion: these incidents make "check before you hand an agent your email, number or wallet" more convincing. C4 stays BUILD, with Muse as C4's first platform module (what permissions Muse actually gets, how to turn each off, and which incidents have happened). Do not start a separate "Muse security" site, which would compete head-on with news sites.

3.3 Generic AI agent directory / navigation site — KILL

• Demand exists: ai agent directory {free, github}, ai agents directory & marketplace (the brand query for aiagentsdirectory.com), ai agents list {free, github, website}, ai tools directory {submit, 2026, reddit}, theresanaiforthat {alternative, review}.
• Who ranks / who has already listed (direct fetch and SERP proxy, 2026-09-29):

• Judgment: the leading directories already list new launches within a day (TAAFT's Manus v2 page). A new site would compete on listing count, update speed and backlinks, and would lose on all three. The top results for ai tools directory submit are "where to submit" articles from aitoptools, directoryready, aitoolsrecap, lovedby.ai and smollaunch, so the supply side is full too. This matches K2 in today's Cue report and K2 (skills directories) in the 09-28 atlas.
• Only exception: a narrow vertical directory with unique data, i.e. the §3.1 table. It is essentially a directory of only 8 agents with verified data in every cell, not another navigation site with 1,000 tools.

3.4 Invite-code trackers (Muse / Cue / Manus) — KILL

• Autocomplete: muse agent invite code, meta muse invitation code, manus invite code {reddit, generator, free}, manus promo code {2026, for credits reddit}; Cue has no product suggestions.
• SERP proxy ("meta muse invite code"): museaicode.cc, tabaix.com, bitdoze.com, resourify.com — 4/4 are dedicated invite-code pages.
• RDAP: museaicode.cc registered 2026-09-28, muse-invite-code.com 2026-09-27, museinvitecode.com 2026-09-07 (the day before the Muse launch), cuebymanus.com and manuscue.com both 2026-09-28 (the Cue launch day); cueinvitecode.com is 404.
• Deciding factors: supply is saturated, and there is platform-rule and misleading-content risk (K1 from today's report carried over). Invite-code traffic is one-off: the day sign-ups open, the demand disappears.

3.5 Alternative / "vs" pages — KILL (Manus alternatives) / WATCH (Muse alternatives)

• Manus alternatives: very rich autocomplete in 8 languages. But the SERP proxy top 5 is aiagents.wiki, stackbuilt.co, toolworthy.ai, gamut.so and aiagentrank.io, and TAAFT, futurepedia and toolify tool pages carry their own alternatives modules; manusalternative.com was registered on 2026-05-11. → KILL.
• Personal agents compared with each other (grok bot vs muse, muse vs openclaw, openclaw vs hermes): the SERP proxy shows codepick.dev (which already has "Cue vs Muse vs Grok Bot (2026)", published within about 31 hours of the Cue launch), rerealize.com, ddewhurst.com, ai.nl, vismountain, agentlux and superbash — 7+ sites. → KILL.
• Muse alternatives: autocomplete for meta muse alternative, muse agent alternative, meta muse vs chatgpt, meta muse prompts and muse agent use cases is completely empty. The SERP proxy returns unrelated CRM tools (alysio, askelephant, byobot, salesforce, streak), meaning nobody has written pages for this intent yet, and the demand has not formed yet either. → WATCH: once meta muse alternative appears in autocomplete while the top results are still irrelevant, add it as an inner page of the §3.1 table. musealternatives.com and metamusealternative.com are both 404 for now.

3.6 The Muse model line (running Glimmer locally / Spark API pricing / Muse Code plans) — KILL

• Glimmer: rich autocomplete (ollama / 30b / unsloth / dgx spark / open weights / vs qwen 3.8), but it shipped on 2026-08-10, outside the 30-day window. The SERP proxy top 5 is holaclaw.ai, localaimaster.com ("Which Quant Fits 16GB", a tool intent right in the title), pulsemark.ai, computingforgeeks and ollama.com; museglimmer.com was registered on 2026-08-08.
• Spark / Code pricing: the SERP proxy shows tech-insider, myclaw.ai, layer3labs and Meta's official pricing page on dev.meta.ai. LLM cost comparison tools were already killed on 09-28 (K4: pricepertoken covers 300+ models with only 2 active subscriptions), and this round found nothing to overturn that.

3.7 Muse opt-out / support / APK — KILL

• meta muse opt out / turn off / image opt out: the SERP proxy is mobilesyrup (2026-07-08), Rolling Stone PH, wowktv and Instagram's official help center. This is the old July Muse Image story, already covered by news and official help.
• whatsapp ai agent turn off / not showing: official WhatsApp support intent.
• muse agent apk / meta muse apk download: in essence, users outside the region trying to get around the lock, which crosses methodology.md's "do not help circumvent platform rules" line.

3.8 Use-case and prompt libraries (personal agent use cases / prompts) — WATCH (only as §3.1 inner pages)

• Generic terms (personal ai agent use cases / ideas, ai agent prompt template, ai agent use cases for personal use) have rich autocomplete. The top results are personal blogs, Towards Data Science, the Google blog and Reddit, which signals informational intent and weak monetization.
• Brand-specific terms (meta muse prompts, muse agent use cases, meta muse examples, meta muse templates) are all empty.
• → No standalone site. Turn them into "what to say to the agent" examples inside each task cell of the §3.1 table, serving both search and users.

4. Opportunity scores (1–10, coarse, not a precise model)

Weights: "SERP gap", "product wedge (unique data or not)", "monetization" and "compliance risk (reverse: higher score = lower risk)" are the deciding variables; the rest are for reference. Search volume and trend are unknown, so Demand is only a rough read of autocomplete richness.

5. Top 3 + 14-day validation plan + kill conditions

🥇 #1 "Which agent can do this?" task × capability × region table (BUILD-lite)

Head terms / cluster: which ai agent can make phone calls for you | ai agent to make phone calls for you | ai agent for booking flights / restaurants | best ai agents for personal use | is meta muse available in canada / uk / india | meta ai available countries Languages: English first. Demand behind meta muse 日本 and meta muse germany must be re-validated against local SERPs (not done this round); do not simply translate.

Kill / adjust conditions (checked on D14): - Indexed, but 0 impressions in both GSC and Bing → run the four-level GSC diagnosis on crawl and indexing first; if indexing is fine and impressions are still 0 → stop adding pages and move to WATCH. - Impressions exist but are all brand navigation queries (e.g. "meta muse"), with no task or region queries such as "which agent / that calls / available in" → task-organized demand is not real; KILL. - On D14 email sign-ups are < 10 and no affiliate or sponsor can be attached → no monetization path; keep the pages but stop maintaining them. - Meta or Manus publishes an official per-country availability and capability list → the region column loses its value; keep only the task matrix.

🥈 #2 Agent permission self-check + Muse module (C4 = BUILD, carried over from today's report)

• This round does not re-judge C4; it only adds evidence: the 4 Muse incidents in §3.2 plus the autocomplete terms meta ai agent {data leak, breach} and ai agent permissions management.
• New actions in the 14 days: D1–D3, check the 4 incidents against their originals (all are headline-level for now) before anything goes on a page. D4, ship a Muse permission checklist (the Mac app's per-app off / read-only / read-and-act levels, sourced from Muse Mac help documentation; the official original must be checked first). Everything else follows C4's original plan.
• Kill: C4's original conditions, plus one more: if 2 or more of the 4 incidents do not hold up on checking, downgrade the Muse module to an FAQ paragraph.

🥉 #3 Muse alternatives / Muse prompts (WATCH, 30-minute low-cost monitoring only)

• No code and no domain purchase. Every 3 days, re-run these seeds with ac2.py: meta muse alternative, muse agent alternative, meta muse vs chatgpt, meta muse prompts, muse agent use cases, meta muse examples.
• Upgrade condition: at least 2 of these start returning suggestions, and the WebSearch top 5 still has no targeted page → add them as inner pages of #1 (no standalone site).
• Kill condition: still all empty after 14 days, or the top results get covered by sites such as codepick or toolworthy → KILL.

6. KILL list (with reasons, so they don't come back)

1. Generic AI agent / AI tool directory site: TAAFT updated Manus v2 within 24 hours of launch; AgentFilter claims 1,420 agents, Enterprise DNA 6,761 entries, agenticindex 892 vendors; aihub.cn already has a Cue page.
2. Muse / Cue / Manus invite-code trackers: 4/4 top results are dedicated invite-code sites; cuebymanus.com and manuscue.com were registered on the Cue launch day (09-28), and museaicode.cc also on 09-28; platform-rule risk.
3. Manus alternatives / "agents like manus" list sites: covered by 5 alternative sites plus 3 large directories; manusalternative.com was registered in 2026-05.
4. Personal agent "vs" pages (Muse vs Grok Bot vs OpenClaw vs Hermes vs Cue): 7+ sites, and a three-way comparison appeared within about 31 hours of the Cue launch.
5. "Can my Mac run Muse Glimmer" calculator: the window has passed (08-10); 4+ tutorial sites and ollama already cover it.
6. Muse Spark / Muse Code pricing calculator: an official pricing page exists; already killed on 09-28 (K4).
7. Muse opt-out tutorials: an old July story, covered by news and official help.
8. Muse APK / region-lock workarounds: crosses the method's compliance line.
9. WhatsApp AI agent support content: official support intent.
10. AI tool directory "where to submit" lists: the supply side is saturated.
11. AI agent rankings / tier lists: aiagentrank.io, userightai and others already do this.

7. Data sources and blocked channels

8. Next evidence most likely to change the decision

1. Use any keyword tool (free Ahrefs / Semrush quotas are enough) to add search volume, KD and CPC for #1's 8 head terms, recording the tool, region and date.
2. On a machine with normal Google access, review the real SERPs by hand (US, incognito), especially the top results for ai agent that makes phone calls for you and is meta muse available in canada.
3. Check whether the consumer calling apps (Sabit, OsmO, Voyp) run affiliate programs (not verified); this decides whether #1 can make money.
4. Check the 4 Muse incidents in §3.2 against their originals.