Legal

MCOMP API Terms of Use

Last updated: November 17, 2026

1. About these API Terms

1.1 These API Terms apply to the MCOMP public API, its API keys, its documentation (the "API documentation", currently at https://mcomp.app/developers) and the data it returns (together, the "API"). The API is part of the Service.

1.2 These API Terms supplement, and are incorporated into, the MCOMP Terms and Conditions (the "Terms"). The Privacy Policy also applies. Capitalized words not defined here have the meanings given in the Terms.

1.3 The Organization agrees to these API Terms. They are accepted on its behalf by an Organization owner or administrator when the Organization creates its first API key. That person confirms they have authority to bind the Organization. We record when, and by whom, each Organization accepted. In these API Terms, "You" means the Organization.

1.4 If these API Terms conflict with the Terms, these API Terms control for the API only. The Terms control for everything else.

2. Access and API keys

2.1 The API is available by invitation. The Company decides whether to enable it for an Organization, which scopes and which market data the Organization may access, and how many keys it may hold. The Company may change these settings.

2.2 Keys belong to the Organization, not to an individual. Organization owners and administrators create and revoke keys in the MCOMP desktop application or in Settings on mcomp.app. A key is displayed once when it is created. We do not store the key in readable form and cannot show it again.

2.3 You must keep keys secret. Use them only from servers You control and send them only in the request header described in the API documentation. Never put a key in a URL, in browser or mobile application code, in a public repository, or anywhere people outside Your Organization can read it.

2.4 You are responsible for all use of the API under Your keys, whether or not You authorized it, until the key is revoked.

2.5 If You believe a key has been lost, exposed or misused, revoke it at once and notify us at [email protected]. We may rotate or revoke any key to protect the Service. A key also stops working if the person who created it stops being an owner or administrator of, or leaves, the Organization. Create a replacement key before changing that person's role.

3. Permitted use

3.1 While Your Organization has an active paid Subscription and the API is enabled for it, You may use the API for Your Organization's own internal business purposes. You may not use the API during a Free Trial, even if a key works.

3.2 This includes building Your own internal tools, dashboards, alerts and integrations, and combining API data with Your own data for use inside Your Organization.

3.3 The API is read-only. It does not let You change anything in the Service.

4. Restrictions

4.1 The Acceptable Use section of the Terms applies to the API. In addition, You may not do any of the following.

4.2 No resale or redistribution. You may not resell, sublicense, publish, redistribute or otherwise make API data available to anyone outside Your Organization. This covers raw data, any substantial part of it, and anything derived from it, in any form, including as a dataset, feed, API, or a product or service that competes with the Service. The only exception is prior written permission from the Company.

4.3 No key sharing. You may not give keys to anyone outside Your Organization, except a contractor working for You, who may use them only for Your benefit and under these API Terms. You are responsible for their acts as if they were Yours. Your Affiliates are outside Your Organization.

4.4 No evasion of limits. You may not get around rate limits, budgets, scopes or access settings. This includes using several keys, Accounts or Organizations to obtain more access than was granted to You.

4.5 No scraping. You may not collect data from the Service by automated means other than the API.

4.6 Lawful use. You may not use the API or its data in a way that breaks the law or the terms of any Third-Party Service, including ticketing platforms and marketplaces.

4.7 No testing of our systems. You may not probe, scan, load-test or security-test the API without our prior written permission.

4.8 No model training. You may not use API data to train, fine-tune or improve machine-learning or artificial-intelligence models without our prior written permission.

5. Rate limits and usage

5.1 The API has limits, including a request rate, a per-minute data budget, a minimum interval between requests for the same event, and a polling limit on the change feed. Limits apply per Organization, across all of its keys. The current defaults are in the API documentation, and response headers show Your remaining allowance.

5.2 The Company may set different limits for an Organization and may change any limit at any time.

5.3 Requests over a limit are refused with a 429 response that says when to retry; other temporary errors may do the same. Your software must wait as instructed. Repeatedly ignoring limits, or trying to evade them, may lead to suspension.

5.4 We measure API usage per key and per Organization, by minute and by day. We use these records to operate and protect the API, to prevent abuse, to provide support and, where agreed with You, for billing. We may monitor API use to check compliance with these API Terms. Our usage records are the basis for any usage-based charge, unless clearly in error.

5.5 We do not guarantee any level of capacity or throughput.

5.6 Whether API access is included in Your Subscription or charged separately, and any limits, scopes or market data that come with it, are agreed directly with the Company, like the other commercial terms under the Terms.

6. Alpha status, changes and support

6.1 The API is an alpha release. No service-level, uptime, response-time or accuracy commitment applies to it.

6.2 We may add, change or remove endpoints, fields, limits, scopes and error codes, and may suspend or discontinue the API. The API documentation states the current version.

6.3 Where practicable, we will try to give at least 14 days' notice of a change that we expect to break existing integrations. We may act sooner, or without notice, for security, legal, abuse-prevention or other urgent reasons. Notice may be given by email, in the Service or in the API documentation.

6.4 Support for the API is by email to [email protected] on a best-effort basis.

6.5 Changing, suspending or discontinuing the API is not a termination of Your Subscription and gives no right to a refund, except for any separately charged, prepaid API fee covering the period after we discontinue the API without Your breach.

7. Data, ownership and attribution

7.1 Customer Data returned by the API, such as Your watchlists, filters and notes, remains Yours as described in the Terms.

7.2 All other API data, including market data and the Company's selection, arrangement and compilation of it, belongs to the Company, its licensors or the relevant third parties. So does the API itself.

7.3 While You have access, the Company grants You a limited, non-exclusive, non-transferable, revocable license to retrieve, store and use API data for the purposes permitted in section 3. No other rights are granted.

7.4 The Company is not sponsored by, endorsed by or affiliated with the ticketing platforms, marketplaces or venues that appear in API data. Their names and trademarks belong to their owners, and these API Terms give You no right to use them. You may not suggest that the Company or any such third party endorses Your products.

8. Suspension, revocation and termination

8.1 The Company may suspend or revoke keys, or disable the API for Your Organization, if You breach these API Terms or the Terms, if fees are overdue, or if we reasonably believe it is necessary to protect the Service, its users or a Third-Party Service.

8.2 We may suspend access immediately and without notice for a security risk or abuse. Where practicable, we will tell You why afterward.

8.3 Your keys stop working when Your Subscription ends, when Your Organization is paused or suspended, or when the API is disabled for You. You may stop using the API at any time by revoking Your keys.

8.4 Within 30 days after Your API access ends, You must delete the API data You have stored. You may keep Your own Customer Data, Your own internal analyses and reports that do not contain a substantial part of the raw API data, and any copies You are required by law to keep. Section 4 continues to apply to anything You keep.

8.5 Sections 1.4, 2.4, 4, 5.4, 7 (except the license in 7.3), 8.4, 8.5, 9 and 10, and any fees owed under 5.6, continue after access ends.

9. Disclaimers and liability

9.1 The API and its data are provided "AS IS" and "AS AVAILABLE" under the disclaimer in the Terms.

9.2 API data comes from Third-Party Services and public sources. It may be delayed, incomplete, unavailable or inaccurate, and it is not professional advice. You are responsible for checking it before acting on it and for the decisions You make with it. We do not promise that Your use of API data complies with the terms of any Third-Party Service. That is Your responsibility.

9.3 You will defend and indemnify the Company against third-party claims, and the resulting losses and reasonable costs, that arise from Your breach of sections 2, 3 or 4.

9.4 The Limitation of Liability section of the Terms applies to the API and to these API Terms. The governing law and dispute provisions of the Terms also apply.

10. Changes to these API Terms

10.1 The Company may change these API Terms. For a material change, we will make reasonable efforts to give at least 30 days' notice before it takes effect, unless a shorter period is needed to address law, security, fraud, abuse or an urgent change to the Service. Notice may be given as described in 6.3.

10.2 If You continue to use the API after a change takes effect, You accept the changed API Terms. If You do not agree, You must stop using the API and revoke Your keys.

11. Contact

Questions about these API Terms may be sent to [email protected].

MCOMP aggregates publicly available event and ticketing information for analytical and informational purposes. Data may include references to third-party ticketing platforms, marketplaces, and providers, including but not limited to Ticketmaster, SeatGeek, AXS, MLB, Paciolan, and VividSeats. MCOMP LLC is not affiliated with, sponsored by, or endorsed by any third party referenced. All trademarks are the property of their respective owners.