“A Twitter feed that's just your favorite search terms, all combined together.”

FeedFusion 9000

ALREADY EXISTS, YOU'RE LATE
2/10
“You just described TweetDeck columns, which Twitter killed, then X brought back behind a $8/month paywall. Congrats.”

An agent that monitors multiple Twitter/X search queries simultaneously and merges them into a single unified, chronological feed.

This is so solved it hurts. TweetDeck was doing this in 2008. The only reason it feels like a problem is because Elon paywalled the good version. You're not identifying a gap in the market — you're identifying a gap Elon intentionally created to extract $8/month from you.

whycantwehaveanagentforthis.com
Try Your Own Problem

Viability Analysis

Market Demand55
Tech Feasibility95
Competition85
Monetization30
AI Disruption Risk40
Fun Factor45

Pros & Cons

What's going for it

X's API paywall ($100/mo for basic access) has created genuine user frustration and willingness to pay for alternatives
Simple enough to build in a weekend — low technical risk, fast to validate
Could expand beyond X to Bluesky, Mastodon, Threads — making it platform-agnostic is a real differentiator
Niche power users (journalists, researchers, traders) will pay for reliable keyword monitoring

What's against it

X's API pricing ($100+/month) will eat your margins before you get 10 paying customers
X can and will change API terms overnight — your entire business evaporates with one policy update
TweetDeck still exists behind X Premium — you're competing with the original for $8/month
Every developer who lost TweetDeck already built their own version of this — your TAM is 'people who can't Google'

Who You're Up Against

TweetDeck (X Pro)saas

Multi-column Twitter dashboard with search feeds — now paywalled at X Premium

high
Hootsuitesaas

Social media dashboard with keyword stream monitoring across platforms

medium
Tweetbot / Ivory (Tapbots)saas

Third-party Twitter/Mastodon clients with list and search management — killed by API pricing

low
Nittersaas

Open-source Twitter frontend — repeatedly killed by X's API crackdowns

low
Fedica (formerly Tweepsmap)saas

Twitter analytics and monitoring tool with keyword stream features

medium

Open Source Alternatives

n8n Twitter/X integrationsopen source

Workflow automation that can poll multiple X search endpoints and merge into one feed

medium
RSS-Bridgeopen source

Converts Twitter searches to RSS feeds — combine in any RSS reader for free

high
Huginnopen source

Self-hosted agent system that can monitor Twitter searches and aggregate them

medium

When Will Big AI Kill This?

Most Likely Killer

X (Twitter)

Timeline: Already happened — and will happen again the moment you get traction

Now3mo6mo1yr2yrNever

How They'll Do It

They'll either revoke your API access, change rate limits, or just... add the feature back to X Premium to undercut you

Your Survival Strategy

Go multi-platform immediately. If your product works on Bluesky + Mastodon + X, killing your X access only hurts you a little instead of killing you entirely

Confidence

92%

If You're Crazy Enough to Build It

Solo Dev Time

1-2 weekends for MVP, 2 weeks for something you're not embarrassed to show people

Team Size

One developer who has already been burned by the Twitter API before

Estimated Cost

$100-300/month in X API fees plus ~$20/month infra — the API will cost more than your server

Tech Stack

Next.jsX API v2Bluesky AT ProtocolRedis for feed cachingVercel

Want to actually build this?

Work with me to ship it.

Survived the verdict? Good. Let's build the damn thing.

Got another problem that needs an agent?

Roast My Problem

whycantwehaveanagentforthis.com