Music · head-to-head
Jamendo vs Phishin
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.
Phish.in is a free, listener-run archive of legal live Phish recordings, covering shows, tracks, songs, venues, and tours through its v2 REST API. Read endpoints (shows, tracks, search) are fully public and keyless — a plain GET against /api/v2/shows returns real data with no credentials at all — while account-scoped features like playlists and likes require a logged-in user. The project is open source and privately funded, with an MCP endpoint also available for AI-assistant clients.
| Jamendo | Phishin | |
|---|---|---|
| Authentication | API Key | None |
| Pricing | free | free |
| Formats | JSON, XML | JSON |
| CORS | yes | yes |
| HTTPS | Yes | Yes |
Phishin needs no API key, while Jamendo requires API Key — pick Phishin to start without signup.