canonical: https://jentic.com/apis/onemusicapi.com/onemusicapi

# One Music API

One Music API aggregates music metadata from multiple sources including MusicBrainz and Discogs into a single search interface. The API exposes search across artists, releases, and tracks, plus detail endpoints for artists and releases by id. Responses bring together identifiers, release titles, dates, and credits drawn from upstream catalogues so applications can resolve a track or artist without integrating each underlying source separately.

## For AI agents

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

## Scope

Does not handle audio playback, lyrics, or licensing royalties - use for unified music metadata search and lookup only.

## Capabilities

- 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
- Retrieve release details including credits and dates by id

## Use cases

### 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.

Example prompt: 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.

Example prompt: 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.

Example prompt: 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.

Example prompt: 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

| 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 |

## Key resources

- **Artist** — Search artists by name and retrieve detail by id
- **Release** — Search releases by title and retrieve detail by id
- **Track** — Search tracks by title across upstream catalogues

## Why Jentic

- **Setup:** Wiring One Music API by hand means managing its API key and building each artist, release, and track lookup against api.onemusicapi.com yourself. Through Jentic you install once, import One Music API from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** One Music API endpoints are read-only searches and lookups for artists, releases, and tracks, so you limit the agent to the operations it needs, such as searching a release or fetching a track. It reads metadata and does nothing else unless you add operations to the allowed set.
- **Credential handling:** Your One Music API key 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.
- **Discovery method:** Agents search Jentic by intent such as 'search a music release' or 'look up an artist', and Jentic returns the matching One Music operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **MusicBrainz API** — MusicBrainz is one of the upstream sources One Music API aggregates, available directly with broader query power.
- **Spotify Web API** — Pair Spotify catalogue and playback data with One Music's broader metadata graph.
- **Stripe API** — Use Stripe to monetise music discovery and licensing apps built on One Music data.

## FAQ

### 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.

### Can I limit what my agent is allowed to do with the One Music API?

Yes. Because you run Jentic One yourself, your own rules decide which operations and credentials the agent may use, and the One Music API endpoints are all read-only searches and lookups for artists, releases, and tracks. You can restrict the agent to just the operations it needs, such as searching a release or fetching an artist by id, and leave the others out of its allowed set. Since these endpoints only read metadata, the agent cannot write or change anything, and it can call nothing beyond the operations you approve.