Acceptable Use Policy

Use the API only if you are 21 or older, and only for or with people who are 21 or older.

Do not build, market or operate an Application aimed at, or likely to be used by, anyone under 21. Do not use the API for or on behalf of a minor.

Do not give Outputs to anyone in, or make them available from, a place where doing so is unlawful or that we have blocked (API Terms, section 3.4).

Do not connect the API or any Output to software that places, routes, sizes, times or recommends for automatic placement any wager, bet, trade or order, on a sportsbook, exchange, prediction market or elsewhere. A person must make every betting decision.

Do not use Outputs for price-gap trading between Operators, bonus abuse, account-limit evasion, or any plan to get around an Operator’s rules, age, location, identity or self-exclusion checks.

Sportsbooks, sports pools, exchanges, prediction-market venues, daily fantasy and pick’em operators, tout or tipster services, betting affiliates and lead generators, and anyone working for them, may not use the API or receive Outputs for trading, pricing, risk management, marketing, promotion or lead generation unless DeepChamp has signed a separate written agreement that allows it.

Do not use Outputs to promote a betting service, earn a referral fee, or send a person to place a bet.

Use Outputs only inside your own Application, for your own use and for End Users of that Application, in the form returned and with the Compliance Object attached.

Do not resell, sublicense, syndicate, publish, post in bulk, or repackage Outputs, or sell or share access to the API or a Key.

Do not build or run a feed, dataset, index, archive or API from Outputs, or anything that substitutes for a sports-data service. The limited evaluation and audit log that the API Terms allow (section 4.2) is the only record of Outputs you may keep beyond the display period.

Stay within the rate limits, quotas and spending caps in the API response headers and the documentation. Do not request more distinct games, teams or entities than your limits allow.

Do not use several Keys, accounts, addresses, wallets or services to get around a limit, or split one workload across them.

Do not scrape, crawl, mirror, or bulk-collect Outputs or documentation, or run automated collection outside the API’s own interface.

Do not share, sell, borrow or leak a Key. Do not put a Key in client-side code, a public repository, a prompt or a log that others can read.

Do not bypass authentication, payment challenges, quotas, safety filters, geographic controls or monitoring. Do not use stolen, shared or unauthorised payment credentials, and do not reverse a payment for a Paid Call that succeeded.

Do not probe the API for prompts, models, scoring rules or Third-Party Data, and do not reverse engineer it.

Do not train, fine-tune or distill models on Outputs, and do not use Outputs to build a competing product. Measuring the accuracy or calibration of DeepChamp for your own use, within the limits of the API Terms (section 4.2), is allowed.

Do not use Outputs, or anything about a person’s betting, to target, price to, push or encourage a person because they appear to be losing, chasing losses, betting more than they can afford, or showing signs of a gambling problem.

If an End User shows signs of distress about gambling, or asks for help, show the responsible-gambling notice (section 10) and do not use an Output to sell or encourage more betting.

Do not remove, hide or contradict the notice or the helpline in the Compliance Object.

Do not present an Output as a certain outcome, as risk-free, or as a recommendation to bet.

Do not describe an Output as proof of how DeepChamp, Jev or any Output has performed, and do not state any results, records or returns for DeepChamp or for Outputs. DeepChamp makes no such claim.

Do not suggest that DeepChamp, or any league, team, athlete, sportsbook, exchange or data provider, sponsors, endorses or is affiliated with you or your Application. Do not call an Output official league data.

Say that Outputs are AI-generated, and that the content is information, not betting advice.

Every response carries a compliance object with the fields age_gate, notice, helpline, helpline_url, ai_generated, terms_url and privacy_url. When you show an Output, or anything built from it, to an End User, show in readable text, not in a hidden field: the notice; the helpline and helpline_url; that it is AI-generated; and that it is for adults 21 and over.

Show these at the start of each session and with every response that shows a ranked signal, probability or edge score. Voice and other non-text interfaces must say the equivalent. The API Terms (section 6) set out the full duty.

Show any attribution or notice about third-party content exactly as given.

Update how you show these within 30 days after we change the Compliance Object and publish the change in the documentation.

If you or someone you know has a gambling problem, call, text or chat with 1-800-MY-RESET (National Problem Gambling Helpline; call, text or chat at https://www.1800myreset.org). Outside the United States, use your local responsible-gambling service. DeepChamp provides sports research and information only; it does not give betting advice and does not promise any result.

Follow all laws that apply to you and your End Users, including gambling, advertising, consumer protection, data protection, sanctions and export law.

Do not use the API for anything unlawful, fraudulent, harassing, or that infringes someone’s rights, or to use inside, confidential, hacked or non-public information about athletes, teams, leagues or markets.

Do not add league, team or athlete logos or photographs to Outputs in a way that suggests we supplied or licensed them.

Report suspected misuse, a leaked Key, a security problem or content that breaks this policy to vanessa@inovaplatforms.com, and put “DeepChamp for Agents abuse” in the subject. For anything else, use the same address.

A person who thinks an Output was shown to a minor or to someone in distress should say so; we treat it as urgent.

We may monitor use through logs and usage patterns, as the Privacy Policy describes, to find breaches and abuse.

If we think you broke this policy, we may, at our choice and without notice where the risk is high: slow or limit your Keys; refuse or end requests; suspend or revoke Keys; end your access; refuse refunds for calls tied to the breach; require you to remove or correct your Application’s presentation; and, where the law requires or a provider asks, report the matter to authorities, providers or platforms.

We may share information about a breach with the data and model providers whose terms it affects.

A breach of this policy is a breach of the API Terms. Our rights under those Terms, including suspension, termination and indemnity, apply.

We may change this policy. Material changes are announced on this page and by email at least 30 days before they apply, except where a law or a provider requires sooner.