Acceptable Use Policy

This AUP sets out what you can and cannot do with the Stadar API. It is incorporated into the Terms of Service by reference. Violations may result in immediate suspension or termination.

1. Permitted uses

Stadar is built to be used. On every paid tier you may, without separate permission:

power sportsbooks, odds-feed services, and betting-adjacent products that consume esports data;
build media sites, content platforms, prediction tools, fantasy products, and analytics dashboards;
run internal models, research, and trading workloads against the API;
cache API responses on your own infrastructure for as long as your product needs them, in line with the licence in clause 4 of the Terms;
use the data commercially, including monetising the products you build with it.

This is deliberate. Stadar is the only self-serve flat-tier esports data API that permits betting workloads — we don't want you wondering whether your use case is OK. If it's listed above, it is.

2. Downstream gambling — your product, your responsibility

Stadar provides data. We are not a sportsbook, a tote, an exchange, or any other kind of gambling operator. If you build a product that takes bets, displays odds, or facilitates wagering of any kind, you are the operator. That means you, not Stadar, are responsible for:

holding any gambling licence required in the jurisdictions you serve;
age and identity verification of your end users;
responsible-gambling tooling, self-exclusion, and player-protection measures required by your regulator;
geo-blocking jurisdictions where your product may not lawfully operate;
marketing standards, advertising rules, and bonus-and-promotion compliance;
anti-money-laundering and counter-terrorist-financing controls.

You must not represent or imply, in your product's UI, marketing, or terms, that Stadar is the gambling operator, runs the book, sets the lines, or is otherwise responsible for the outcome of bets. Stadar's name and marks may not be used in a way that suggests endorsement of any specific wager, market, or operator.

3. Sanctions and restricted regions

You may not access or use the Service from, or provide it to end users in, jurisdictions subject to comprehensive sanctions administered by the UK, the EU, the United Nations, or the United States (currently including Cuba, Iran, North Korea, Syria, and the Russian-occupied regions of Crimea, Donetsk, Luhansk, Zaporizhzhia, and Kherson). You also may not use the Service if you are on a UK, EU, UN, or US sanctions list. Stadar may block requests from networks associated with these jurisdictions without notice.

4. Rate limits and quotas

Each tier has a daily quota and a per-second rate limit, published at /pricing. You must not:

register multiple accounts to stack free quotas, evade limits, or fragment a single workload;
share API keys outside your organisation or resell access to your key;
use the API as a continuous bulk-mirror of our database when an export endpoint exists for the same data on your tier;
attempt to circumvent rate-limit headers, retry-after instructions, or quota-exhaustion responses by means other than waiting or upgrading.

If your workload has spiky or unusual shape, email [email protected] before launching — it's almost always cheaper to talk to us than to be throttled.

5. Attribution and share-alike

A material portion of Stadar's data is derived from Liquipedia and licensed under CC-BY-SA 3.0. The full Attribution Policy explains where attribution appears in each response and what you must do downstream. In short: where you re-display or redistribute Liquipedia-derived content, you must credit Liquipedia and, for substantial reuse, carry the CC-BY-SA 3.0 share-alike obligation forward in your published work. Stripping the _sources block from your cached copies is a breach of this AUP.

6. Prohibited uses

You may not use the Service to:

break the law in any jurisdiction relevant to you or to your end users;
build a product whose primary value is reselling raw Stadar data dumps as a competing API, feed, or database;
scrape Stadar at a rate or pattern intended to exhaust our capacity or harm other customers;
probe, scan, or attempt to penetrate the Service except under an authorised security-research arrangement;
use the Service for safety-critical or life-critical decision-making, medical advice, immigration decisions, credit decisions, or any context that requires regulated data quality;
misrepresent the source, recency, or licence of data obtained from the Service;
harass, defame, or invade the privacy of esports players or staff (the API does not return private data, but normalised public profiles can still be misused — don't);
train a model intended primarily to replicate the Service's normalisation, identifier mappings, or schema and offer that model as a competing API.

7. Security expectations

Keep your API keys out of client-side code, public repositories, and shared logs. Rotate immediately if a key leaks. Don't expose Stadar endpoints directly to untrusted clients in a way that would let them issue arbitrary requests under your key — proxy through your own backend. If you discover a security issue in Stadar itself, please email [email protected] with "Security" in the subject line; we'll respond within two business days and won't pursue good-faith researchers who follow coordinated disclosure.

8. Enforcement

For clear or serious breaches — circumventing rate limits, building a competing data feed from raw exports, ignoring sanctions, stripping attribution — we may suspend or terminate access immediately and without refund. For ambiguous cases we'll usually email you first and give you a chance to fix the issue before any action. Repeated violations after warning will lead to termination.

9. Reporting abuse

If you believe another Stadar customer is violating this AUP — for example by redistributing raw data dumps — email [email protected] with "AUP report" in the subject line. We treat reports confidentially and act on the ones with evidence.

Acceptable Use Policy.