Melodie API

Name: Melodie API
Brand: Melodie API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentMediaAudio Processingnone14 EndpointsREST

For Agents

Search and download royalty-free music tracks from Melodie's catalogue, filtered by genre, mood, instrument, or purpose. Returns licensed audio files for video, podcast, and ad production.

Install Jentic One Beta

Connect the Melodie API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Melodie API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fmelod.ie%2Fmelodie" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fmelod.ie%2Fmelodie" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Melodie API.

Search the catalogue by free-text query, genre, mood, instrument, and intended purpose across /api/v1/tracks/search

Surface trending tracks in real time for content tooling that needs fresh music

Browse curated collections for thematic projects such as travel, fitness, or corporate explainers

GET STARTED

Start building with Melodie API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Melodie API for, with concrete tasks.

★ Video Editor Music Picker

Editorial and social-video tools embed Melodie search to give creators a royalty-free music picker scoped to their project. The /api/v1/tracks/search endpoint accepts mood, genre, and purpose filters in one request, returning a paged result the editor can audition without leaving the timeline. Integration takes a single afternoon because the API requires no authentication for catalogue browsing.

Call /api/v1/tracks/search with mood=upbeat, purpose=travel, max_duration=120, return the top 10 tracks with preview URLs.

Podcast Background Music Selection

Podcast production platforms surface Melodie trending and collection endpoints so hosts can pick intro and bed music aligned with episode themes. Trending data refreshes daily, which keeps libraries from feeling stale, and curated collections provide pre-vetted music sets for genres like business, true crime, or comedy.

Fetch the 'business podcast' collection from /api/v1/collections, then return the five tracks with the longest available loop region.

Generative Video Soundtrack Matching

AI video generation platforms call the Melodie taxonomy endpoints - moods, genres, instruments, purposes - to map a generated scene description to a structured music search. The taxonomy gives the LLM a fixed vocabulary to project natural-language scene mood onto, which produces more consistent music selection than free-text search alone.

Read the moods list from /api/v1/tracks/moods, map the scene description 'a tense chase through Tokyo at night' to mood=tense and genre=electronic, then run /api/v1/tracks/search.

AI Agent Music Sourcing

An AI agent embedded in a creator tool can take a natural-language brief - 'find me three acoustic tracks under two minutes for a wedding montage' - and resolve it into a structured Melodie search. Through Jentic, the agent loads the search schema and the moods/instruments/purposes taxonomies in one session and chains the calls without writing custom client code.

Search Jentic for 'find royalty-free music', load /api/v1/tracks/search, execute with mood=romantic, instrument=acoustic-guitar, max_duration=120, return three results with download URLs.

Key Endpoints

14 endpoints — the melodie api provides programmatic access to a royalty-free music catalogue licensed for use in video, podcast, advertising, and game projects.

METHOD

PATH

DESCRIPTION

GET

/api/v1/tracks/search

Faceted search across the track catalogue

GET

/api/v1/tracks/simplified_search

Lightweight search endpoint with reduced response payload

GET

/api/v1/tracks/trending

List currently trending tracks

GET

/api/v1/collections

Browse curated collections

GET

/api/v1/collections/{collection_safename}

Get tracks in a specific collection

GET

/api/v1/tracks/moods

List available mood tags

GET

/api/v1/tracks/genres

List available genre tags

GET

/api/v1/tracks/purposes

List available usage purpose tags

GET

/api/v1/tracks/search

Faceted search across the track catalogue

GET

/api/v1/tracks/simplified_search

Lightweight search endpoint with reduced response payload

GET

/api/v1/tracks/trending

List currently trending tracks

GET

/api/v1/collections

Browse curated collections

GET

/api/v1/collections/{collection_safename}

Get tracks in a specific collection

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring Melodie by hand means hand-coding each track search, collection, and taxonomy call against api.melod.ie and adding account credentials only where licensed downloads require them. Through Jentic you install once, import the Melodie API from the API Directory, store any download token once, and your agent calls it.

Permission scoping

Melodie's search and taxonomy endpoints are public reads and the collection id travels in the path (/collections/{collection_safename}), so scope the agent to the read operations it needs, such as searching tracks or listing collections. You choose the operations it may call, so a licensed download is included only if you add it.

Credential isolation

Any Melodie account token for licensed download flows is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'find royalty-free music for a video', and Jentic returns /api/v1/tracks/search with its full filter schema for mood, genre, instrument, purpose, and duration so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Melodie API through Jentic.

What authentication does the Melodie API use?

The OpenAPI spec declares no security scheme - catalogue browsing endpoints are open. Download endpoints typically require a licensed account; through Jentic any account credential is held in the encrypted vault and injected at request time.

Can I filter tracks by mood and instrument together with the Melodie API?

Yes. /api/v1/tracks/search accepts mood, genre, instrument, and purpose filters in the same request, and you can preload the allowed values from /api/v1/tracks/moods and /api/v1/tracks/instruments to drive a UI.

What are the rate limits for the Melodie API?

The OpenAPI spec does not declare quantitative rate limits. In practice catalogue search is generously rated for client-side use; download endpoints are gated by your licence tier. Watch for 429 responses and back off if seen.

How do I find a track for a specific scene through Jentic?

Run `pip install jentic`, search for `find royalty-free music`, load the /api/v1/tracks/search operation, and execute with the desired mood, genre, and max_duration. Jentic returns the matched tracks with preview URLs.

Does the Melodie API cover trending music?

Yes. The /api/v1/tracks/trending endpoint returns a daily-refreshed list of popular tracks in the catalogue, which is useful for keeping music libraries fresh in production tooling.

Can I limit what my agent is allowed to do with the Melodie API?

Yes. Because Jentic One is self-hosted, you decide which Melodie operations your agent may call and your own rules govern access. You can allow only the public read endpoints it needs, such as /api/v1/tracks/search, the mood, genre, and purpose taxonomy lists, and /api/v1/collections for browsing curated sets. A licensed download operation is included only if you explicitly add it, and any download token stays with your instance rather than the agent's context.