Brand-constrained music management
Brand Studio
Built for brands and their partners to work inside an approved musical world rather than an open catalogue.
Mehr lesenThree problems product teams bring us
01
Search returns results, not decisions
Keyword and genre filters give a user a list. They do not explain why a track fits this brand, this scene or this audience, so the user still has to guess.
02
Discovery and rights live in different systems
A user finds something usable, then leaves your product to find out whether they are allowed to use it. That handoff is where workflows break.
03
Music expertise does not scale with headcount
The judgement that makes a good match is held by a few people. Encoding it into a product is the only way to serve every user, in every market, at once.
From scene to shortlist.
A sample walkthrough of the workflow an integration exposes, using curated example data. Step through it to see what each stage takes in and gives back.
Walk the stages
1. Scene or brief
Capture what the moment needs, in the user's own words.
The input is a scene description, a brief, or a video. Example: a thirty-second film, three locations, ending on a product close-up, tone confident but not aggressive, audience 25–40, German market.
- Input: text brief, structured parameters, or video
- No music knowledge required from the end user
This is a sample walkthrough with curated data, not a live API call. It does not show real response times, and the brand-fit reasoning shown is an explanation of method, not a validated accuracy score.
The stages above describe the workflow an integration exposes. Exact endpoints, payloads, authentication, limits and availability are covered under enterprise and partner access, we confirm them in writing during scoping rather than publishing unverified specifications here.
How an integration conversation runs
Access to Brand Studio and SceneMatch APIs is granted under enterprise and partner agreements, as described on our developer page. The path below reflects that access model.
- 01
Use case
You provide
The workflow you want to serve, your user type and the volume you expect.
You receive
An assessment of which capabilities apply and which are out of scope.
- 02
Technical scoping
You provide
Your architecture, data flow constraints and security requirements.
You receive
Confirmed integration surface, formats and the conditions attached to access.
- 03
Partner agreement
You provide
Commercial and legal contacts.
You receive
Written terms covering access, usage and support commitments.
- 04
Implementation
You provide
Engineering time and a test environment.
You receive
Credentials, documentation and a technical contact during build.
Capability matrix
What each capability takes in, what it returns, and how access works.
| Capability | Input | Output | Example product use | Access |
|---|---|---|---|---|
| SceneMatch™ | Scene description, brief or video | Ranked candidate tracks with musical attributes | Suggest music inside a video editor | Enterprise / partner |
| Brand Studio | Brand profile and asset library | Brand-constrained curation and guardrails | Keep a brand's teams inside approved music | Enterprise / partner |
| mDNA™ profile | Brand positioning and existing assets | Musical parameter set for the brand | Explain why a track fits a brand | Project engagement |
| Rights information | Candidate track and intended usage | Available usage information for the track | Show usage context beside a search result | Enterprise / partner |
How this is used today
Narrative-driven music matching
SceneMatch™
Matches music to visual content by analysing narrative and pacing rather than keywords alone.
Mehr lesenFrom scene description to music shortlist
What an integration needs to be worth building. Use this to frame an internal discussion.
- The user moment: where in your product does music get chosen?
- The input you can realistically capture: text, structured fields, or the video itself
- Whether a brand profile exists to constrain results
- What your user does with the shortlist next
- Whether rights information needs to appear in the same view
- Volume, markets and languages you expect to serve
- Who owns the integration after launch
Questions product teams ask
Brand Studio is about a brand's own musical world: profiles, approved assets and guardrails so teams stay consistent. SceneMatch™ is about matching music to content by analysing narrative and pacing. They are often used together, SceneMatch™ proposes, the brand profile constrains.
No. Discovery and rights are deliberately separate. Available rights information can be surfaced next to a candidate, but confirmation of permitted usage for your specific media, territory and term remains an explicit step.
We provide the matching, brand profiling and curation capability and the documentation for it. You implement the interface, your user permissions, your storage and how results are presented. Responsibilities are written into the partner agreement.
With the use case, not the endpoint. Tell us the workflow and the volume; we confirm which capabilities apply, then move to technical scoping and terms.
Documentation is provided under enterprise and partner access. Our developer page describes that access model; we do not publish endpoints, limits or authentication details publicly.