How this works
A continuously growing knowledge graph built from podcast RSS metadata. No audio is ever downloaded, and no transcripts are analysed yet — this is what metadata alone can support.
The pipeline
RSS feed → conditional GET (ETag / Last-Modified) ← unchanged feed = 304, no bytes → normalise episode metadata → extract entities (rules + confidence) → resolve identities (aliases, variants) → extract relationships → Cloudflare D1 → this site, a REST API and an MCP server
Why you can trust a claim
Every relationship is stored with the episode, the exact source text, the extraction rule and a confidence score. Nothing is invented: if you see an edge, there is a quote behind it. Open the “evidence” disclosure on any connection to read it.
What is in the graph
Agents welcome (private)
The same graph is exposed as an MCP server (POST /mcp) with semantic tools such as search_entities, get_related_entities, get_entities_across_podcasts and find_path_between_entities, plus a JSON API under /api. Both are private: disabled unless a WORLDMAP_API_TOKEN is configured, and then requiring it as a bearer token.
Honest limits
Extraction is rule-based, so recall on free-form prose is limited and a link with an uninformative domain can be typed wrongly. Confidence, the extractor name and the source text are stored precisely so a later semantic pass can correct them, and processing can be re-run at any time without duplicating anything.
Book links
Book pages link out to a source for the ISBN (Open Library / Google Books / Wikidata) and, where available, to Amazon and Goodreads. As an Amazon Associate we earn from qualifying purchases; the Goodreads link is a plain reference — Goodreads does not run an affiliate program.