Use cases & endpoints
Central bank speeches dataset — searchable and cited
Speeches are where policymakers say the things a committee statement cannot. They are also where the earliest signals of a shift usually appear, delivered at a conference in front of an audience of two hundred people and a webcast nobody watched.
As a corpus they are scattered by construction: each institution publishes its own officials, regional banks maintain separate archives, and the format ranges from clean HTML to a scanned PDF of prepared remarks. Building a usable dataset means collecting across institutions and normalizing the metadata that makes speeches comparable — who spoke, in what role, where, and when.
Hindcast maintains that corpus with delivery timestamps preserved, roles recorded as they stood at the time, and the text chunked so retrieval returns an argument rather than a document. Every passage keeps its link back to the published original.
hindcast — session
previewhindcast> speeches mentioning a topic across several banks this year
→ tool: cb_speeches { banks:["..."], query:"...", period:"..." }
✓ passages with speaker, institution, venue and date
source: institutional speech archives
What's covered
- Speeches across the Fed system, BCB, ECB, BoE, BoJ and LatAm banks
- Speaker role recorded as of the delivery date
- Venue and event captured alongside the text
- Original language preserved for non-English remarks
- Passage-level chunks with links to the source document
- Delivery timestamps for as-of questions about what had been said
Join the waitlist — this page's dataset is already selected.
Questions
Why keep the speaker's role as of the delivery date?
Because it changes the weight of the words. The same person speaking as a regional president and later as a governor is not making an equivalent statement, and a corpus that only stores current roles quietly rewrites that history.
Are speeches scored for tone?
No. The dataset returns text and metadata; tone scoring is a modeling choice with many defensible variants, and baking one into the data would make the others harder to build.
Related
Join the waitlist. Vote the roadmap. First in, first served.