API Terms of Service

Audio submitted through the API is processed entirely in memory and is never persisted: we do not write your audio to disk, object storage, a message queue, or any backup. Raw bytes are received, analyzed, and discarded when the analysis finishes. Only the resulting JSON (scores, measurements, and the written diagnosis) and the metadata you submit (such as the file name) are stored.

We do not use your audio to train machine-learning models, and the service does not generate, master, remix, or modify audio. This section is a binding commitment of these API Terms, not a courtesy: if we ever intended to change it, the change would apply only to requests made after notice to you, never retroactively to audio already processed.

Test-mode requests (keys prefixed ts_test_) never reach the analysis engine; any bytes sent to the sandbox upload endpoint are discarded without being read.

You agree that you will:

• only submit audio you have the legal right to submit, and no content that is unlawful or infringes someone else's rights;
• not attempt to defeat, probe, or circumvent rate limits, quotas, concurrency caps, eligibility checks, or the service availability controls described in section 7, including by rotating API keys or accounts;
• not submit files deliberately crafted to disrupt, crash, or degrade the analysis service or to exhaust its resources;
• not resell, sublicense, or expose the raw API endpoints as a competing standalone music-analysis API without a written partner agreement with us (building products and services on top of the API is welcome and encouraged);
• not use the API to attempt to access analyses, keys, or data belonging to another account.

If you are interested in a partner or platform integration, contact us at hello@trackscore.ai.

Every API key is subject to rate limits, daily quotas, and concurrency caps. Current limits are documented in the API reference and returned on API responses via rate-limit headers; they may vary by key and plan.

The analysis engine is a shared resource. We may throttle, queue, or reject requests, adjust a key's limits, or suspend a key or account, where we reasonably believe usage degrades the service for others, indicates abuse, or breaches section 2. Where practical we will contact you before or promptly after taking action. If you expect sustained high volume, contact us about partner pricing rather than working around the limits.

API keys are bearer credentials: anyone holding a key can spend your credits and read your analyses. Keys are shown once at creation and stored by us only as one-way hashes; we cannot recover a lost key, only issue a new one.

You are responsible for keeping keys secret and for all requests made with your keys, whether or not you authorized them. Do not embed live keys in client-side code, public repositories, or distributed applications. If you believe a key has been exposed, revoke it immediately in the Developer console and notify us. We may revoke keys that we reasonably believe are compromised, leaked, or being used in breach of these API Terms.

API access is included with Pro and Studio subscriptions and uses the monthly credits of the account that owns the key: one successful analysis consumes one credit, the same as the web app. If an analysis fails on our side, the credit is restored automatically. Test mode is free and does not consume credits.

Credits consumed by completed analyses are not refundable. Credit purchases, subscription billing, renewals, and cancellation are governed by the TrackScore Terms of Service and the pricing shown at purchase. Complimentary, metered, or partner keys are provisioned by us and governed by the written agreement under which they were issued; where no separate agreement exists, these API Terms apply.

The API is versioned in the URL path; the current version is /api/v1. Within a version we make only additive changes, and clients must ignore unknown JSON fields. A breaking change ships as a new path version; from the day a successor is announced, the deprecated version emits Deprecation and Sunset headers (RFC 8594) and keeps serving unchanged for at least 12 months before retirement.

The versioning and deprecation policy is the source of truth for this commitment and is incorporated into these API Terms.

The API is offered without an uptime service-level agreement in v1. We operate the API behind service availability controls, including a service-wide kill switch, and may suspend, throttle, or disable the API in whole, per feature, or per key: for maintenance, to protect the analysis engine or other customers, to investigate suspected abuse, or where required by law. We use reasonable efforts to keep disruption short and, for planned changes, to communicate in advance.

Features described as early access, beta, or preview may change or be withdrawn without the section 6 notice period. Retirement of a whole API version always follows the section 6 deprecation policy. If we suspend your key for a suspected breach of these API Terms, we will tell you why on request, and restore access if the concern is resolved.

The API returns automated, advisory analysis. Scores, grades, and the written diagnosis are opinions produced by software about measurable characteristics of audio. They are not a guarantee of commercial performance, playlist placement, label interest, audience response, or fitness for any purpose, and they are not professional mastering, legal, or business advice.

The API is provided "as is" and "as available", without warranties of any kind, express or implied, including merchantability, fitness for a particular purpose, and non-infringement. To the maximum extent permitted by law, TrackScore Holdings, LLC is not liable for indirect, incidental, special, consequential, or punitive damages, or for lost profits, revenue, or data, arising from the API; and our total aggregate liability arising out of or relating to the API is limited to the greater of (a) the amounts you paid us for the service in the 12 months before the event giving rise to the claim, or (b) fifty United States dollars ($50.00 USD). Nothing in these API Terms excludes liability that cannot be excluded under applicable law.

Our Privacy Policy explains how we handle personal data across TrackScore, including account data for API users. In addition, for the API specifically: we retain analysis results (the JSON described in section 1) and API usage records (request identifiers, timestamps, endpoint, status, and latency) to operate, secure, and bill the service. Audio itself is never retained, as set out in section 1.

We may update these API Terms as the API evolves. For material changes we will give notice through the Developer console or by email to the account owner before the change takes effect; continued use of the API after the effective date constitutes acceptance. The "Last updated" date below always reflects the current version.

These API Terms are governed by the laws of the State of Florida, USA, without regard to conflict-of-law rules. If any provision is found unenforceable, the remainder stays in effect. Questions about these API Terms: hello@trackscore.ai.