Licensing
Licensing & attribution
What you can do with Krok Odds data, in plain English. This page is a summary — the binding terms are in the Terms of Service, and if the two ever read differently, the Terms win.
The short version
- Build products with it. Commercial use is allowed.
- Do not resell it as a raw feed, or serve it as your own API.
- Cache it, and keep what you have already pulled — including after you cancel.
- Credit us by default: “Data provided by Krok Odds” linked to krokodds.com.au.
- Need to run without the credit? Reach out to us for non-attribution terms.
Commercial use
You can build something you charge for. Entry-fee competitions, paid dashboards, a product of your own that uses our prices as an input — all fine. Nothing in our pricing changes because you charge your own customers.
The one thing we ask is that you tell us what you are building before you launch it. Public services that display our odds or our analytics, or that are offered to any person for a fee — a paid tipping channel included — are licensed individually under Section 8 of the Terms: a written confirmation from us, not a different price. Email [email protected] with a one-line description and we will confirm it in writing. It is a short email and it is cheaper than rebuilding later.
What is not allowed
- Reselling the data as a raw feed. You may not sell, sublicense or redistribute Krok Odds data as a standalone data product, dataset or feed.
- Serving it as your own API. Passing our responses through an endpoint of yours — or mirroring our data behind one — is redistribution, whatever you call it.
- Building a competing public product. Public or fee-charging odds comparison, arbitrage detection, expected-value detection or betting-market analytics need a commercial licence. Private, invite-only tools that are not charged for are permitted.
- Bulk-extracting to rebuild our dataset. Pull what your plan entitles you to and build on it; do not scrape around your plan limits to construct a substitute for the API.
Storing and caching
Store what you pull, cache it hard, and serve your users from your cache. That is the recommended pattern — it is faster for you, cheaper on credits, and the honest way to stay inside your plan. Every endpoint documents its cache floor; respect it and you will not need to think about rate limits.
You may keep the data you have already downloaded for as long as you like, including after your plan ends and after you cancel. Retention does not widen what you may do with it: the redistribution limits and the attribution requirement continue to apply to retained data for as long as you hold it, and a termination for breach ends the right to keep using it.
Attribution
Attribution is required by default. Wherever you display Krok Odds data, show “Data provided by Krok Odds” or “Powered by Krok Odds”, linked to krokodds.com.au.
It has to be visible on the same screen or view as the data, at the same time as the data — not only in a footer, an About page or a legal page, and not behind a menu. On a screen with many data points, one clear attribution for that screen is enough; you do not need one per row. Where the data leaves a screen — an export, an embed, a notification, a file you pass on — the credit goes with it, as a header or a trailing line.
Some endpoints carry a third-party credit of their own; where the endpoint documentation names one, it sits alongside ours. Attribution is a licence condition, not a courtesy — losing it is a breach of the Terms.
No attribution: reach out to us
If the credit does not suit your product, reach out to us for non-attribution terms. Removing the credit changes one thing only — the attribution line comes off. Every other term still applies: no resale, no pass-through API, no competing public product without a commercial licence.
Email [email protected] from the address on your account and we will work out the terms with you.
Anything else
Redistribution rights, white-label access, bulk feeds and unusual product shapes are licensed case by case on commercial terms — same address, [email protected]. If you are unsure which side of a line your product falls on, ask before you build.