Deezer vs Jamendo

Deezer's REST API serves the catalog metadata behind the streaming app: tracks, albums, artists, playlists, charts, and full-text search. Unusually for a major streaming service its read endpoints are fully keyless — a plain GET against api.deezer.com returns real track data with no App ID, key, or token at all — while OAuth is reserved for endpoints that act on a user's own account, such as favorites or the activity feed. Responses can be requested as either JSON or XML via an output query parameter, and the API is free to use within Deezer's terms.

Jamendo's API serves a catalog of roughly half a million independently released, Creative-Commons-licensed tracks, with over 20 read methods covering search, radios, and discovery plus write methods for managing a signed-in user's library. Reading the catalog only needs a free client_id issued on signup — full OAuth2 is reserved for the endpoints that act on a specific user's account — and responses can be requested as JSON, pretty-printed JSON, or XML. There's no published pricing tier for API access; it's free to use under Jamendo's terms.