DeepChamp for Agents
API Terms of Service
Version api-terms-2026-10-30.v1. Last updated: October 30, 2026.
These Terms cover DeepChamp for Agents, our sports-research intelligence API for AI agents. Read them with the Acceptable Use Policy, the documentation and the Privacy Policy.
1. Who we are and what these Terms are
- 1.1
These Terms are an agreement between Inova Platforms, Inc., a Delaware corporation, 8 The Green, Ste A, Dover, DE 19901 (“DeepChamp”, “we”, “us”), and the person or entity that gets an API key, connects to our MCP server, or pays for a call (“Developer”, “you”). If you accept for an entity, you confirm you have authority to bind it.
- 1.2
They cover the DeepChamp for Agents REST API, remote MCP server and any command-line tool or software development kit we publish for them (together the “API”), and the documentation.
- 1.3
You accept these Terms by requesting a key, by sending a request that carries a key, by making a Paid Call, or by signing an Order Form, whichever is first. If you do not agree, do not use the API.
- 1.4
The Acceptable Use Policy is part of these Terms.
2. Definitions
- 2.1
“Agent” means software, including an AI model, an agent framework or a script, that calls the API on your behalf or under your key.
- 2.2
“Application” means the product or service you operate that uses an Agent and the API.
- 2.3
“End User” means a person who uses your Application or to whom an Agent presents an Output.
- 2.4
“Output” means anything the API returns, including rankings, scores, orderings, written analysis, summaries, context fields, identifiers, metadata and the Compliance Object.
- 2.5
“Compliance Object” means the
complianceobject returned with every response, as set out in section 6. - 2.6
“Free Call” and “Paid Call” mean a request to an endpoint that is priced at zero, or priced above zero, in the price list. A Paid Call is a request that returns a success response (HTTP 2xx) and for which payment was settled or is invoiced.
- 2.7
“Key” means a credential we issue that identifies you to the API.
- 2.8
“Operator” means a sportsbook, bookmaker, casino, exchange, daily fantasy or pick’em operator, sports pool, prediction-market venue, betting affiliate or lead generator, tout or tipster service, or anyone acting for one.
- 2.9
“Order Form” means a written order or enterprise agreement signed by both parties.
- 2.10
“Third-Party Data” means data, content or marks that belong to or are licensed from someone other than us.
3. Eligibility and attestations
- 3.1
Age. The API is for adults. You attest that you, and every End User who sees an Output, are at least 21 years old. You will not give Outputs to anyone you know, or reasonably should know, is under 21, and you will not build an Application aimed at, or likely to be used by, people under 21.
- 3.2
Business use. The API is sold to developers and businesses. If you are an individual, you attest that you use it for your own work or project and not as a consumer.
- 3.3
Authority and law. You will use the API only as the law allows where you and your End Users are, and you are responsible for knowing those laws, including gambling, advertising, consumer protection, data protection, export and sanctions law.
- 3.4
Restricted jurisdictions. You will use the API only where information services of this kind are lawful. You will not provide the API or Outputs to anyone in, or make them available from, a place where doing so is unlawful. We may block any jurisdiction, in the API or by notice, at any time.
- 3.5
Sanctions and exports. You are not named on, or owned or controlled by anyone named on, a government sanctions list. You will not use the API or Outputs in a sanctioned place, and you will not export, re-export or make them available in breach of export or sanctions law.
4. The service and your licence
- 4.1
Grant. Subject to these Terms and payment, we grant you a limited, non-exclusive, revocable, non-transferable, non-sublicensable licence to (a) call the API through your Keys, and (b) use Outputs internally, and show or relay them to End Users inside your Application, in the form returned, with the Compliance Object and any attribution or notice in the Output kept attached and visible (section 6), for the End User’s own information.
- 4.2
Cache and retention. You may keep Outputs only as follows:
- (a)
For display: you may keep an Output for up to 24 hours after its
as_oftime, so you can show it in the same session or request chain, unless the Output says otherwise or an Order Form allows more. - (b)
For evaluation and audit: you may keep an internal log of Outputs you received, limited to the Output plus its
signal_id,content_hash,model_version,issued_atandas_of, to measure the service for your own purchasing and risk decisions. The log must not be shown to, shared with or sold to anyone else, and must not be used to train a model. - (c)
Nothing else: you may not build a database, archive, index or feed of Outputs for any other purpose.
- (a)
- 4.3
What stays ours. We own the API, the Outputs, our rankings, scores, models, prompts, written analysis and documentation, and our names and marks. You get no rights except those in 4.1. You may use our name only, in plain text, to say that your Application uses the API, and never in a way that suggests we or any league, team, athlete or data provider endorses you.
- 4.4
Your content. You keep your rights in what you send us. You give us the right to use request metadata to run, secure, bill and improve the API, as described in the Privacy Policy. Do not send personal data about End Users (see section 15).
- 4.5
Feedback. If you send us ideas about the API, we may use them without payment or credit.
5. What you may not do
- 5.1
You will not, and will not let anyone else:
- (a)
resell, rent, lease, sublicense, syndicate or republish Outputs or access to the API, or share, sell or lend a Key;
- (b)
scrape, crawl, harvest or bulk-collect Outputs, or use more than the limits in section 10, including by using many Keys, accounts or addresses to avoid a limit;
- (c)
train, fine-tune or distill any model on Outputs, or build a dataset, index, feed or API from Outputs that serves sports data or analysis to others, including anything that works as a substitute for a sports-data service. Measuring the accuracy or calibration of DeepChamp for your own use, as 4.2(b) allows, is not a breach of this paragraph;
- (d)
build a product or service that competes with DeepChamp using Outputs;
- (e)
reverse engineer, decompile or probe the API to extract prompts, models, weights, scoring rules or Third-Party Data;
- (f)
remove, alter, hide or contradict the Compliance Object or any notice in an Output;
- (g)
state or suggest that an Output is a certain outcome, a recommendation to bet, official league data, or endorsed by a league, team, athlete or data provider;
- (h)
bypass authentication, rate limits, quotas, payment, safety filters or geographic controls;
- (i)
use the API for anything unlawful, or in breach of the Acceptable Use Policy, which is part of these Terms.
- (a)
6. The Compliance Object: you must relay it
- 6.1
Every response carries a
complianceobject with these fields:- (a)
age_gate: the number 21, the minimum age for End Users. - (b)
notice: the text “Research and information, not betting advice. No outcomes are guaranteed. Adults 21+ only, where legal. AI-generated analysis can be wrong; use your own judgment.” - (c)
helpline: “1-800-MY-RESET”, andhelpline_url: “https://www.1800myreset.org”. - (d)
ai_generated: true. The content is AI-generated. - (e)
terms_urlandprivacy_url: links to these Terms and to the Privacy Policy.
- (a)
- 6.2
When an Agent or Application presents an Output, or anything built from an Output, to an End User, you must also present, in readable text and not in hidden fields, at the start of each session and with every response that shows a ranked signal, probability or edge score:
- (a)
the
notice; - (b)
the
helpline(1-800-MY-RESET) and thehelpline_url; - (c)
that the content is AI-generated; and
- (d)
that it is for adults 21 and over.
- (a)
- 6.3
Voice and other non-text interfaces must give the equivalent in spoken form.
- 6.4
If an Output carries an attribution or a notice about third-party content, you must show it exactly as given wherever you show the Output.
- 6.5
You will update how you present these items within 30 days after we change the text or fields of the Compliance Object and publish the change in the documentation, or sooner if a law or a provider requires it and we say so.
- 6.6
If an End User appears to be in distress about gambling, or asks for help, you will show the
noticeand thehelplineand will not use an Output to sell, upsell or encourage more betting. You will not use an Output to target, price to or encourage a person because they are losing or chasing losses.
7. Gambling restrictions
- 7.1
No automated wagering. You will not connect the API or any Output, directly or through an Agent or other software, to any system that places, routes, sizes, times or recommends for automatic placement any wager, bet, trade or order, including on a sportsbook, exchange or prediction market. A person must review the Output and make every betting decision. No Agent may place a wager, or be authorised to place one, without that person’s own decision on that wager.
- 7.2
No Operators without a separate agreement. You may not use the API, and may not give Outputs to, sportsbooks, sports pools, exchanges, prediction-market venues, daily fantasy or pick’em operators, affiliates, lead generators, other Operators or anyone acting for them, for trading, pricing, risk management, marketing, lead generation or promotion, unless we have signed a separate written agreement that says so. If you become, or work for, an Operator, tell us at once and stop using the API.
- 7.3
No affiliate use. You will not use Outputs to promote a sportsbook or any other betting service, to earn a referral fee, or to direct a person to place a bet.
- 7.4
Not a sportsbook. DeepChamp does not accept, place, hold, broker or settle wagers, does not hold anyone’s betting money, and does not offer betting credit. Nothing in the API changes that.
8. Information only: no advice, no guarantee, no reliance
- 8.1
Outputs are sports research and information. They are not betting, financial, legal, tax or investment advice, and not a recommendation, invitation or solicitation to place, avoid or change any wager.
- 8.2
Outputs are generated in part by artificial intelligence and software. They can be wrong, incomplete, delayed or out of date. Sports outcomes are uncertain. We do not promise any result, accuracy, return or outcome, and we make no statement about how any Output has performed or will perform. You will not make one on our behalf.
- 8.3
You, and not we, are responsible for how you and your End Users use Outputs, and for any decision made using them. Do not rely on an Output as the only basis for any financial or wagering decision, or for accepting, grading or settling a wager.
- 8.4
We may change, withhold or correct an Output at any time.
9. Payments
- 9.1
Price. Paid Calls cost what the price list says when the call is made. We may change prices for future calls on 30 days’ notice, or immediately for a new endpoint. There is no charge for Free Calls.
- 9.2
Machine payments. For Paid Calls without an Order Form, the API answers a request with an HTTP 402 payment challenge. Your Agent pays with a method we support, which at launch may include a card payment token or a stablecoin payment, and then repeats the request. We may change, add or remove supported methods, and a method may have a minimum amount. Stablecoin payments are available only where the processor and the law allow. By paying, you authorise the charge and confirm that you may use the payment credential.
- 9.3
Processor. Stripe, Inc. and its affiliates process payments. Their terms apply to the payment itself. We do not receive full card numbers or private keys. You are responsible for the security of any wallet, token or credential your Agent uses, and for setting spend limits on it.
- 9.4
Refunds. A payment is final once a Paid Call returns a success response. We refund a payment only for a call that failed or was flagged as not charged: an error response, a timeout on our side, or a response not delivered. We refund to the original payment method or, for a stablecoin payment, to the paying address in the same asset, less any network fees. We do not refund for an Output that was inaccurate, was not what you hoped for, or was not used, and we do not refund for calls made by anyone with your Key.
- 9.5
No chargebacks for delivered calls. You will not dispute or reverse a payment for a Paid Call that returned a success response. We may suspend you and withhold future access if you do.
- 9.6
Taxes. Prices exclude taxes. We add sales, use, digital or similar taxes where we are required to collect them. You will pay them, or give us a valid exemption certificate, and you bear any withholding.
- 9.7
Enterprise invoices. Under an Order Form we bill metered usage monthly in US dollars, in arrears, due 30 days from the invoice date. Our meter is the record of usage. Raise a billing dispute in writing within 30 days of the invoice; undisputed amounts stay due. Late amounts bear interest at 1 percent per month or the maximum the law allows, whichever is less. We may suspend the API after 10 days’ written notice of non-payment. Any minimum commitment is stated in the Order Form.
- 9.8
Prepaid balance. If you hold a prepaid balance, it is a prepayment for Paid Calls. It is not a deposit account, earns no interest, and is not transferable. If we end the API, we refund your unused balance, unless we ended your access under 12.1 because you breached these Terms.
10. Rate limits and fair use
- 10.1
We set rate limits, daily quotas and spending caps per Key, per account, per address and per endpoint, published in the documentation and returned in response headers. We may lower them to protect the service, our costs or our data sources. We may cap the number of distinct games, teams or entities you can request per day.
- 10.2
When you reach a limit you will get an error (for example HTTP 429) and a time to retry. Keep to it. Retrying faster, opening more Keys, rotating addresses or splitting traffic to avoid a limit is a breach of section 5.
- 10.3
We may refuse or end a request that looks like scraping, bulk collection, key sharing or abuse.
11. Keys and security
- 11.1
Keep Keys and payment credentials secret and out of client-side code, public repositories and prompts. You are responsible for everything done with them, including by Agents.
- 11.2
Tell us promptly at vanessa@inovaplatforms.com, with “DeepChamp for Agents abuse” in the subject, if you think a Key was exposed or misused. We may revoke Keys that appear exposed.
- 11.3
We may cap, rotate or expire Keys. Free Keys may expire after 90 days of no use.
12. Suspension and termination
- 12.1
We may suspend or end your access at once, with or without notice, if we believe you breached these Terms or the Acceptable Use Policy, if a payment fails or is reversed, if your use creates legal, security, regulatory or cost risk, if a data or model provider requires it, or if we stop offering the API. We will try to tell you when we can.
- 12.2
You may stop using the API at any time. Under an Order Form, termination follows the Order Form. We may end these Terms for convenience on 30 days’ notice.
- 12.3
On ending, your Keys stop working, your licence ends, and you must delete Outputs you kept for display. You may keep an evaluation and audit log under 4.2(b), and its conditions continue to apply. Amounts owed stay owed. Sections 4.3, 5, 7, 8, 9 (for amounts owed) and 14 to 25 survive.
13. Availability and changes to the API
- 13.1
There is no service level. The API is provided as available, may be delayed, limited, changed, paused or withdrawn, and is not built for uses where a failure could cause harm. A service level applies only if an Order Form states one.
- 13.2
We may add, change or remove endpoints and fields. Where we reasonably can, we give 30 days’ notice of a breaking change to a paid endpoint, except where a law, a provider or security requires faster action.
- 13.3
Outputs depend on third-party data and models. We may remove or change content if a provider changes its terms, ends supply or asks us to.
14. Third-party data and models: flow-down
- 14.1
Outputs are built in part with Third-Party Data and with models run by other companies, used under their terms. You will follow the restrictions in Schedule A and in any notice in an Output or in the documentation, as updated.
- 14.2
Third-Party Data remains the property of its owners. No league, team, athlete, sportsbook, exchange, data provider or model provider sponsors, endorses or is affiliated with the API unless we say so in writing. You will not use their names or marks except as an Output shows them or as the law allows.
- 14.3
Outputs contain no team, league or athlete logos or photographs. You will not add them in a way that suggests they came from us.
15. Privacy
- 15.1
Our Privacy Policy describes the data we handle. For the API, that is request metadata used to run, secure, bill and improve the API, as described in the Privacy Policy.
- 15.2
Do not send us personal data about your End Users in a request. If you do, you confirm you may, and we may delete it.
- 15.3
You are responsible for your own notices, consents and lawful basis for what your Application does with End Users’ data.
16. Confidentiality
- 16.1
Keep non-public pricing, Order Form terms, security details and unreleased API features confidential, except where the law requires disclosure.
17. Disclaimers
- 17.1
THE API AND OUTPUTS ARE PROVIDED “AS IS” AND “AS AVAILABLE”. TO THE MOST THE LAW ALLOWS, WE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE, NON-INFRINGEMENT, ACCURACY, COMPLETENESS, TIMELINESS, AVAILABILITY AND UNINTERRUPTED OR ERROR-FREE OPERATION. WE DO NOT WARRANT THAT ANY OUTPUT IS CORRECT, THAT IT WILL HELP ANYONE MAKE OR AVOID A LOSS, OR THAT IT IS LAWFUL FOR YOUR OR YOUR END USERS’ USE.
18. Indemnity
- 18.1
You will defend, indemnify and hold harmless DeepChamp, its affiliates, officers, employees and agents, and its data and model providers where our agreements with them require it, from claims, losses, liabilities, fines and costs (including reasonable legal fees) arising out of or related to: (a) your Application and its End Users; (b) your or your End Users’ use of Outputs, including any wager, trade or marketing decision made using them; (c) your breach of these Terms or the Acceptable Use Policy; (d) your violation of law, including gambling, advertising, age, consumer protection or data protection law; (e) your violation of anyone’s rights; and (f) any claim by your customers, End Users or regulators about your Application.
- 18.2
DeepChamp gives you no indemnity under these Terms.
19. Compliance with our providers
- 19.1
Where a provider’s terms require us to pass a duty to you, the duty in Schedule A binds you directly. If a provider tells us a use of Outputs breaches its terms, we may require you to stop that use at once.
20. Limitation of liability
- 20.1
TO THE MOST THE LAW ALLOWS, DEEPCHAMP IS NOT LIABLE FOR INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL, EXEMPLARY OR PUNITIVE DAMAGES, LOST REVENUE, LOST INCOME, LOST BUSINESS, LOSS OF DATA OR GOODWILL, BETTING OR GAMBLING LOSSES, WAGERS PLACED OR NOT PLACED, STALE OR INCORRECT OUTPUTS, SERVICE INTERRUPTION, OR THIRD-PARTY DECISIONS, EVEN IF TOLD THEY MIGHT OCCUR.
- 20.2
TO THE MOST THE LAW ALLOWS, OUR TOTAL LIABILITY FOR ALL CLAIMS RELATING TO THE API IS NOT MORE THAN THE GREATER OF (a) THE FEES YOU PAID US FOR THE API IN THE 12 MONTHS BEFORE THE EVENT AND (b) USD 100. FOR USE OF FREE CALLS ONLY, THE LIMIT IS USD 100.
- 20.3
In plain words: the most we can owe you for all claims is the greater of what you paid us for the API in the 12 months before the event and USD 100. If you used only Free Calls, the most is USD 100.
- 20.4
Nothing limits liability that the law does not allow us to limit.
21. Governing law and venue
- 21.1
Delaware law governs these Terms, without regard to conflict-of-law rules.
- 21.2
The state and federal courts located in Delaware have exclusive jurisdiction over any dispute about these Terms or the API, and each side consents to that jurisdiction and venue.
22. Relationship to other terms
- 22.1
For use of the API and MCP server, these Terms control over DeepChamp’s consumer Terms of Service. Those consumer Terms continue to govern the DeepChamp app and website and do not give you a licence to automate access to them. The licence in 4.1 does not extend to the app, the website or anything else.
- 22.2
Order of precedence: an Order Form, then these Terms, then the Acceptable Use Policy, then the documentation.
23. Changes to these Terms
- 23.1
We may change these Terms. For a material change we will post the new version and email the address on your account at least 30 days before it applies. Using the API after that date means you accept it. If you do not accept, stop using the API. Other changes apply when posted.
24. General
- 24.1
Entire agreement. These Terms, the Acceptable Use Policy and any Order Form are the whole agreement between us about the API and replace earlier statements about it.
- 24.2
Assignment. We may assign these Terms. You may not assign them without our written consent.
- 24.3
No third-party beneficiaries. Nobody other than you and us has rights under these Terms, except that the providers of the third-party data and models described in Schedule A may enforce sections 5, 14 and 19 and Schedule A.
- 24.4
Severability and waiver. If a part of these Terms is unenforceable, the rest stays in force. A right is waived only in writing, and not using a right is not a waiver of it.
- 24.5
Force majeure. Neither side is liable for a delay or failure caused by events beyond its reasonable control, other than a duty to pay.
- 24.6
Notices. We may give notice to the email address on your account. You may give notice to us at the email address in section 25. A notice by email takes effect when sent.
- 24.7
Relationship. We and you are independent contractors. Nothing here makes either side an agent, partner or employee of the other, and nothing here gives you exclusivity.
- 24.8
Electronic acceptance. Your acceptance online, by Key request or by use of the API is a binding electronic signature, and our electronic records of it are evidence.
25. Contact
- 25.1
Inova Platforms, Inc., 8 The Green, Ste A, Dover, DE 19901.
- 25.2
Email vanessa@inovaplatforms.com for legal notices, security reports and abuse reports. Security and abuse reports: put “DeepChamp for Agents abuse” in the subject.
Schedule A. Flow-down terms for third-party data and models
You agree to each of these terms, which come from the providers whose data and models we use:
- (a)
Do not use Outputs to build or run a sports-data API, feed or equivalent data service for third parties.
- (b)
Do not share, sell, lend or resell Keys or access to the API.
- (c)
Do not state or suggest that anything is official league data, or that it is endorsed by, sponsored by or affiliated with a league, team, athlete or data provider.
- (d)
You are responsible for age, location, responsible-gambling and consumer-protection duties for your Application.
- (e)
Do not use Outputs to develop models that compete with the providers of the models we use.
- (f)
Outputs contain no team, league or athlete logos or photographs. Do not add any in a way that suggests we supplied or licensed them.
- (g)
A provider may require us to remove or change content. We may do so at any time, and we may require you to stop a use at once (section 19).
- (a)