Terms of Service
These terms govern access to the OpenCricketAPI website, API, MCP server, dashboard, documentation and paid plans.
Effective and last updated: 6 October 2026
1. Agreement and eligibility
By creating an account, getting an API key, buying a plan or using the service, you agree to these terms and the policies linked from them. You must be at least 18 years old and legally able to enter this agreement. If you act for an organisation, you confirm that you may bind it.
2. The service
OpenCricketAPI provides cricket data through REST endpoints, an MCP server, documentation and a dashboard. Historical data comes mostly from Cricsheet, and some domestic and youth competitions, live scores and fixtures come from ESPN. Coverage, freshness and individual fields vary by competition and source. Missing facts are returned as missing; we never estimate or invent them. We may add, change, suspend or remove features as sources and the product change.
Unless a separate written agreement says otherwise, there is no guaranteed service level, no guarantee of uninterrupted availability, and no guarantee that a particular match, competition, statistic or live score is available.
3. Accounts and API keys
You are responsible for accurate account information, for activity under your account, and for keeping your API keys private. Do not publish, resell, transfer or share a key outside your team or application. Tell us at once if you think a key was exposed. We may rotate, suspend or revoke a key to protect the service.
4. Plans, quotas and payments
Prices, quotas and rate limits are shown on the pricing page. Our systems measure usage. Requests above your monthly quota or per-minute limit are refused with an error; we never charge for overage. Unused quota does not carry over to the next month.
Dodo Payments is the Merchant of Record for paid plans. Dodo handles payment processing, invoices, sales taxes, refunds and chargebacks under its own buyer terms and privacy policy. Paid plans renew every month until you cancel. You can cancel your plan on your dashboard, or change it with Manage billing.
Cancellation and refunds are covered by our Refund and Cancellation Policy. Your mandatory consumer rights are not affected.
5. Acceptable use
You may not use the service to:
- break the law, infringe rights, or misrepresent the source or accuracy of data;
- probe, bypass, disable or interfere with authentication, quotas, security controls or our infrastructure;
- introduce malware, send abusive automated traffic, overload the service, or use another person's account or key;
- resell access or API keys, or present the service itself as your own, without our written permission;
- treat outputs as guaranteed facts where safety, financial loss or regulated decisions depend on them.
Cricket data can be delayed, incomplete, corrected or unavailable, and live scores can lag the match. Nothing in the service is betting, financial, legal or other professional advice.
6. Your applications and content
You are responsible for your integration, the notices you give your own users, your security, your legal compliance and the decisions you make from the data. Information you send us through support or forms stays yours, but you allow us to use it to answer your request and run the service.
7. Data you receive: caching, retention and attribution
We set no maximum retention period on responses you receive. You may cache them, store their fields, keep exact responses for testing, and keep derived figures for as long as you need. When your access ends, you do not have to delete data you received while it was valid. Our own retention of your account, usage and billing records is covered by the Privacy Policy.
Internal use of data you keep, such as research, statistics, model training and evaluation, is allowed. Section 5 bars reselling access and presenting the service as your own; it does not restrict internal work on data you lawfully received.
Access through the service is not a licence to redistribute a source's data. Every response names its source in meta.source and its licence in meta.licence. Cricsheet data is licensed under the Open Data Commons Attribution License (ODC-By 1.0), so credit Cricsheet in anything you publish from it. Data with meta.source ESPN carries no open licence, and we cannot grant you rights to redistribute it. Where a source licence sets obligations of its own, those apply to your use directly, and we cannot waive them for the source.
8. Intellectual property
We keep our rights in the OpenCricketAPI software, website, branding, documentation and original materials. Third-party data, names and marks stay subject to their owners' rights. Open-source components are covered by their own licences.
9. Suspension and termination
You may stop using the service at any time. We may limit, suspend or end access for non-payment, abuse, security risk, legal requirements or a serious breach of these terms. Where reasonably possible, we will tell you first and give you a chance to fix the problem. Sections that by their nature should survive termination stay in effect.
10. Disclaimers and liability
To the extent the law allows, the service is provided “as is” and “as available”. We disclaim implied warranties of merchantability, fitness for a particular purpose and non-infringement. We are not responsible for source outages, third-party services, or decisions made from cricket data.
To the extent the law allows, we are not liable for indirect, incidental, special, consequential or lost-profit damages. Nothing in these terms excludes liability that the law does not allow us to exclude, or limits your mandatory consumer rights.
11. Changes, disputes and contact
We may update these terms. A changed version shows a new date at the top, and we give extra notice of important changes. If you keep using the service after a change takes effect, you accept the updated terms.
These terms are governed by the law that applies to the service operator, subject to any mandatory protections in your country. Before starting a formal dispute, please email opencricket@proton.me so we can try to resolve it.