Skip to content
Busk Map
Taste data from the Qloo API

Taste data from the Qloo API: The brain
of Busk Map

Qloo knows who likes what, and where. Busk Map asks it 18 kinds of question, and every answer lands somewhere in your busk.

Qloo calls go through NotOnQ when configured, Qloo direct otherwise.

  • 18kinds of Qloo call
  • 28–37Qloo calls for a new busk
  • 0on a rerun: answers cached for 24 h
  • 10parts of your busk it decides
  • ≤ 25Qloo calls per learn run

The wiring

  • Qloo
  • Spotify, Ticketmaster, Last.fm
  • The path you picked

Qloo calls18 kinds

With three other sources

Data pointswhat comes back

Your buskwhat it decides

Pick any piece

  • Try Set and songs to learn: four Qloo calls, Spotify and Last.fm meet in your suggested set
  • Try Taste heatmap: one call that shapes the map and the ranking

Notes

Meet the Hive

The Hive is Busk Map's research agent. The Hive picks which Qloo questions to ask, but never makes up a number.

Numbers come from data

The Hive, our agent, picks which Qloo questions to ask, but never makes up a number: it can only choose among pitches Busk Map's engine scored, and a busk that cites a number no call returned is rejected.

Light on the quota

Answers are cached for 24 hours, and Busk Map paces its own calls to 3 a second, so a rerun makes no new calls.

Next · not built yet

  • Taste from genres as well as artists, for the taste map
  • Searching Qloo’s genre list directly
  • A nearest-neighbourhood retry when a city area comes back empty
Back to Busk Map