earningscalls-dev · Terms of Service

earningscalls-dev terms of service

Read from earningscalls-dev's own page on 2026-11-09. 16 statements quoted word for word; anything the page does not say is shown as unstated, never guessed. APIs.io verifies none of it.

Effective date

Updated October 9, 2026

Permitted use

summary: Personal analysis, integration and decision support
Subscribers may use the data and API for: Personal analysis and research Integration into proprietary applications and internal tools Decision support based on earnings call data
Read from earningscalls-dev's own page on 2026-11-09
summary: Store and cache responses while subscribed
While the subscription is active, Customer may store and cache API responses for as long as its processing requires, including in a persistent search index, embedding store or internal archive used by Customer's own analyses and application features.
Read from earningscalls-dev's own page on 2026-11-09
summary: Show derived analyses and short excerpts to end users
Customer's products, tools and agents may present to End Users, and to any agent or system acting for an End User, only Customer's own analyses, summaries, evaluations, derived results and selected quotation excerpts.
Read from earningscalls-dev's own page on 2026-11-09

Prohibited use

summary: Redistribution or resale of data
Resell, syndicate, or redistribute the data, in whole or substantial part, to third parties — directly or indirectly, including via derivative datasets — without our prior written consent.
Read from earningscalls-dev's own page on 2026-11-09
summary: Proxy or relay operation
Operate the Service as a proxy or relay , i.e., re-expose the EarningsCalls API to third parties under another brand, via another API gateway, or as a tool, function or connector that a third-party agent or system can call.
Read from earningscalls-dev's own page on 2026-11-09
summary: Exposing raw transcripts to end users
Expose raw transcript content to End Users or their agents.
Read from earningscalls-dev's own page on 2026-11-09
summary: Fanning out one key across end users
Fan out a single API key across many independent end-users in a manner that materially evades tier quotas
Read from earningscalls-dev's own page on 2026-11-09
summary: Bulk scraping of the archive
Systematically scrape or bulk-download the archive in a way inconsistent with normal application use
Read from earningscalls-dev's own page on 2026-11-09
summary: Reverse engineering
Reverse engineer, decompile, or attempt to extract source code from the Service
Read from earningscalls-dev's own page on 2026-11-09

Caching

stance: conditional
While the subscription is active, Customer may store and cache API responses for as long as its processing requires, including in a persistent search index, embedding store or internal archive used by Customer's own analyses and application features.
Read from earningscalls-dev's own page on 2026-11-09

Redistribution

stance: prohibited
Resell, syndicate, or redistribute the data, in whole or substantial part, to third parties — directly or indirectly, including via derivative datasets — without our prior written consent.
Read from earningscalls-dev's own page on 2026-11-09

Attribution

Governing law

jurisdiction: British Columbia, Canada
These Terms are governed by and construed in accordance with the laws of CANADA, British Columbia, without regard to conflict of law principles.
Read from earningscalls-dev's own page on 2026-11-09

Liability cap

Our total aggregate liability for any claims arising from or related to the Service shall not exceed the amount paid by you to us in the twelve (12) months preceding the claim.
Read from earningscalls-dev's own page on 2026-11-09

Termination notice

We reserve the right to suspend or terminate access to the API, structured data, or documentation for any reason, including violation of these Terms.
Read from earningscalls-dev's own page on 2026-11-09

Change notice

Users will be notified of significant changes, and continued use of the Service constitutes acceptance of the updated Terms.
Read from earningscalls-dev's own page on 2026-11-09

Rate or usage limits referenced

The primary enforcement metric for each tier is the monthly API request quota and the per-minute rate limit.
Read from earningscalls-dev's own page on 2026-11-09

Document

Download YAML · schema: API Commons Terms of Service 0.1.0 · transcribed by claude-haiku-5-5, checked verbatim against the fetched page