Libraries 2026
musicbrainzc3
Find the MusicBrainz IDs behind a Spotify, Last.fm, or barcode lookup.
musicbrainzc3 reads the MusicBrainz database through its web service. Its job is narrow and useful: find the MusicBrainz IDs (MBIDs) behind what other services give you, so one artist, recording, or release can be tied together across Spotify, Last.fm, and local files.
It sends HTTP through httpc3 and uses C3’s standard library for JSON. It has no UI code.
Lookup by URL
MusicBrainz links its entities to pages on other services. Given a Spotify artist URL or a Last.fm artist page, the client returns the artists, releases, recordings, and release groups MusicBrainz associates with it. Up to 100 URLs can be sent in one batch.
MusicBrainz matches a URL’s exact text, so normalize_url turns the links people paste — …/intl-de/artist/…?si=…, spotify:artist:…, http://last.fm/… — into the form the database stores. Lookups apply it automatically.
Releases and tracks
Release search covers title, artist, track count, barcode, and release group, best score first. That is how an album with poor tags finds its release. Once found, the client returns the release’s media and every track’s position, number, title, length, recording, and ISRCs, which is the data a tagger needs to match files to recordings.
ISRC and barcode
lookup_by_isrc returns the recordings with a given ISRC and their artist credits, optionally with the releases each recording appears on. Barcode search handles UPC and EAN (including the UPC-A/EAN-13 equivalence), returning exact matches with labels and release groups.
Status
0.2. The calls work against the live service; the API may still change. Glaze uses it alongside spotc3 and lastfmc3 to reconcile the same music across services.