earningscalls.dev vs AlphaSense

Earnings call transcripts compared: pricing, coverage and API access. Competitor figures taken from their own public pages on July 30, 2026.

The short version

AlphaSense: Enterprise research platform with AI search over calls, filings and broker research.

earningscalls.dev: one job, done deeply. 248,529 earnings call transcripts from 12,702 companies, free to read on the site, available as JSON through the earnings call API or to AI agents through the MCP server, from $24.99/month.

Genuinely a different tier of product. If your team needs broker research, expert-network calls and an enterprise workflow, AlphaSense earns its price. If you need earnings call text in your own pipeline, an annual seat contract is a heavy way to buy a JSON feed - that is the gap we fill at $24.99/month with no sales call.

AlphaSense vs earningscalls.dev: side by side

earningscalls.devAlphaSense
Price to start Pro $24.99/mo (5,000 requests), Ultra $39.99 (25,000), Enterprise $299 (100,000) Quote-only, no public price list. Reported seat pricing runs roughly $10,000-$20,000 per user per year, with tiers that include expert-call transcripts reported above $40,000 per seat
Free access Every transcript free to read on the site, no account. Free API tier via RapidAPI (50 requests/month) No self-serve free tier; access starts with a sales conversation
Earnings call transcripts Core product: 248,529 calls from 12,702 companies across 70 countries Deep, and paired with broker research and expert calls that we do not carry at all
Speaker segments Yes - every call split by speaker turn, tagged executive/analyst/operator, ~93% named Yes, inside their platform UI
MCP / AI-agent access Yes - hosted MCP server included in every plan Not advertised as an open MCP endpoint
Commitment Monthly, self-serve checkout, cancel anytime Annual contracts, seat-based

AlphaSense details are quoted from www.alpha-sense.com/, checked July 30, 2026. Pricing and packaging change - verify on their site before deciding. If you spot something out of date here, tell us at support@earningscalls.dev and we will correct it.

Which one fits your use case