| 0 |
| Ecosystem | 1 | 1 |
| Match Graph | 0 | 0 |
| Pricing | Free | Free |
| Capabilities | 14 decomposed | 12 decomposed |
| Times Matched | 0 | 0 |
Fetches OHLCV data, real-time quotes, and chip distribution across A-shares, HK, and US markets from a 7-tier provider hierarchy (EFinance → AkShare → Tushare → Pytdx → Baostock → YFinance → Longbridge) with automatic circuit-breaker failover and data validation. Each provider is prioritized by reliability and latency; if one fails or times out, the system transparently falls back to the next tier without interrupting the analysis pipeline.
Unique: Implements a 7-tier provider priority system with automatic circuit-breaker failover rather than simple round-robin or single-provider approaches; EFinance (Priority 0) is free and near real-time, eliminating the need for paid APIs for basic analysis. The system validates data quality and latency at each tier before falling back, ensuring analysis uses the freshest available data.
vs alternatives: Outperforms single-provider solutions (e.g., yfinance-only) by guaranteeing data availability across market disruptions; more cost-effective than commercial data APIs (Bloomberg, FactSet) by leveraging free Chinese data sources (AkShare, Tushare) as primary tiers.
Routes stock data through a unified LiteLLM interface to multiple LLM backends (Gemini, Claude, DeepSeek, OpenAI, Ollama) with embedded trading philosophy rules and 11 built-in strategies (Bull Trend, Golden Cross, Wave Theory, etc.). Each strategy is implemented as a 'skill' that guides the LLM's reasoning via system prompts and structured output templates, ensuring analysis adheres to quantitative trading principles rather than generating arbitrary commentary.
Unique: Embeds 11 quantitative trading strategies as reusable 'skills' with LLM-guided reasoning rather than hardcoded technical indicators; uses LiteLLM abstraction to support 5+ LLM backends (Gemini, Claude, DeepSeek, OpenAI, Ollama) with unified interface, enabling provider-agnostic analysis and cost optimization. Trading philosophy rules are enforced via system prompts, ensuring recommendations align with quantitative discipline.
vs alternatives: More flexible than rule-based technical analysis (TA-Lib) because LLM reasoning adapts to market context; more disciplined than pure LLM chat because strategies constrain reasoning to specific trading frameworks. Supports local Ollama deployment for zero-cost inference, unlike cloud-only solutions (ChatGPT, Gemini API).
Integrates with messaging platform bots (Telegram Bot API, Discord Webhooks, WeChat Work Bot API) to enable interactive analysis queries and report delivery. Users can send commands to the bot (e.g., '/analyze AAPL' or '/portfolio') and receive analysis results directly in the chat. The bot supports slash commands, inline buttons for quick actions (buy/sell/hold), and rich message formatting (embeds, cards, rich text). Bots run as separate processes and poll for messages or listen to webhooks.
Unique: Implements native bot integrations for Telegram, Discord, and WeChat Work (Chinese platform) with slash commands, inline buttons, and platform-specific rich formatting. Enables interactive analysis queries directly in chat without leaving the messaging app. Supports group chat usage with optional rate limiting to prevent abuse.
vs alternatives: More convenient than web UI because users don't need to open a browser; analysis is delivered in their existing chat workflow. More interactive than report-only notifications because users can query analysis on-demand and execute actions via inline buttons. Supports Chinese platforms (WeChat Work) natively, unlike most Western financial APIs.
Enables deployment of the analysis system to GitHub Actions, a free CI/CD platform that runs workflows on a schedule (cron) or on-demand. The system is packaged as a Docker container or Python script that runs in the GitHub Actions environment, fetches stock data, runs analysis, and sends notifications. No server hosting is required; GitHub Actions provides free compute for public repositories (2000 min/month) and paid plans for private repositories. Workflows are defined in YAML and version-controlled alongside the code.
Unique: Leverages GitHub Actions free tier (2000 min/month for private repos, unlimited for public) to run scheduled analysis without paying for cloud hosting. Workflows are defined in YAML and version-controlled alongside code, enabling reproducible deployments. Integrates with GitHub Secrets for secure credential management.
vs alternatives: More cost-effective than cloud-based scheduling (AWS Lambda, Google Cloud Scheduler) because GitHub Actions is free for public repos and cheap for private repos. More maintainable than local cron jobs because workflows are version-controlled and visible in the GitHub UI. More scalable than single-machine deployments because GitHub Actions can run multiple workflows in parallel.
Packages the entire analysis system (backend, frontend, database, notification services) as a Docker Compose stack that can be deployed locally or to cloud platforms (AWS, Google Cloud, DigitalOcean). The Compose file defines services for the FastAPI backend, React frontend, PostgreSQL database, and optional Redis cache. Deployment is as simple as 'docker-compose up', with all dependencies and configuration managed by the Compose file. Supports environment-based configuration (dev, staging, prod) via .env files.
Unique: Provides a complete Docker Compose stack (backend, frontend, database, cache) that enables single-command deployment ('docker-compose up') without manual service setup. Supports environment-based configuration (dev/staging/prod) via .env files. Enables local development with the same stack as production, reducing environment drift.
vs alternatives: More convenient than manual service setup because all dependencies are defined in a single file. More reproducible than cloud-native deployments because the stack is version-controlled and can be deployed identically across environments. More accessible than Kubernetes because Docker Compose has a lower learning curve and is suitable for small to medium deployments.
Enables deployment of the analysis system as a systemd service (Linux) or cron job that runs on a local machine or VPS. The system runs continuously as a background service, polling for scheduled analysis times and executing them. Systemd provides service management (start, stop, restart, status) and automatic restart on failure. Cron provides simple time-based scheduling without a persistent service. Both approaches require minimal infrastructure (just a Linux machine) and zero cloud hosting costs.
Unique: Provides both systemd service and cron job deployment options for Linux, enabling simple self-hosted scheduling without cloud infrastructure. Systemd provides service management (start/stop/restart) and automatic restart on failure. Cron provides simple time-based scheduling. Both approaches require minimal setup and zero cloud hosting costs.
vs alternatives: More cost-effective than cloud-based scheduling because it runs on a cheap VPS or local machine. More reliable than manual script execution because systemd provides automatic restart and monitoring. More flexible than GitHub Actions because it supports long-running services and persistent state.
Aggregates news, risk alerts, earnings data, and capital flow from 4+ specialized search APIs (Anspire, Tavily, Bocha, SerpAPI) and enriches the LLM analysis context with up-to-date fundamental information. The search service queries for stock-specific news, regulatory filings, insider trading, and market sentiment, then embeds results into the LLM prompt as structured context to ground recommendations in real-world events rather than historical price patterns alone.
Unique: Implements a multi-API search strategy (Anspire, Tavily, Bocha, SerpAPI) with fallback logic similar to data fetching, ensuring news availability even if primary search API fails. Structures search results as context blocks for LLM prompts, enabling the AI to cite specific news events in recommendations. Supports market-specific search (A-shares, HK, US) with appropriate query formatting per market.
vs alternatives: More comprehensive than single-source news APIs (e.g., NewsAPI alone) because it aggregates multiple providers and includes earnings/risk data. More efficient than manual news monitoring because search is automated and results are pre-structured for LLM consumption. Supports Chinese market news (via Anspire, Bocha) unlike most Western financial APIs.
Implements a multi-agent system that decomposes complex investment questions into sub-tasks, each handled by specialized agents (technical analyst, fundamental analyst, risk manager, sentiment analyzer). Agents communicate via a shared context store and iteratively refine recommendations through multi-turn reasoning. The orchestrator routes user queries to appropriate agents, aggregates their outputs, and synthesizes a final recommendation with consensus scoring and dissent tracking.
Unique: Implements agent specialization with explicit role separation (technical analyst, fundamental analyst, risk manager, sentiment analyzer) rather than a single monolithic LLM; agents share context via a structured store and produce scored outputs that are aggregated with dissent tracking. This enables explainable AI where users can see which agents support/oppose a recommendation and why.
vs alternatives: More transparent than single-LLM analysis because users see reasoning from multiple specialized perspectives. More robust than simple prompt engineering because agent disagreement surfaces uncertainty. Enables cost optimization by routing simple queries to cheaper agents and complex queries to more capable (expensive) models.
+6 more capabilities
Crawls 11+ heterogeneous platforms (Zhihu, Weibo, Bilibili, Twitter, Reddit, HackerNews, etc.) and RSS feeds using platform-specific scrapers, normalizes disparate data schemas into a unified NewsItem model, and deduplicates content across sources using fuzzy title matching and URL canonicalization. The system maintains platform-specific metadata (rank, heat value, engagement metrics) while presenting a single normalized feed, enabling cross-platform trend detection that would be invisible within individual platform silos.
Unique: Implements platform-specific crawler modules with unified NewsItem schema and fuzzy deduplication across 11+ heterogeneous sources (Chinese + international), rather than relying on single-platform APIs or generic RSS parsing. Maintains platform-specific metadata (rank × 0.6 + frequency × 0.3 + platform hot value × 0.1) for weighted hotspot scoring.
vs alternatives: Covers more platforms (especially Chinese social media) with deeper metadata extraction than generic RSS aggregators, and provides unified deduplication across sources unlike single-platform monitoring tools.
Implements a multi-stage filtering pipeline that matches news items against user-defined keywords using regex patterns, required word lists, and excluded word lists. The system applies frequency-based scoring (keyword occurrence count) combined with platform hotspot weights to rank filtered results. Configuration is stored in frequency_words.txt with support for regex patterns, AND/OR/NOT boolean operators, and per-keyword weighting. Filtering occurs at collection time (reducing storage) and again at report generation time (enabling dynamic reconfiguration without re-crawling).
Unique: Combines regex pattern matching with frequency-based scoring and platform hotspot weighting (rank × 0.6 + frequency × 0.3 + platform hot value × 0.1) in a two-stage pipeline (collection-time and report-time filtering). Supports dynamic reconfiguration without re-crawling by applying filters at report generation.
TrendRadar scores higher at 58/100 vs daily_stock_analysis at 41/100. daily_stock_analysis leads on quality, while TrendRadar is stronger on adoption and ecosystem.
Need something different?
Search the match graph →© 2026 Unfragile. Stronger through disorder.
vs alternatives: More flexible than simple keyword matching (supports regex and boolean logic) and more efficient than semantic filtering (no LLM overhead), making it suitable for real-time filtering at scale.
Detects newly emerged topics by comparing current crawl results against historical data stored in the system. Topics are marked as 🆕 (new) if they appear for the first time in the current crawl or if their hotspot rank increased significantly compared to previous crawls. The system tracks topic emergence velocity (how quickly a topic rises in rankings) and flags topics with unusual acceleration. New topic detection is performed at report generation time, enabling dynamic detection without re-crawling. The system maintains a historical hotspot index for comparison.
Unique: Detects new topics by comparing current hotspot rankings against historical data, marking topics with significant rank increases as 🆕. Tracks emergence velocity to distinguish breaking news from sustained trends.
vs alternatives: More efficient than semantic similarity detection (no LLM overhead) and more accurate than simple first-appearance detection (accounts for re-emerging topics), but requires historical baseline data.
Provides a web-based UI for editing TrendRadar configuration files (config.yaml, frequency_words.txt, timeline.yaml) with real-time validation and preview. The editor supports: (1) syntax highlighting for YAML and regex, (2) validation of keyword patterns (regex compilation check), (3) preview of filtered results based on current keyword configuration, (4) drag-and-drop channel configuration, (5) schedule preview (shows next 10 execution times). Changes are validated before saving, preventing configuration errors. The editor is optional; users can edit config files directly.
Unique: Provides web-based configuration editor with real-time validation, regex preview, and schedule visualization. Enables non-technical users to configure TrendRadar without editing YAML files.
vs alternatives: More user-friendly than manual YAML editing and provides validation feedback, but adds operational complexity compared to file-based configuration.
Integrates LiteLLM to provide vendor-agnostic AI analysis and summarization of filtered news items. Users configure their preferred LLM provider (OpenAI, Anthropic, Ollama, local models, etc.) once in config.yaml, and the system automatically routes analysis requests to that provider. The AI analysis capability includes: (1) automated summarization of long articles into key points, (2) sentiment analysis (positive/negative/neutral), (3) trend prediction based on historical patterns, and (4) custom analysis prompts. Analysis results are cached to avoid redundant API calls and can be pushed directly to notification channels.
Unique: Uses LiteLLM abstraction layer to support any LLM provider (OpenAI, Anthropic, Ollama, local models) with single configuration, enabling provider switching without code changes. Caches analysis results to reduce redundant API calls and costs.
vs alternatives: More flexible than hardcoded OpenAI integration (supports any LiteLLM provider) and cheaper than dedicated sentiment analysis APIs (can use local models), but slower than rule-based sentiment analysis.
Leverages LiteLLM to translate news content from source languages (primarily Chinese) to target languages (English, etc.) on-demand. The system detects source language automatically (via langdetect or similar), caches translations to avoid re-translating identical content, and batches translation requests to reduce API calls. Translations are stored alongside original content, enabling bilingual reports and multi-language notification delivery. Translation can be triggered at collection time (all news) or report time (only filtered news).
Unique: Implements provider-agnostic translation via LiteLLM with automatic language detection, content-based caching, and batch request optimization. Stores translations alongside originals for bilingual report generation.
vs alternatives: More flexible than dedicated translation APIs (supports any LiteLLM provider) and cheaper than commercial translation services when using local models, but slower than specialized translation APIs.
Implements a notification abstraction layer supporting 9+ delivery channels (WeChat, WeWork, Feishu, Telegram, Email, ntfy, Bark, Slack, etc.). Each channel has a provider-specific formatter that converts normalized news items into channel-appropriate messages (e.g., WeChat card format, Telegram markdown, email HTML). The system batches notifications atomically—all news items for a report are sent as a single batch to each channel, ensuring consistency and reducing API calls. Message formatting respects channel constraints (character limits, attachment limits, etc.) and supports templating for customization.
Unique: Implements atomic message batching across 9+ heterogeneous channels with provider-specific formatters and constraint-aware truncation. Single configuration enables simultaneous delivery to WeChat, WeWork, Feishu, Telegram, Email, ntfy, Bark, Slack, etc. without code changes.
vs alternatives: Supports more channels (especially Chinese platforms like WeWork, Feishu) than generic notification services, and batching reduces API calls and spam compared to per-item notifications.
Exposes TrendRadar's data and analysis capabilities as an MCP server, enabling AI agents and LLM applications to query trends, perform analysis, and generate insights through natural language. The MCP server implements tools for: (1) querying filtered news by keyword/date/platform, (2) retrieving trend statistics and hotspot rankings, (3) running custom analysis on news subsets, (4) generating reports in various formats. Clients (Claude, other LLM agents) can invoke these tools via MCP protocol, enabling conversational exploration of trends without direct database access. The server maintains state across multiple requests, allowing multi-turn conversations about trends.
Unique: Implements full MCP server exposing trend data and analysis tools to LLM agents, enabling conversational queries and multi-turn analysis workflows. Maintains state across requests and supports complex tool invocations (filtering, analysis, report generation).
vs alternatives: Enables conversational access to trends (vs. API-only access) and integrates with LLM agent workflows (vs. standalone tools), but adds operational complexity compared to simple REST APIs.
+4 more capabilities