FreqBlog vs GetSongBPM
GetSongBPM is a long-running, free BPM and key database with a public API, and for plenty of projects it is all you need. The question is what your app needs beyond tempo and key — and how you look tracks up. If you are replacing Spotify’s discontinued audio-features endpoint, that usually means energy, valence and a Spotify ID or ISRC lookup, which is where the two differ. Every GetSongBPM claim below comes from its API page and the published documentation for its API (api.getsong.co, shared with its sister site GetSongKEY), checked on 28 October 2026.
At a glance
| Dimension | FreqBlog Music Metadata API | GetSongBPM API |
|---|---|---|
| Price | Free tier of 1,000 requests/month, no card; paid plans from £9.99/mo; Pro £129/mo for 750,000 requests (£0.17 per 1,000) | Free; no paid plans described |
| Conditions | Credit “Audio analysis by FreqBlog” somewhere users can find it — an about or credits screen is fine | A link back to GetSongBPM.com from your website or store listing is required; accounts without one can be suspended without notice |
| Rate limit | Monthly plan quota; over quota returns 429 until it resets | 3,000 requests per hour; exceeding it blocks the key for one hour |
| Track lookup input | Name + artist, ISRC, MusicBrainz ID or Spotify ID | Search by title and/or artist, then fetch by GetSongBPM’s own song ID; no ISRC or Spotify ID lookup documented |
| Fields returned | 25+ per track: BPM, key as name + Camelot + Open Key, energy, valence, danceability, acousticness, instrumentalness, mood, genre, ISRC, MBID and more | Tempo, key, Open Key, danceability (0–100), acousticness and a beta time signature; no energy, valence, loudness or instrumentalness |
| Tracks not yet covered | Analysed on demand: a 202, then served once ready | Not described in its API documentation |
| DJ / agent tooling | /transition, /next-track and /setlist set-builder; hosted MCP server at mcp.freqblog.com/mcp | None described in its API documentation |
| Pre-analysed catalogue | 1.7 Million+ tracks warm | Not stated on its API page |
When GetSongBPM is the better fit
For some projects it is simply the right tool:
- You need only tempo and key, and the budget is zero at volume. 3,000 free requests an hour is far more than FreqBlog’s free 1,000 a month.
- You already run a public website or store listing, so the mandatory backlink costs you nothing.
- You want a simple, long-established resource with community client libraries already written for it.
Why teams pick FreqBlog
- The rest of Spotify’s feature set. Energy, valence and instrumentalness alongside danceability and acousticness — the fields most apps built on Spotify’s
audio-featuresactually used, on the same 0–1 scale. - Look up the way your data is keyed. Name + artist, ISRC, MusicBrainz ID or Spotify ID, so a migration does not need a search-and-match step first.
- Built for harmonic mixing. Every key ships as name, Camelot and Open Key, and the set-builder orders a crate into a beat-matched, key-compatible arc.
- Batch and backfill.
/bulkresolves up to 50 tracks per call, and anything not yet analysed is queued and analysed on demand rather than returned empty. - Agent-native. A hosted MCP server lets LLMs and coding agents query the catalogue with no local setup.
- A named, accountable operator. Run by Steven Birring in Nuneaton, UK — an ICO-registered sole trader trading as Stackbase/FreqBlog.
FAQ
Is the GetSongBPM API free?
Yes. GetSongBPM’s API page says use is free, but a link back to GetSongBPM.com from your website or app-store listing is required, and accounts without one can be suspended without notice. Requests are limited to 3,000 per hour; going over blocks the key for an hour.
Does GetSongBPM return energy or valence?
Not in its documented API response. It returns tempo, key (including Open Key notation), danceability, acousticness and a beta time signature. If your app used Spotify’s energy, valence or instrumentalness, you need a source that computes them — FreqBlog returns all three.
Can I look up a track by ISRC or Spotify ID?
With FreqBlog, yes — ISRC, Spotify ID, MusicBrainz ID or plain name + artist. GetSongBPM’s documented lookups are a title/artist search followed by a fetch by its own song ID; we found no ISRC or Spotify ID lookup in its documentation.
Moving from GetSongBPM: what changes in my code?
Mostly scale. GetSongBPM documents danceability as an integer from 0 to 100, and client libraries report tempo arriving as a string; FreqBlog returns floats — danceability, acousticness, energy and valence on Spotify’s 0–1 scale and BPM as a number — so divide old thresholds by 100.