Market intelligence for your AI teams.
Content Radar fetches public content — trending searches, best-seller rankings, developer posts, job postings, tenders and bounties — from 76 verified sources into one normalized store. Every team reads it; you see the raw rows, the charts and a daily brief.
The AI workflow
From your goal to work you can review.
You direct
Public content, collected once
Content Radar gathers permitted public rows into the shared store.
AI works
AI analysts find the patterns
The Market Analyst and other team agents read the store, interpret trends and prepare cited briefs.
You inspect
Evidence you can inspect
See the source rows, charts, watch terms and the brief together before deciding what to do.
Public content only, by rule
An anonymous client with no cookies sees exactly what the radar sees. Never behind a login, never anyone's session, no CAPTCHA solving. robots.txt is honoured on every request, one HTTP layer rate-limits per host, and a source whose terms forbid automated access is listed but never fetched.
Raw rows, charts, and an AI analyst’s cited brief
The Market tab shows the same data three ways: the raw rows (title, source, time, link), charts — rows per day, regions, top topics — and a written brief from the AI Market Analyst that quotes at most twelve words per item and links the source. Add watch terms and you get a daily series of hits per term.
One evidence store for every AI team
The Social team reads it for what communities are discussing; the Deals and Jobs teams read the postings; the Ecommerce team reads the trend feeds and best-seller rankings; the Sales team reads registers and directories. These AI agents never fetch anything themselves — they read the store through one tool, so policy is enforced in one place.
How it runs
Sources are audited
A source goes live only after an auditor verified it three times — terms, robots, output.
Fetched on a cadence
Each source has its own cadence and page budget. The shared HTTP layer applies per-host rate limits, respects Retry-After and uses bounded retries; sources return normalized rows.
Never wiped
Rows accumulate; tripwires catch a source that suddenly returns nothing, and a watchdog repairs it.
Read by every team
Raw rows, charts and briefs in the Market tab of each suite.
Questions, answered
Does it log in anywhere?
No. It fetches only what an anonymous visitor can see, honours robots.txt, and lists — but never fetches — sources whose terms forbid automation.
Does it copy the content?
It distils. Items are stored trimmed, agents quote at most twelve words and always link the source.
Can I add my own terms or sources?
Watch terms, yes — per suite, with a daily series. New sources go through the onboarding audit first.
What do watch terms help me see?
Watch terms let you follow mentions of a topic across collected public items over time. Use the daily hit series alongside the underlying rows and source links to understand what changed.
Why do sources have different freshness or coverage?
Sources use different fetch cadences and expose different public information. A degraded or unavailable source can reduce fresh results; inspect source status and item timestamps when comparing trends.
Should I read the rows or just the analyst brief?
Use the brief for an overview, then inspect the raw rows and cited links for decisions that matter. Charts and summaries describe the collected data, not the entire market or a guarantee of demand.
Decide from data, not from a hunch
Seventy-six public sources, one store, a brief every day.