One Music API

Name: One Music API
Brand: One Music API
Availability: InStock

✓ Official Vendor SpecMediaAudio ProcessingapiKey5 EndpointsREST

For Agents

Search and resolve unified music metadata for artists, releases, and tracks across MusicBrainz, Discogs, and other upstream catalogues.

Install Jentic One Beta

Connect the One Music API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the One Music 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://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | 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 One Music API.

Search artists by name and return matching catalogue records

Search releases by title and return aggregated metadata

Search tracks by title across multiple upstream catalogues

Retrieve full artist details by their unified identifier

GET STARTED

Start building with One Music API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use One Music API for, with concrete tasks.

★ Music Catalogue Resolution

Resolve user-entered artist or album text into a clean unified id by searching across multiple upstream catalogues in one call. GET /artist/search and GET /release/search return ranked candidates so an agent or application can pick the best match without integrating MusicBrainz and Discogs separately.

Search for artists named 'Tame Impala' via /artist/search and pick the highest-confidence match by id.

Track Identification for Playlists

Identify the canonical metadata for a list of track titles supplied by users or extracted from audio recognition. GET /track/search returns matching tracks across catalogues, supporting deduplication and consistent display in playlist management tools.

Search /track/search for 'Bohemian Rhapsody' and return the top three candidate tracks with their release ids.

Album Detail Enrichment

Enrich a release record with credits, dates, and identifiers by calling GET /release/{releaseId} after a search. This supports building album detail pages without scraping or maintaining direct integrations to each upstream music database.

Retrieve full details for release id 'abc-123' via GET /release/{releaseId} and extract release date and primary artist credit.

Agent Music Lookups via Jentic

Music and entertainment agents resolve artists, releases, and tracks through Jentic without holding the One Music API key. The agent searches Jentic for the lookup intent, loads the schema, and executes the call with the user-supplied query string.

Use Jentic search 'search music artist' to locate /artist/search, load its schema, and execute a query for the user-supplied artist name.

Key Endpoints

5 endpoints — one music api aggregates music metadata from multiple sources including musicbrainz and discogs into a single search interface.

METHOD

PATH

DESCRIPTION

GET

/artist/search

Search for artists by name

GET

/artist/{artistId}

Get artist detail by id

GET

/release/search

Search for releases by title

GET

/release/{releaseId}

Get release detail by id

GET

/track/search

Search for tracks by title

GET

/artist/search

Search for artists by name

GET

/artist/{artistId}

Get artist detail by id

GET

/release/search

Search for releases by title

GET

/release/{releaseId}

Get release detail by id

GET

/track/search

Search for tracks by title

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

One Music API keys are stored encrypted in the Jentic vault (MAXsystem). Agents only ever hold a scoped reference, so the raw key never enters the agent context.

Intent-based discovery

Agents search Jentic with phrases like 'search music release' and the matching One Music endpoint surfaces with its input schema, ready to execute.

Time to first call

Direct integration: half a day for auth and response shaping. Through Jentic: under 30 minutes — search, load schema, execute.

FAQs

Specific to using One Music API through Jentic.

What authentication does the One Music API use?

The API uses an apiKey credential passed in a header. Through Jentic the key is stored encrypted in the vault and the agent receives a scoped reference, so the raw key never enters prompts or logs.

Can I search across MusicBrainz and Discogs with One Music API?

Yes. The artist, release, and track search endpoints aggregate matches from upstream catalogues including MusicBrainz and Discogs, returning a unified result set in a single response.

Does the One Music API expose track-level details by id?

The current spec exposes artist and release detail endpoints by id, plus a track search endpoint. Track-level detail typically comes from the linked release record retrieved via GET /release/{releaseId}.

What are the rate limits for the One Music API?

Rate limits are not declared in this OpenAPI spec. Consult onemusicapi.com/docs for the current per-key limits before scaling lookups for a large catalogue.

How do I look up an artist through Jentic?

Run pip install jentic, search 'search music artist', then load the /artist/search schema and execute with the artist name. Follow up with GET /artist/{artistId} for full detail when needed.