Cue / Manus keyword scan: is an unindexable product domain worth a new site

# Cue / Manus keyword scan and site-launch diagnosis (2026-09-29)

Verdict up front: there is a site to build, but it is not a Cue content site — it is a "credits and permissions ledger" site. This round returns 3 BUILD / 5 WATCH / 4 KILL. The one worth building inside 14 days merges C1 (Manus credit loss and account operations) with C4 (what you are about to allow an agent to do). Search volume, KD, CPC and Trends are unknown this round — no keyword-tool account, and Google Search plus the Trends API are blocked from this exit — so every judgement rests on autocomplete, raw HTTP responses, observed SERPs and published vendor/competitor data.

1. What shipped, and when

Manus shipped Manus 2.0 and Cue together on Monday 2026-09-28. From the announcement (manus.im/blog/introducing-manus-2-0, fetched 2026-09-29T05:33Z):

• "Cue is a new standalone app for your personal agents… built on the same infrastructure as Manus."
• "each agent has its own email, phone number, wallet, and computer, so it can send messages, pay within the budget you set, and see a task through on its own machine. It can also take your calls and leave you a summary."
• "Put several agents in a group chat with a shared goal" · "At a restaurant, scan the QR code and your agent can order for you or hold your place in line."
• "Cue is in early access and free to use with an invite code. You can start with MEETCUE… Everyone who gets access also receives extra invite codes to share." iOS is "coming soon after App Store review".

Implicator.ai (Marcus Schuler, 2026-09-28 4:23 PM PST, 10-minute read, full text archived): "Its efficiency claims are unverified, and the launch lands as Manus seeks a $4 billion valuation after Beijing blocked Meta's deal." Ownership is confirmed at headline level from archived CNBC HTML: "China blocks Meta's $2 billion takeover of AI startup Manus" and "Meta's $2B Manus deal pushes away some customers". Reuters returned 401 and was not read.

Pool size anchor, vendor-reported and unaudited: Manus's own blog post "Manus Update: $100M ARR, $125M revenue run-rate" — "crossed $100M in ARR, eight months after launch".

Press surface in the following 24–30 hours, including what was absent: Techmeme carried one Bloomberg line; no TechCrunch, The Verge, Reuters, Axios, WSJ or Business Insider item about Cue was found; the Hacker News story sits at 1 point with 2 comments; Cue has no Product Hunt launch (Manus itself has 8, most recently Cloud Computer at 270 points). English content slots were taken within hours by small SEO blogs — cellcog.ai (17h), wandabuilds.ai (1h), explainx.ai, gpts24.com. Chinese coverage was already saturated inside 24 hours: sohu, toutiao, woshipm, zhihu, aiposthub, aihub.cn, linux.do, v2ex.

2. Crawling cue.im: the domain is currently unindexable

All observations from raw HTTP responses, 2026-09-29T05:25–05:36Z.

Every path hardcodes <link rel="canonical" href="https://cue.im">. The only crawlable text on the domain is one title, one description and one keywords meta tag (Cue, Manus, AI agents, AI assistant, automation). No robots meta. The launch date is visible in the preloaded asset path: files.manuscdn.com/assets/dashboard/materials/2026-09-28/….

Manus's own domain does not catch Cue either: manus.im/cue → 404; of 71 URLs in manus.im/sitemap.xml, 0 contain cue|2-0|cascade|studio|automat (the 2.0 post is not submitted); the visible text of help.manus.im/en/ mentions "Cue" 0 times, with only 2 articles in the Manus 2.0 collection, and /en/collections/manus-2-0 → 404.

By contrast the parent site's SEO machine is mature: 17 language sitemaps in robots.txt, programmatic /tools/* pages (pdf-to-ppt, ai-image-generator, nano-banana-pro-slides), /features/* (mail, wide-research, browser-operator, skills) and /compare pages against ChatGPT, Lovable and Replit. One more technical gap worth recording: manus.im/pricing serves 204,552 bytes of HTML but only 646 characters of visible text after stripping tags — plan and credit numbers are client-rendered.

In the on-page audit framework this is a P0 topic-entry vacuum: no official page currently answers any Cue information need in crawlable text. A vacuum is not automatically a durable opportunity — Manus has demonstrated it understands SEO, so filling it is a matter of time.

3. Keyword scan: 5,066 autocomplete rows, 2,621 unique suggestions, 109 seeds

Method: suggestqueries.google.com/complete/search?client=firefox, three waves (phrase seeds / deep expansion / single-word roots) across en-us, en-gb, en-in, en-au, de-de, fr-fr, ja-jp, es-es, pt-br, zh-cn, it-it, kr-kr. Raw lines in suggest_phrase.tsv, suggest_wave3.tsv and suggest_wordlevel.tsv (these three feed the atlas); the wider 12-locale single-word pass ships too as suggest_raw.tsv. Aggregates in keyword_autocomplete_matrix.json and inventory.json.

3.1 Zero query history for the brand, and heavy token pollution

cue im, cue.im, meetcue, cue by manus, cue early access, cue im invite code, cue manus app, cue vs manus return no product suggestions at all. Google offers cue ball, cue cinemas, CUET exam (Indian university entrance), cue image, cue imax, iCUE download (Corsair software), meetcute (a film trope). Nine seeds came back empty in en-us. Outside English, no locale produced a single suggestion containing cue or manus in a product sense; zh-cn returned only 246 rows and is filtered at the endpoint, so it is not used as demand evidence.

Two things are true at once. Window — no page has accumulated semantic history on these terms, so the SERP is decided by whatever appeared in the last day. Toxicity — cue is a common word, so brand traffic leaks permanently to CUET, iCUE, cue.com, withcue.ai (a same-named AI meeting-notes app, live on Google Play), billiards, NASDAQ:CUE and, in Chinese, the slang usage "别cue我". Bing's first page for "cue im" already mixes in Merriam-Webster and Baidu Baike. Only qualified forms are usable: cue by manus, manus cue, cue.im, meetcue.

3.2 The install-base demand is about money and accounts, not features

These clusters fired consistently in en-us, en-gb and en-in — multi-year behaviour, independent of Cue:

• Credits: manus credits → cost, explained, free, code, not refreshing, promo code, usage, reddit
• Account: manus account suspended → why is my manus account suspended, reddit, how to get suspended account back; manus login → error, page, app, im
• Trust: is manus safe → is manus ai app safe, is manus im safe, is manus secure, is manus reliable, manus ai safety
• Price: manus pricing → tiers, plan, api, team, india, reddit; Spanish cuanto cuesta manus ai
• Substitution: manus alternatives → free, github, open source, reddit, manus im alternatives
• Codes: manus invite code → generator, free, reddit, referral code (see KILL)

Community phrasing is more diagnostic than keywords (all captured this round, sources in the appendix): "MANUS: HOW MANY CREDITS HAVE YOU LOST?", "It literally burns 300 credits in under 10 minutes", "Manus refunded $698.89, then deducted 57,848 credits", "Expired credits is the most ridiculous thing I have ever heard of", "randomly expensive because the agent decided to go on a side quest", "i still like Manus. i just hate being scared to hit run now" (r/ManusOfficial, 20 points), "Horrible manus customer service". First reactions on the Cue side land on money and identity too — linux.do: "cue好像还可以购买美国手机号？？？真的假的" (can Cue buy a US phone number?), "邀请码是多少呀" (what is the invite code), "手慢了…找不到填写的入口" (the code entry was impossible to find).

3.3 One capability, three vocabularies

• Builders: give your ai agent a phone number (present verbatim in autocomplete), email inbox api for ai agents, ai agent email inbox, langchain ai agent inbox, ai agent for email {automation, management, reply, responses}, ai email agent for gmail
• Security: ai agent identity → management, security, access management, governance, verification, framework, microsoft, startup — 117 rows across 9 locales, the largest non-brand cluster this round
• Consumers: ai agent that makes calls for you, ai agent to make calls for me, free ai agent phone number, ai to unsubscribe from emails, use ai to unsubscribe from emails, ai to manage my email, personal ai agent {app, free, github, setup, use cases}, ai personal assistant {app, free, device, like jarvis}
• Payments: visa ai agent credit card payments, mastercard ai agent payments, moonpay ai agent debit card, robinhood ai agent credit card, can ai agents spend money

Press says "personal agents", builders say "give your agent an email", security says "agent identity", consumers say "ai inbox". virtual employee is unusable — it is already owned by offshore human VA listings.

3.4 Jobs, ranked

556 of roughly 2,500 agent tutorials in the sampled set are email triage — the single largest task. The rest of the recurring list: unsubscribes and subscription cancellation, bill and medical-bill negotiation (one HN thread at 1,034 points and 923 comments), receipt and invoice capture, morning briefings, bookings and appointment chasing, form-filling where no API exists, and dull vertical admin (law-firm retainer letters, rental deposits, estate paperwork). Cue's own copy lands on three of these (answer calls and leave a summary, scan a QR code to order or hold a place, group-chat collaboration). Product direction matches the task language — but none of it is published as crawlable task pages, which is exactly the internal-link map for C1 and C2.

4. Supply and monetisation rails (competitor scale verification)

Full layer-by-layer evidence with URLs and access timestamps is in raw/competitors.md (75 raw HTML documents, 11 TrustMRR responses, 38 explicit unknown flags).

Email layer is occupied and priced. AgentMail (YC, $6M seed, homepage literally "Email Inbox API for AI Agents", Free $0/3 inboxes → Developer $20/mo → Startup $200/mo) has no affiliate program — /affiliate, /affiliates and /partners all 404. Lumbox $0/$9/$29/$99, Shipmail $4–$29 (Scale $2.50 per mailbox), plus OpenMail and Robotomail holding content slots. This layer is red ocean with no revenue-share rail, not a gap. Verified indie revenue does exist nearby: ColdSire (cold-email inboxes, $6/mo per account) — Stripe-verified last-30d $15,428, MRR $15,815, 915 subscriptions, all-time $1,036,622, MRR −8.1%, on sale asking $215,000 with 24 offers (re-fetched independently from /startup/coldsire.md; MRR and growth match).

Voice/number layer is the only place with a cash affiliate rail. Retell ($0.07–$0.31/min, infra $0.055/min) pays 15% of referred revenue for 12 months, 90-day cookie, monthly, no thresholds; Robofy 30% recurring for 12 months, 60-day cookie, Tolt + Stripe; FlyHermes 20% lifetime, Rewardful. Vapi prices Core $29/mo and Pro from $999/mo; Synthflow enterprise from $30,000/yr — vendors charge heavily, so third-party content can only survive as a neutral comparison. BookedIn AI (no-code agents across voice, SMS, email and Instagram; the closest independent analogue to Cue) is Stripe-verified at MRR $11,948, 94 subscriptions, last-30d $6,009 (−18.4%), on sale asking $1,000,000 with 9 offers — an asking price of 84 months of declining MRR is evidence about valuations, not about demand. Raw numbers themselves are a commodity: 5SIM sells single-use numbers from $0.008.

Wallet/card layer has almost no attachable business model. Proxy (useproxy.ai, the most explicit "cards + accounts + wallets for AI agents": $0 cap $100 / Personal $19.99 + 0.15% overage / Business $199 + 0.10%) shows a waitlist on every tier; AgentCard has no pricing page though Mastercard Agent Pay is live on it; the one TrustMRR-verified indie attempt, PayLinks ("agentic-first payments"), is at $0 revenue, 0 subscriptions, −59% growth30d. FastCompany reported Mercury launching virtual cards for AI agents but returned 403, so that remains unverified. Card networks are already generating queries: Visa Intelligent Commerce, Mastercard Agent Pay.

Identity/credential layer has money but no indie slot. None of the 204 TrustMRR startups sells "agent identity" as its product; the layer is held by enterprise IAM (Aembit, Dock, cidaas, Bitwarden, Infisical, Nango) plus AgentMail's free AgentID (OIDC for agents). The adjacent indie position is proven though: Brevilabs, agent context and credentials, Stripe-verified last-30d $31,293, MRR $18,758, 1,423 subscriptions, all-time $894,878, 95% profit margin, MRR −3.8%, not for sale (independently re-fetched; figures match). There are fish in this pond, and the water level is falling — entry has to come from a new surface (consumer-side permission review), not from another enterprise IAM clone.

Rails on the Manus side are credits, not cash. manus.im/affiliates, /affiliate and /referral-program all 404; /fellows is an offline ambassador program with batch two closed; manus.io/affiliates is a lander stub (114 bytes redirecting to /lander), not Manus's. Program terms (manus.im/edu/rules) state "Credits have no monetary value and cannot be exchanged for cash", amounts are undisclosed and discretionary, self-referral is prohibited but bulk distribution of referral links is permitted. manusinsider.com already lives on that rail, stating on-page: "This free guide is supported by referral credits" — not cash income, but a functioning model.

The security event is the strongest timing evidence this round. Salt Labs disclosed on 2026-09-24 that an email carrying an obfuscated instruction produced remote code execution inside a victim's Manus environment, reaching credentials and tokens for connected Gmail, Drive and GitHub. Dark Reading covered it exclusively (curl 403; headline and framing cross-confirmed via Implicator.ai, the Aviatrix Threat Research Center page and Security Against AI; the original Salt Labs blog path now 404s, recorded as unreachable). Implicator.ai adds: "A Manus security warning appeared only after the payload had run" and "Salt Labs said Manus did not reply to its report." Four days later, Cue hands consumers an email address, a phone number, a wallet and a computer. The industry newsletter The Neuron put it as: "hand the agent a wallet, then invent the circuit breaker".

5. Verdicts

Judgements follow the gefei rules used throughout: demand before code, page form decided by intent, no revenue promises. Full fields (demand evidence / supply evidence / intent / form / monetisation / risk / kill) are in the downloadable candidates.json.

BUILD

C1 — Manus credits and account operations desk. Demand: the whole 3.2 cluster plus verbatim complaints about burn, expiry and post-refund clawbacks. Supply: no independent Manus credit calculator exists (multiple searches, no hit; Manus publishes three worked examples — 200/360/900 credits — and no tier table, and even those numbers are client-rendered). Form: credit calculator (task → credits → cost, covering expiry and non-refresh cases) + suspension and appeal paths + billing-anomaly checklist. Monetisation: one-off template pack $9–19, policy and tier change alerts $5–9/mo, AdSense as floor. Manus pays referrals in credits, so affiliate is not a cash rail here. Kill: under 1,000 GSC impressions at day 30 or email conversion below 1%; or the official help centre ships a credits tier table plus a dedicated collection.

C4 — Agent permissions and risk desk (before you hand it an inbox, number, wallet). Demand: the ai agent identity cluster, is manus safe / secure / reliable, explicit refusal language ("I just watched my AI Agent delete 400 emails", "do not give openclaw access to your inbox. it is hallucinating legal threats to cancel subscriptions", "I'd never give an agent my card") and a public email→RCE disclosure. Supply: one Dark Reading article plus three second-hand write-ups; no independent permissions checker or checklist site exists. Form: free checker (pick a platform → enumerate the identity surfaces that agent actually holds, and what is missing) + downloadable checklist + budget circuit-breaker configuration guide. Monetisation: checklist and template packs, team tier (who approved what), change alerts. Shares the Worker + D1 + detection base already scouted for candidate D (AI crawler and agent traffic monitoring), so it can be a second leg of that product rather than a new bet. Risk: every security statement needs a citable source — misstating a vendor flaw costs credibility and legal exposure; YMYL-adjacent, so disclaimers are mandatory. Kill: if a vendor publishes its own agent-permissions checklist within two weeks, or if no second independent source holds up, demote to a C2 inner page.

C2 — The Cue fact sheet (English, indexable, window-type). Demand: zero brand query history, empty English press, saturated Chinese coverage — the English need is unhosted. Supply: zero crawlable official content (section 2). Form: SSG single page, every claim quoting the official text with retrieval dates, changelog, relation to Manus, supported clients, access conditions, known limits; always qualified (Cue by Manus, cue.im), never implying official status. Monetisation: email list (early access, change alerts) feeding C1 and C4 paid products. This is a traffic asset, not a durable one: it dies the moment cue.im ships crawlable text or a sitemap, at which point it becomes internal linking for C1 and C4. Kill: crawlable body text or a submitted sitemap on cue.im, or manus.im/cue stops returning 404.

WATCH

W3 — Agent capability stack table (email / number / card / identity, who sells it and how it is priced). Roots are growing (274 unique suggestions across ID1–ID4) but only voice carries affiliate cash (Retell 15%, Robofy 30%, FlyHermes 20%); email and wallet vendors have none, and the data needs monthly manual verification — last round already proved affiliate payouts cannot cover verification labour. Do not build unless the scope narrows to voice alone.

W1 — Cross-assistant subscription and credit bill aggregation. Queries are real (manus pricing {tiers, api, team, india}, manus credits {cost, usage, not refreshing}, Spanish cuanto cuesta manus ai), but the opacity that creates the gap also blocks programmatic collection, and last round falsified cross-provider usage tooling (free OSS saturation) and comparison-site ceilings (pricepertoken, DR 51, 2 active subscriptions). Revives only if an official billing or usage API becomes reachable.

W2 — Agentic payments authorisation and limits. visa ai agent credit card payments and mastercard ai agent payments are in autocomplete; this cluster's SERP was not deeply sampled (Bing degrades on multi-word queries, section 7), so supply is unknown. Cut it if the first page is all card-network and processor documentation.

KILL (do not re-propose)

• K1 Invite-code resale or generator. Demand is genuine (manus invite code generator; MEETCUE plus shareable codes), but it sits against platform rules and the misdirection boundary, and Manus explicitly reserves the right to terminate accounts and cancel unused credits at any time.
• K2 "Best personal AI agent" directory. personal ai agent {app, free, ideas, use cases} demand exists, but navigation sites (aihub.cn, aigc.cn, explainx, gpts24) indexed Cue within 24 hours. Aggregating traffic is not aggregating money.
• K3 Chinese-language Cue / Manus 2.0 content. Bing's first page for manus cue was 7/7 Chinese content within 24 hours, and the bare token "cue" is absorbed by Chinese internet slang.
• K4 A consumer clone of Cue itself. Inbox issuance, number ranges, card issuing, persistent desktops and call answering are regulated infrastructure with 24/7 duty; failure harms user funds directly. An independent developer cannot hold this — same reasoning that killed the gateway/relay form last round.

6. If only one site gets built

Merge C1 and C4: "how much your agent spent, and what you allowed it to do." Two free entry points — credit calculator and permissions checker — with the paid side being billing-dispute and appeal templates plus credit-policy and permission-change alerts. Reasoning: the demand is multi-year install-base behaviour rather than new-term hype; the supply gap is verifiably empty (no calculator, no independent permissions checklist, official pricing not crawlable, no Cue documentation in the help centre); monetisation does not depend on a Manus affiliate that pays only credits; the failure cost is one page and one day; and it reuses the same Worker + D1 + detection base already scouted for candidate D. Cue's launch raises this line's credibility and timing — a security disclosure, and wallets and inboxes handed to consumers — it is not the whole reason for the line.

7. What this round could not measure (fix next round)

1. Search volume, KD and CPC are unknown for every term — no Ahrefs or Semrush account.

2. Google SERP and intitle/allintitle supply were not obtained: every google.com/search request from this exit returns 302 to a consent page, with or without CONSENT/SOCS cookies, and trends.google.com/api/* returns an error page. All supply claims therefore come from Bing, WebSearch result sets and vendor page structure, and KGR cannot be computed.

3. Bing degrades on multi-word queries: manus alternatives, manus credits explained, is manus im safe and manus pricing tiers returned byte-comparable result sets (manus.im + Baidu Baike + Wikipedia + aigc.cn), i.e. the phrase was not honoured; intitle: no longer works in Bing. Supply for those queries is recorded as unknown and the "About N results" figures are not quoted — the same number repeated across six different queries.

4. Reddit's JSON endpoints all 403 and old.reddit serves a login wall, so community evidence is headline-grade; cite it as such.

5. Mercury's card launch (FastCompany, 403) is unread. Ownership is confirmed only at headline level (archived CNBC titles); the $4B valuation and deal detail must go back to primary sources before being written into a page.

6. TrustMRR has no keyword search for unauthenticated callers (/api/ai/discovery?q= ignored byte-for-byte; /search?q= returns one identical 57,168-byte shell for all 10 tested terms), 34 coarse categories with no ai-agents/inbox/voice-agent bucket, and category pages cap at 30 with no pagination. Competitor samples are a sample, not a census.

8. Fourteen-day validation plan (if section 6 is adopted)

• D0–D2: ship two SSG entry pages (credit calculator, permissions checker). Each needs crawlable purpose, worked examples, stated limitations and an update date; Title/H1 use qualified terms; no implied officialdom.
• D2: submit sitemap and GSC, plus Bing Webmaster Tools; one inner page per root from 3.2/3.3 (credits not refreshing, why suspended, is manus safe, give your agent an email, agent identity security).
• D3–D7: re-run the 8 candidate roots through a keyword tool or a consented incognito browser to fill real volume, KD, CPC and intitle supply — closing the section 7 gaps.
• D7–D10: let GSC's actual queries drive either more pages or small Title edits only. Once a page is producing queries, small edits only — no full rewrites.
• D14: continue or stop against the kill criteria. No income promises: any RPM estimate must state its assumptions (traffic, language, ad slots, conversion).

9. iOS follow-up (requested after the first draft, same day)

9.1 Correction: C1's supply evidence moves down one notch

I pulled the documentation index manus.im/docs/llms.txt (200, 8,252 bytes, 58 pages) and manus.im/docs/introduction/plans.md (200, 4,049 bytes). Two findings:

• "Cue" appears 0 times across all 58 documentation pages — stronger than the help-centre check alone: Cue does not exist in official knowledge surfaces at all.
• The plans page already states the dashboard has Current Balance, Usage History, Spending Insights and "Alerts: Get notified when your credit balance is running low", and that "Add-on credits never expire". The three plans carry only qualitative wording (Free "Limited monthly credits", Pro "Generous monthly credit allocation", Team "Shared team credit pool") — no credit numbers, no per-task cost table, no expiry rules for monthly credits.

So the C1 gap narrows from "no alerts exist" to "no numbers and no rules, plus a docs-versus-reality mismatch": communities still report credits not refreshing, expired credits and a $698.89 refund followed by a 57,848-credit deduction, while the docs say add-ons never expire. C1's form changes accordingly — a dated, auditable credit-rules and numbers library, a billing-dispute evidence pack, cross-account ledger export — and drops building alerts the vendor already ships. It stays BUILD, with one added kill condition: once Manus publishes real numbers and expiry rules, only the ledger value remains.

9.2 The Cue iOS vacuum (IOS1 = WATCH)

Apple's own Search API (itunes.apple.com/search?entity=software, raw JSON archived for three storefronts): cue manus returns two unrelated board games in the US and zero results in CN and JP — Cue has no iOS app, matching "iOS coming soon after App Store review"; the guessed testflight.apple.com/join/cue is a 404.

The name is already crowded on the App Store: CUE Astrology (7,144 ratings), Cue: AI Note Taker (3,644, 44pixels), Cards Universe & Everything (10,441), Cue by Wonder Workshop, CUE Cinemas, plus a Japanese "Cue - AI搭載の文字起こし" (303). Autocomplete gives cue ios and cue ios app in DE, surrounded by other companies' apps. Meanwhile manus ios app, manus app download ios cluster in DE and manus testflight hits in us/gb/jp — "how do I install Manus on iPhone, how do I get beta" is already searchable behaviour. The Manus iOS app is real: id 6740909540, BUTTERFLY EFFECT PTE. LTD., released 2025-03-27, 38,329 US ratings, v26.17.0 updated on launch day 2026-09-28 with release notes reading "Buy a phone number or cloud computer for Manus".

Verdict: the iOS vacuum is genuine but worth only one inner page inside C2 plus a segmented email list (release date, TestFlight, iPhone feature deltas), because the moment it ships, media and ASO sites fill the query within hours — the window is shorter than C2's.

9.3 The iOS app slot: credit visibility (IOS2 = WATCH, and the only cash rail this round)

Demand is a cross-language cluster: ai subscription tracker, ai subscription usage tracker, ai spending tracker app, best ai spending tracker, ai budget tracker, ai expense tracker (hitting in us/gb/de/jp).

The decisive supply fact is that this niche has no winner yet: every indie AI-credit tracker on the App Store sits at zero to trivial traction — Limits: AI Usage Tracker 32 ratings (2026-07-14), Usage for Claude 5, Agent Meter: AI Usage 2, AI Limits & Reset Tracker 0, AI Usage Meter 0, AI Subscriptions 0, SubsTracker AI 0, Yula: Subscription Tracker AI 1 — while generic subscription management already has Rocket Money (394,391), Bobby (8,004) and SubPilot (4,866).

Three counter-arguments keep this at WATCH: ① the previous round killed the desktop equivalent (Usagebar at $9 one-off plus free open source at 3,577★); ② Apple ships subscription management and Screen Time itself; ③ Manus already claims low-balance alerts, and its API documentation describes task triggering only, with no usage or credit endpoint — meaning real numbers require manual entry or scraping the user's own dashboard, so the cost lands on human labour.

If built, the wedge is widget + Shortcuts plus billing-dispute evidence export (screenshot timeline matched to published terms), $3–8/mo through App Store subscription — the only rail this round that does not depend on a vendor affiliate. Kill: no way to obtain any provider's real credit data without manual entry within two months, or 30-day retention under 20%.

9.4 iOS forms killed outright

• A Cue client or third-party shell: no API, no listing, violates App Store 4.2/4.3 and has no data source.
• Bidding on the "cue" keyword in ASO: at least six live apps already hold the name; cost far exceeds return.
• An agent email/number app on iOS: numbers are $0.008 commodities, the inbox layer is already priced and crowded (AgentMail $0/20/200); iOS would be a shell with no differentiated data asset.

10. Method and reproducibility

Requests made this round: curl with a Chrome user agent through the local proxy for raw responses; suggestqueries.google.com/complete/search?client=firefox (5,066 rows); 22 Bing search queries with raw HTML saved; TrustMRR public API (/llms.txt, /api/ai/discovery, /startup/{slug}.md); Product Hunt product-page parsing; the HN Algolia API; and WebSearch. Every raw archive, script and aggregate JSON is downloadable below, and each figure should be locatable in those files. Methodology: the locally installed gefei skill (Mode 1 discovery, Mode 2 keyword validation, on-page audit framework).