> The Resomix API is a music similarity and audio analysis API with search, similarity by track or upload, and versioned track analysis of your own catalogue. Developers // Live · Partner-scoped REST API · Powered by PYXIS-1 # Put similarity and track intelligence inside your product. The Resomix API is a music similarity and audio analysis API for partners, powered by Resomix's PYXIS-1 engine. Search your own catalogue by sound and rank it by how the music actually sounds, through a partner-scoped REST API. Structured Track Intelligence analysis (tempo, key, loudness, structure, mood and genre signals) is enabled on request, against your own catalogue. Partner-scoped · Versioned JSON · Private catalogue index - Search + similarity · **LIVE** - Track analysis · **ON DEMAND** - Partner-catalogue only - Batch ingestion · **LIVE** - Guided pilot · **AVAILABLE** 01 // Capabilities ## Three capabilities. One partner-scoped API. "Find the partner-catalogue track ID for this title or artist." **in:** title / artist / auto query **out:** matching partner tracks + IDs GET /api/v1/search_tracks/ "Which tracks in our catalogue sound most like this one?" **in:** catalogue track ID · or uploaded reference (≤100 MB) **out:** ranked matches · scores · metadata · playlist info POST /api/v1/similarity/search POST /api/v1/similarity/upload "What does this track contain and how does it behave?"track analysis api **in:** uploaded audio **out:** versioned structured JSON (async) POST /api/v1/analysis/upload GET /api/v1/analysis/{id}/status GET /api/v1/analysis/{id}/result result depths: 10 · 20 · 50 · 100. Full parameters and schemas live at api-docs.resomix.com Search and similarity are enabled on every partner key. Track analysis is provisioned on request and runs against your own catalogue, so talk to us before building on it. Returned fields are versioned and may be partial or optional. 02 // The search space ## Your key searches your catalogue. Nothing else. **No shared catalogue. No cross-partner results.** Every partner runs against its own sealed index: its own catalogue, credentials and results. A key can never query another partner's catalogue or Resomix's consumer product, and an uploaded reference is only ever a query against your own index. **No shared public pool.** Each partner has its own catalogue, credentials, index and results. **No cross-partner retrieval.** A key can never query another partner's catalogue, or Resomix's consumer product. **Uploads stay queries.** An uploaded reference is analysed as the query; its matches still come only from your own indexed catalogue. 03 // Workflows ## See the request. Read the response. Five supported workflows: real endpoints, real envelope, fictional data. Search is metadata-based: it finds the partner track ID, which similarity then uses. Two calls, one workflow. compare rank order within a response; raw score bands are not universal quality measures across unrelated queries · examples are generic http, not official sdks 04 // Onboarding ## Deliver the catalogue once. Query it through the API. The API searches a private index built from your catalogue. Managed batch ingestion is the live onboarding route today. audio + csv manifest → .done marker last → webhook when ready 1. Deliver audio + CSV manifest 2. Add **.done** last 3. Resomix validates and processes 4. Private index ready, webhook notifies you a partial upload never starts processing · .done is sent last · one active batch per partner · validation is all-or-nothing, so a rejected batch is corrected and re-sent with a new .done · new batches top up the catalogue and rebuild the private index 05 // Analysis data ## Turn audio into versioned product data. **Read results defensively.** Fields may be optional: a partial result returns the fields that completed successfully, with the job status alongside. 06 // Integration ## Use the live path today. Plan the next layer later. Similarity and search inside your existing backend or application, using your interface and your customer journey. Requires an indexed partner catalogue. Track analysis can be added on request. Managed SFTP onboarding that builds and grows the private index. **Required before partner-catalogue similarity** Evaluate on a representative sample of your own catalogue with a scoped key; this is the current evaluation route. A self-serve trial catalogue is planned. It is not available today. A ready-made "find similar" interface for minimal front-end work. Planned. The experience under your own brand, on enterprise terms. Planned. versioned /api/v1 routes · scoped keys, e.g. search:read · keys begin rmx_ IDs, scores and metadata. No audio access. Adds short-lived playback tokens for authorised media requests. Available only to provisioned partners with the required service mode and rights. Per-second limits and monthly quotas apply. On HTTP 429, respect Retry-After and use exponential backoff. 07 // Questions ## Questions developers ask about the Resomix API **Is there an API for music similarity search?** Yes. The Resomix API returns ranked similar tracks from your own indexed catalogue, from a catalogue track ID or an uploaded reference of up to 100 MB, with scores and metadata in a versioned JSON envelope. **Can I try the API without a partner agreement?** Not today. Resomix does not run a public sandbox, because similarity is only meaningful inside a real catalogue. The evaluation path is a guided pilot with a scoped key against a sample of your own repertoire. A self-serve trial is planned. **What does the track analysis endpoint return?** Versioned structured JSON covering rhythm (BPM, beats, downbeats and phrases), tonality (key, scale, Camelot code, tuning and chromagram), loudness and dynamics, mood and genre signals with scores, structure with millisecond ranges, and provenance. Analysis is enabled per partner on request. **Does the API search a shared catalogue?** No. Every key searches only that partner's private index. A key can never query another partner's catalogue or the Resomix consumer product. **What are the rate limits?** Per-second limits and monthly quotas are provisioned per partner agreement. On HTTP 429, respect Retry-After and back off exponentially. 08 // Evaluate ## Test the API on your own catalogue. There is no public sandbox today. The current evaluation path is a guided pilot using a representative sample of your own catalogue. **Similarity is only meaningful inside a real catalogue.** A shared demo pool would misrepresent both the isolation model and the results you would see in production. The guided pilot puts a scoped key against your own repertoire instead: the same API, honest results. A self-serve trial catalogue is planned. Goals and success criteria, set together. A representative catalogue slice via managed SFTP. Resomix validates, processes and indexes it privately. Partner-scoped credentials for your sample. Search and Similarity against your own data, plus Analysis if you asked for it. For engineering & product teams ## Request a guided API pilot. For implementation detail ## The full reference lives in the docs. --- Source: https://resomix.com/developers Site guide for AI systems: https://resomix.com/llms.txt