Skip to content

add Fathom API doc to engine/ - #2

Merged
shawnla90 merged 1 commit into
shawnla90:mainfrom
dan-sheehan:engine/call-intelligence
Jun 1, 2026
Merged

shawnla90 merged 1 commit into
shawnla90:mainfrom
dan-sheehan:engine/call-intelligence

Conversation

@dan-sheehan

Copy link
Copy Markdown
Contributor

What this adds
engine/fathom.md — a tool doc for Fathom's public API, following the same structure as apollo.md and apify.md.

GTM problem it solves
Fathom is the easiest way for an individual GTM operator to get programmatic access to their own call transcripts. Unlike most conversation intelligence platforms, the API is available on the free tier with no admin gate, so individual ICs can start building per-account intelligence workflows without waiting on procurement.
The doc covers:

Auth, endpoints, and a batch pull pattern that filters meetings by company domain
Four GTM use cases: per-account intelligence (CSM account wiki), churn signal detection, objection pattern mining, and handoff briefings
The MCP endpoint for Claude Code integration
Rate limiting, pagination, and known gotchas

Why Fathom first
I started with Fathom rather than Gong because the individual-API-key access makes it approachable for ICs and smaller teams. Gong, Chorus, Fireflies, etc. could follow the same pattern in future docs.

Validation
Tested against Fathom's live API with an active account. Response shape, auth header format, and pagination behavior match what's documented above.

@shawnla90

Copy link
Copy Markdown
Owner

Hey bud, sorry I'm only seeing this now. I do have a Fireflies API script in there, but I have used Fathom and it's just as easy, so happy to merge this and share it.

@shawnla90
shawnla90 merged commit 047bf5a into shawnla90:main Jun 1, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants