Company
AIMS API
AIMS API, as described on the show by Einar Helde.
Episodes (1)
Einar Helde, co-founder of AIMS API, explains how his bootstrapped machine-learning search finds catalog tracks by feel for production music companies.
Questions these episodes answer
How did AIMS API get paying customers before it launched?
The founders had spent over ten years in production music and knew the companies that lost their search tool when Spotify acquired and shut it down. They went straight to those existing contacts, and two or three agreed to pay before the product had a name.
Why did AIMS API build itself as an API instead of a platform?
Being API-first means AIMS integrates into other companies' existing music products rather than competing with them, so it avoids the customer support, price lists and signup systems a platform needs and can put its money into research, sales and product instead.
How does AIMS API's music search actually work?
A user pastes in a link to a track, such as one from YouTube, or types a description with the newer prompt search, and the system analyzes the audio to return catalog tracks with the same feel, rather than relying on keywords or tags.
Why does search speed matter so much for production music companies?
Helde says being first to answer a brief raises the odds of winning the job, since ad agencies tend to go with whoever replies fastest with the right sounding track, so faster search directly wins more sync placements for a company.
Why doesn't AIMS API build AI music generation tools?
Helde says the company deliberately avoids generative music because hundreds of millions of human-made tracks already exist, so the real problem worth solving is helping people find the right one rather than producing more music.