Politics and Business contain subtopics like politics/elections and business/technology. Episodes are classified into topics automatically — fetch the taxonomy to power category navigation, route episodes to topic-specific feeds, or filter content by interest.
Available to MCP agents as
particle_topic_browse.Browse the taxonomy
Top-level topics:Response (truncated)
ancestry_path is an opaque hash-based path used for programmatic ancestor filtering. Slugs follow a parent/child convention for subtopics (e.g. politics/elections).
Navigate the tree
Get direct children of a topic by passingparent_id:
Response (truncated)
Find a topic by name
Passq to search topic names instead of walking the tree. Exact names come first, then names that start with q, then names that contain it, each ranked by story coverage:
Artificial Intelligence sits under Technology, Business and more), so read each result’s ancestry before picking one. To search within one branch, add parent_id (or ancestry_path_prefix): the search then covers that topic’s descendants, not only its direct children.
qneeds at least 2 characters and cannot be combined withancestry_path. A 2-characterq(such asAI) matches exact names and names that start with it; matching names that merely containqneeds at least one word of 3 or more characters (ai mlmatches exact names and prefixes only).- Name search covers topics with at least 5 story clusters. The long tail of single-story topics is still reachable by browsing with
parent_id. - Search pages reach the top 200 matches. Narrow
qor addparent_idto go further.
Get a single topic
The topic detail endpoint accepts any of three identifier forms in the path:- The encoded
idreturned by the list endpoint (e.g.4FZ4EFh) - The full
slug, including multi-level slugs with/(e.g.politics/elections) - The
ancestry_pathhash (e.g.GtizK,Qcqm_)
Response
ancestors— array of topic names from root to parent. Absent for root topics.ancestry— single human-readable breadcrumb string. Absent for root topics.total_children— total number of direct child topics. Always present (0 for leaves).children— the top direct children ordered by prominence (url_cluster_countdescending, ties broken by name). Capped at 100; whentotal_childrenexceeds 100, paginate the full set via/v1/topics?parent_id={id}.