Radar Makes Podcasts Searchable and Usable by AI Agents

Particle, the AI newsreader startup founded by former Twitter engineers, launched a product called Radar on August 26, 2026 that indexes more than 130,000 podcasts and makes their contents queryable by AI agents through a search API and a native MCP server. The announcement, first reported by TechCrunch's Sarah Perez, targets a gap that has quietly grown more expensive as agent-driven workflows have scaled: spoken audio has no equivalent of a web crawler.

What Changed

Radar is not Particle's first product — the company previously built an AI-powered news reader — but it represents a significant pivot toward developer and enterprise infrastructure. The new platform transcribes every episode it indexes, attaches speaker labels and timestamps, extracts named entities (people, companies, brands, topics), and exposes all of it through both a web interface and a machine-readable API. Multiple reports confirm the same scale figure: 130,000 shows covered at launch, with roughly 20,000 fresh episodes ingested every day.

The podcast catalog is not random. Radar covers all 200 shows in the Apple Top 200 across 135 content verticals — a deliberate choice that gives it signal density where podcast audiences are already concentrated. That scope matters for enterprise buyers who need reliable coverage of specific sectors, not just best-effort crawling of whatever RSS feeds are publicly reachable.

Pricing is tiered. AI Chat Daily confirms a $29-per-month per-seat entry point, a $399-per-month business plan covering 20 seats, and custom pricing for direct API integrations at scale. The business tier is positioned for teams that want to build alert workflows or search dashboards; the API tier is for organizations that want to embed the data into their own agent pipelines. Hedge funds are named as early customers in both the primary TechCrunch report and corroborating coverage — a detail worth pausing on, because it anchors the value proposition in a sector that already pays for structured financial data and has obvious reasons to want unstructured audio from earnings calls, analyst interviews, and investment-themed podcasts translated into something a model can act on.

How It Works

The core technical challenge Radar solves is not transcription — automated speech recognition has been commodity-grade for years. The harder problem is making transcripts semantically useful rather than just searchable by keyword. Radar's approach combines three layers: raw transcription with accurate speaker diarization (assigning words to specific voices), entity extraction that understands context (not just that a company name appears, but who mentioned it, in what framing, and when), and a retrieval layer that lets downstream systems query across all of that structure.

The MCP server is the detail developers will care most about. Model Context Protocol is an open standard for connecting AI agents to external data and tool providers, and shipping Radar with a native MCP integration means any agent that speaks MCP — including Claude Code and other Claude-based workflows — can query Radar's podcast index without a custom integration layer. Particle's partnership with Exa, a web search API already used in agent grounding workflows, is worth noting here: multiple sources confirm the Exa connection, and the combination of Exa's text-web coverage with Radar's audio coverage represents a grounding stack for agents that covers both modalities. The alerting layer — mentions delivered via email, Slack, or webhook, filterable by guest, topic, or chart rank — is aimed at the human interface side of the same data.

The ingestion pipeline is continuous rather than batch. Twenty thousand episodes per day is a large enough throughput that coverage of breaking news, earnings calls, and live event commentary stays current on a timescale that matters for real-time research agents. That freshness requirement is presumably what drove Particle to build a dedicated infrastructure play rather than licensing an existing transcription service and indexing the output.

What It Means for Developers

The honest framing here is that Radar is solving a problem that agent builders have been working around rather than solving. Web retrieval, vector databases, and RAG pipelines are all built on text. When an agent needs to answer a question like "what did the CFO of that company say about margins last quarter," it can search earnings transcripts if those transcripts exist as text — but it cannot, without something like Radar, search the podcast interview where the CFO said the same thing off-script in a more candid register. Our read is that the audio blind spot is more significant than it looks from a pure data-coverage angle: spoken-word content is often less guarded, more timely, and more opinionated than the same person's written or official communications. That asymmetry is exactly why hedge funds are early adopters.

For teams building research or market-intelligence agents, the MCP integration is the lowest-friction path to testing Radar's coverage. Rather than building a custom API client and parsing JSON responses, an agent can be configured to call Radar as a tool with the same syntax it uses for any other MCP-compatible data source. The $29/seat entry point makes individual developer experimentation financially low-stakes; the custom API tier is where Particle is probably making its real revenue from the hedge fund cohort.

What to watch: Newsgab's coverage raises a fair concern about nuance flattening — podcast conversations are inherently meandering, and converting a 90-minute interview into indexed, timestamped entity-tagged clips necessarily compresses context. Whether that compression introduces meaningful distortion in high-stakes use cases (legal research, financial analysis, political coverage) is an open question that Radar's entity extraction approach doesn't fully resolve. The system knows who said what, but it cannot yet reliably score the confidence or irony register of the claim. That limitation matters less for alert-and-monitor workflows than it does for agent tasks that need to reason about speaker intent.

Sources