Terms of Service

Updated August 11, 2026

1. Acceptance of Terms

By subscribing to and using the earnings call transcript API ("Service") provided by DREAVERR DIGITAL SOLUTIONS LLP - operating under the brand name earningsapi.io - you agree to be bound by these Terms of Service ("Terms"). If you do not agree to these Terms, please do not use the Service.

2. Service Description

The Service is a REST API platform that provides subscribers with:

The API is the primary interface for accessing and interacting with structured earnings call data. Documentation, the MCP server, and dashboard features serve as supplementary tools for managing access and exploring the dataset.

3. No Financial Advice

4. Rights and Usage

5. Risk Acknowledgment

6. Limitation of Liability

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. This cap applies however the claim arises, whether in contract, tort, negligence or otherwise, and applies in aggregate rather than per claim. We are not liable in any case for indirect or consequential loss, including lost profits, lost trading opportunities, lost or corrupted data, or the cost of obtaining replacement data.

Your relationship with your own users is yours. If you build a product, report or service on our data, your customers and end users are your counterparties, not ours. We have no contractual relationship with them and accept no liability toward them or toward you for anything arising out of that relationship. This includes claims about the accuracy or completeness of what you present to them, licensing or redistribution questions they raise, service interruptions they experience through your product, and any commitments you make to them that go beyond what these Terms grant you. You are responsible for making sure your own terms, disclosures and licences cover what you do with our data.

Indemnification. You agree to defend, indemnify and hold us harmless from any third-party claim, demand or proceeding, and from the resulting damages, liabilities and reasonable legal costs, that arises out of your use of the Service or your breach of these Terms. This covers in particular claims brought by your own customers or end users, claims that your use or onward presentation of the data infringed someone's rights, and claims arising from redistribution, resale or public exposure of the data beyond what section 8 permits. We will notify you of any such claim and may, at our discretion, take over its defence at your cost; doing so does not release you from this obligation.

7. Disclaimer of Warranties

The Service, including the API, structured data, documentation, and dashboard, is provided on an "as is" and "as available" basis without any warranties, express or implied.

Transcripts are a readable record, not a verbatim court transcript. Our transcripts aim to capture faithfully what was said and what it meant, but they are not a word-for-word reproduction of the audio, and differences from the spoken original are normal rather than exceptional. They arise for several reasons. Audio quality on earnings calls varies, and accents, poor phone lines, crosstalk and speakers talking over one another all affect what can be resolved. Passages that carry no informational content are condensed or omitted, including filler, false starts, repetitions, and procedural chatter. Sentence structure is tidied where speech does not translate cleanly to the page, so that a sentence reads the way it was meant rather than exactly as it stumbled out. Names of people, firms, products and technical terms are particularly prone to mistranscription. Beyond that, some passages, and occasionally a transcript as a whole, are closer to an account written up from notes or recollection than to a transcription of the audio. Where that is the case the text conveys the substance of what was said rather than the wording, and quotation marks around it should not be read as a claim of verbatim accuracy.

The practical consequence: treat a passage as a reliable account of what was said, not as forensic evidence of the exact words. If you quote from our transcripts to third parties, or your product does, and the precise wording matters, verify against the company's own recording or published transcript before relying on it. We do not warrant that any passage matches the audio word for word, we are under no obligation to correct a transcript, and we accept no liability arising from differences between a transcript and the underlying call.

8. Plan Quotas, Acceptable Use & Anti-Abuse

The primary enforcement metric for each tier is the monthly API request quota and the per-minute rate limit. Both are technically enforced by the Service. The additional rules in this section exist to protect against abuse and unauthorized resale of the data - they apply on top of, not instead of, the request quota.

8.1 Tier quotas (technically enforced)

All plans are billed quarterly - one payment covers three months of access.

Exceeding either limit returns an HTTP 429 Too Many Requests response and does not result in additional charges. If you need more headroom, upgrade to a higher tier.

8.2 Use scope (anti-abuse guidance, soft MAU bands)

Each tier carries a soft Monthly Active Users (MAU) band that we use as an anti-abuse signal, not as a technical limit. The MAU band describes the kind of workload the tier is priced for; we don't track MAU automatically. The hard limit is your request quota in 8.1.

If you expect to go beyond the band of your tier, talk to us and we will price it properly rather than leave you to guess. Beyond the Ultra band we agree a custom plan.

If your usage stays within the request quota of your current tier and you don't redistribute the data, the MAU bands are informational - they only become an enforcement matter when 8.3 (anti-abuse) or 8.5 (detection) is triggered.

8.3 Anti-abuse and anti-resale safeguards

Regardless of which tier Customer subscribes to, Customer may not:

8.4 Definitions

8.5 Detection & remediation

If we detect usage patterns indicating abuse of the request quota or unauthorized resale of the data - for example: a single Basic key serving thousands of distinct End Users; systematic redistribution or proxy-relay operation; or scraping disproportionate to normal application use - we reserve the right, in our sole reasonable judgment, to:

Customer attests to their use case at signup and at each billing renewal. We may request a brief written description of Customer's use case if reasonable evidence of misuse exists. Where the underlying issue is excess request volume only, a tier upgrade resolves it; where the issue is unauthorized redistribution, termination may apply.

8.6 Assisted bulk export (Pro and Ultra)

Your monthly request quota is there to be used, and for most historical backfills it is the right tool: paginate the archive with the cursor-based sync flow and the quota on Pro and Ultra covers a substantial universe without any special arrangement. That is the normal path, and we would rather you take it.

Occasionally a backfill does not fit sensibly into a monthly quota. In those individual cases we are glad to prepare the dataset for you as a service, at no extra charge, so a one-off historical load does not eat the quota you need for ongoing work. Tell us the companies you follow, the period you need and how deep you want it (call metadata, full transcript text, or speaker-tagged segments), and we assemble it and send a private download link. Typical turnaround is a few business days.

Where we do prepare an export, these are the bands we can deliver comfortably and repeatedly. They cover the realistic case, which is a research universe you actually follow. What the service is not designed for is a copy of the archive at index scale, for example every constituent of a major index or the corpus as a whole: at that point the export would replace the API rather than support it, which is neither what the plans are priced for nor what 8.3 permits. If your universe is genuinely larger than these bands, talk to us at support@earningsapi.io and we will find a sensible arrangement rather than leave you guessing.

Exported data is the same data the API returns and carries the same terms: you may build derived analyses and products on it as described in 8.3, and you may not redistribute it, resell it, or serve it to End Users as a transcript archive. Because the export is a convenience rather than a separate licence, it is available while your subscription is active and follows the same storage and deletion expectations as any other API response.

9. Payments & Subscriptions

All paid subscriptions are processed by Paddle.com as the authorized reseller and merchant of record.

See also our Refund Policy for additional details.

10. Service Availability

We strive to maintain high availability of the Service but do not offer a contractual uptime SLA at this time. We reserve the right to perform scheduled maintenance with reasonable advance notice.

Events outside our control. We are not liable for delay or non-performance caused by circumstances we cannot reasonably control. That includes outages at our hosting, database or payment providers, failures of upstream data sources, network or internet disruption, denial-of-service attacks, changes in law, and natural events or industrial action. Where such an event persists and materially prevents us from providing the Service, either of us may terminate the subscription, and you pay only for the period actually served.

11. Changes to the Service and Terms

12. Termination

We reserve the right to suspend or terminate access to the API, structured data, or documentation for any reason, including violation of these Terms.

Transfer of this agreement. You may not assign or transfer your rights or obligations under these Terms, including your subscription and API access, without our prior written consent. Consent is not unreasonably withheld: a change of control or an internal group reorganisation is normally fine, provided the use case stays the same and you tell us. We may assign these Terms in connection with a merger, acquisition or sale of the business.

13. Governing Law

These Terms are governed by and construed in accordance with the laws of CANADA, British Columbia, without regard to conflict of law principles.

14. Company Information

The Service is provided by DREAVERR DIGITAL SOLUTIONS LLP. earningsapi.io is a brand of DREAVERR DIGITAL SOLUTIONS LLP. Payments are processed by Paddle.com as the authorized merchant of record.

15. Contact Information

For questions or concerns regarding these Terms, please contact us:

DREAVERR Digital Solutions LLP
Email: support@earningsapi.io
Address: 1103 - 11871 Horseshoe Way, Richmond, British Columbia, Canada V7A 5H5

16. Third-Party Media, Fair Use & Takedown

This website may display short excerpts of publicly available video footage and imagery showing public figures - for example executives speaking at earnings presentations, shareholder meetings, and keynote events - in an editorial context that illustrates the public statements our Service indexes and makes searchable.

Acknowledgment

By using the API, structured data, documentation, and related services, you acknowledge that you have read, understood, and agree to be bound by these Terms of Service.

Terms of Service · Refund Policy · Privacy Notice