How MusiMap integrates
Where MusiMap fits in your existing platform and product integration models.
A music platform may already receive audio from upload or partner APIs, store it in its own infrastructure, enrich tracks during ingestion, and expose them to users for search, curation, playlists and dayparting. This page explains where MusiMap fits into that kind of workflow.
Adopting MusiMap does not require redesigning your ingestion, catalogue, playback, search, recommendation, curation or delivery platform. The integration model depends mainly on the MusiMap products you use, whether you have your own catalogue, whether MusiMap Atlas is also used, where audio and metadata live, whether processing is catalogue-based or on demand, and how results should be returned.
At a glance
| What you want to do | MusiMap catalogue | Processing required | Typical integration |
|---|---|---|---|
| MusiTag on demand | No | Tagging per request | Send audio and receive tags immediately |
| MusiTag across your catalogue | Your catalogue | Tagging during ingestion | Ingest music and receive or retrieve tagging results |
| MusiProfile | Your catalogue, MusiMap Atlas, or both | Pre-analysed catalogue | Request profiles through the API |
| MusiSearch | Your catalogue, MusiMap Atlas, or both | Pre-analysed catalogue | Search one or both catalogue sources |
| MusiTrace | Your catalogue | Fingerprinting during ingestion | Monitor configured streams and receive detections |
| Catalogue metadata and credits | Your catalogue and/or MusiMap Atlas | No audio processing required | Enrich or query catalogue information |
Your catalogue, MusiMap Atlas, or both
Integration is not a binary choice between your own catalogue and MusiMap Atlas. Three valid configurations exist:
- Your catalogue at MusiMap, representing the music your organisation manages.
- MusiMap Atlas, MusiMap's curated read-only intelligence layer.
- Both together, where discovery should cover your own music and the wider Atlas corpus.
A catalogue owner with a small private collection may still want search results that combine their own tracks with relevant Atlas content in the same experience. Where the product supports it, your catalogue and Atlas intelligence are complementary rather than mutually exclusive. See MusiMap Atlas and the Catalogue model.
Holding a catalogue representation at MusiMap does not necessarily make MusiMap your system of record. Your platform can remain authoritative for titles, availability, and user-facing catalogue management.
Product integration models
MusiTag
Catalogue ingestion and on-demand tagging are complementary modes. The same customer can tag catalogue content as part of normal ingestion, use the on-demand endpoint for individual tracks, or use both. For example, a time-sensitive new release may need analysis before it enters the normal catalogue delivery flow, while the rest of the catalogue continues through bulk ingestion.
On-demand MusiTag: no persistent customer catalogue is required. You send a track for analysis, MusiMap returns the tagging result, and you store it in your own platform.
Catalogue MusiTag: catalogue content is ingested, tagging runs as part of the processing workflow, and results are returned using the delivery models described in Getting results back.
MusiProfile
MusiProfile analyses a selection or collection of music using intelligence already available for those tracks. It does not send the audio through a new tagging analysis on every profile request.
For your own catalogue, the relevant tracks need to exist at MusiMap and have the required prior intelligence, including tagging. Profiles are then requested through the API. Where MusiMap Atlas is used, that preparation already exists for applicable content, so you can request profiles without first ingesting that music as your own catalogue. Own catalogue and Atlas can coexist in the same product experience.
MusiSearch
MusiSearch works over music that MusiMap has already prepared for discovery. Search can operate against your catalogue, MusiMap Atlas, or both where the use case requires it. For your own catalogue, the relevant tracks must have been ingested and prepared before search can run over them.
MusiTrace
For monitored repertoire in your own catalogue, the catalogue must exist at MusiMap, tracks must be fingerprinted, streams or sources are configured, and detections are delivered through the agreed integration path. MusiTrace onboarding includes contact with MusiMap because monitoring sources and delivery requirements are customer-specific. This is a guided integration tailored to your monitoring needs.
Metadata and credits without audio
Catalogue metadata such as identities, credits and identifiers can be supplied or queried without audio where audio-derived intelligence is not required. Audio is recommended where available because it enables additional MusiMap intelligence. MusiTag and other audio-derived capabilities naturally require audio when those capabilities are used.
Which integration fits me?
I already have a catalogue and audio in S3
Keep your existing storage. MusiMap can read the required audio and return intelligence to your platform.
I want to tag new tracks as they arrive
Use on-demand MusiTag in your ingestion flow, catalogue tagging for bulk delivery, or both.
I want search across my music and Atlas
Prepare your catalogue at MusiMap and combine it with MusiMap Atlas where your entitlement allows.
I want to monitor radio or streams
Use MusiTrace with MusiMap to configure the monitored source and detection delivery.
Continue reading
Getting data into MusiMap
Storage options, supported inputs, and ingestion timing patterns.
Getting results back
Immediate response, API retrieval, and push delivery to your environment.