# The Connecticut River Monster

Page: https://stenobird.com/podcast/new-england-legends-podcast-726559/the-connecticut-river-monster
Text version: https://stenobird.com/podcast/new-england-legends-podcast-726559/the-connecticut-river-monster.md
Podcast: [New England Legends Podcast](https://stenobird.com/podcast/new-england-legends-podcast-726559)
Published: 2026-04-16T14:30:00+00:00
Episode link: https://newenglandlegends.libsyn.com/the-connecticut-river-monster
Audio file: https://dts.podtrac.com/redirect.mp3/pscrb.fm/rss/p/traffic.libsyn.com/secure/newenglandlegends/NEL442_CTRiverMonster.mp3?dest-id=1244321
Processing state: not_requested
JSON: https://stenobird.com/v1/public/podcasts/new-england-legends-podcast-726559/episodes/the-connecticut-river-monster
Duration seconds: 1127

## Resource

In Episode 442, Jeff Belanger and Ray Auger investigate the Connecticut River in Westminster, Vermont, searching for a 100-foot-long monster serpent that's been witnessed along the river for centuries. One of the earliest sightings led to a religious conversion to a historical figure. Is the beast still out there? See more here: https://ournewenglandlegends.com/podcast-442-the-connecticut-river-monster/ Listen ad-free plus get early access and bonus episodes at: https://www.patreon.com/NewEnglandLegends Buy Jeff Belanger's new book Wicked Strange New England on Amazon: https://amzn.to/4lMkM3G Check out Jeff's new underground publication Shadow Zine! https://shadowzine.com/ Listen to Ray's Local Raydio! https://localraydio.com/

## Actions

- request_transcript: `POST https://stenobird.com/v1/public/podcasts/new-england-legends-podcast-726559/episodes/the-connecticut-river-monster/transcription-requests` — Idempotently request low-priority transcript generation for this episode.
- read_markdown: `GET https://stenobird.com/podcast/new-england-legends-podcast-726559/the-connecticut-river-monster.md` — Read the agent-friendly Markdown representation of this episode resource.

A page view does not enqueue transcription. Agents should invoke `request_transcript` explicitly when they need this episode processed.

## Transcript

Full transcripts are not published on public pages unless there is a clear rights basis.