Last.fm
Last.fm is the long-running music recommendation, scrobbling, and music-data service operated by CBS Interactive. Its Web Services 2.0 API (the AudioScrobbler API at ws.audioscrobbler.com/2.0/) exposes catalog data (artists, albums, tracks, tags), charts, geo-listening data, user listening history (recent tracks, top tracks/albums/artists, weekly charts), and the Scrobbling 2.0 write surface (track.scrobble, track.updateNowPlaying, track.love). Every operation is dispatched through a single endpoint via the `method` parameter (e.g. `method=user.getRecentTracks`). Authentication uses an API key for reads and a signed (`api_sig`) session-key flow for writes. The API is free for non-commercial use; commercial use requires a separate agreement via partners@last.fm.
Solid contracts, transparent operations, and an easy start — typically complete on four or five facets with one clear soft spot.
API Evangelist profiles Last.fm the way a machine reads it — 74 machine-readable artifacts across 2 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Last.fm scores 62.6/100 (strong), with a separate agent-readiness read of 24/100 (agent aware). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.
Put this on your own site. The badge is drawn live from Last.fm's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/lastfm/"
title="Last.fm on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/lastfm.svg"
alt="Last.fm Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>
[](https://providers.apievangelist.com/providers/lastfm/)
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/lastfm/"
title="Last.fm on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/lastfm/card.svg"
alt="Last.fm Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>
More shapes, themes and sizes → · Score as JSON · How badges work
How we profile Last.fm
Each block below is one kind of artifact we hold for Last.fm. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 9
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Last.fm Album API
Album metadata, tagging, and search.
Last.fm Artist API
Artist metadata, similarity, tagging, top albums/tracks, and search.
Last.fm Auth API
Token, session, and mobile session acquisition for authenticated calls.
Last.fm Chart API
Global top artists, tags, and tracks.
Last.fm Geo API
Country-level top artists and tracks.
Last.fm Library API
A user's scrobbled artist library.
Last.fm Tag API
Tag metadata, similar tags, top albums/artists/tracks, and chart history.
Last.fm Track API
Track metadata, scrobbling, love/unlove, tagging, search.
Last.fm User API
User profile, friends, listening history, top entities, and weekly charts.
Scroll within the panel for all 9 ·
Postman Collections 2
A runnable collection turns the contract into something a developer can execute in seconds. We profile them because the fastest way to trust an API is to make a real call against it.
Ready-to-run Postman collections for exercising this provider's APIs.
Last.fm Album API
POSTMANOpen Collections 10
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
API Collection
OPEN COLLECTIONLast.fm Web Services API (2.0) Album API
OPEN COLLECTIONLast.fm Web Services API (2.0) Album Artist API
OPEN COLLECTIONLast.fm Web Services API (2.0) Album Auth API
OPEN COLLECTIONLast.fm Web Services API (2.0) Album Chart API
OPEN COLLECTIONLast.fm Web Services API (2.0) Album Geo API
OPEN COLLECTIONLast.fm Web Services API (2.0) Album Library API
OPEN COLLECTIONLast.fm Web Services API (2.0) Album Tag API
OPEN COLLECTIONLast.fm Web Services API (2.0) Album Track API
OPEN COLLECTIONLast.fm Web Services API (2.0) Album User API
OPEN COLLECTIONScroll within the panel for all 10 ·
Arazzo Workflows 10
Real integrations are rarely a single call. Arazzo describes the multi-step sequences — auth, then create, then confirm — so both a human and an agent can follow the choreography, not just the endpoints.
Multi-step API workflows described with the Arazzo specification.
Last.fm Album Genre Profile
Search for an album, resolve its full info and tracklist, then surface the community tags that define its genre.
ARAZZOLast.fm Artist Discovery
Search for an artist by name, resolve full metadata, then surface their top tracks and similar artists.
ARAZZOLast.fm Genre Artist Explorer
Take a genre tag's top artist, branch into similar artists, and pull that artist's top tracks.
ARAZZOLast.fm Geo Artist Spotlight
Find the top artist in a country, resolve their full profile, and list their top albums.
ARAZZOLast.fm Loved Tracks Insight
Read a user's loved tracks, resolve the latest one's full info, and surface the community tags that describe it.
ARAZZOLast.fm Now Playing Context
Read a user's most recent track, resolve its full info, and surface the community tags that describe it.
ARAZZOLast.fm Tag To Track Deep Dive
Resolve a tag's metadata, pull its top tracks, and fetch full info for the leading track.
ARAZZOLast.fm Track Radio Seed
Search for a track, resolve its full info, and build a similar-tracks radio seed — branching when no match is found.
ARAZZOLast.fm User Taste Profile
Read a user's profile, find their top artist for a period, and surface that artist's top tracks.
ARAZZOScroll within the panel for all 10 ·
Pricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the things the Kin Score reads for access clarity — renamed from commercial clarity in rubric 0.12, because a free statutory interface has access terms and no commercial ones.
Published pricing tiers and plan structures.
Lastfm Plans Pricing
PLANSRate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Lastfm Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Lastfm Finops
FINOPSFeatures 8
The notable capabilities this provider advertises, captured as structured features so they can be searched and compared instead of read one landing page at a time.
Notable capabilities this provider offers.
Music Metadata
Comprehensive metadata for artists, albums, and tracks including biographies, images, tags, and similar items
Scrobbling
Track submission API (Scrobbling 2.0) for recording listening history from any client or device
User Listening History
Access recent tracks, loved tracks, top artists, albums, and tracks for any user
Music Charts
Global and geographic top artists and tracks, plus tag-based and weekly user charts
Music Discovery
Similar artist and track recommendations powered by Last.fm's social listening data
Artist and Track Search
Full-text search across the Last.fm music catalog for artists, albums, and tracks
Tag Exploration
Browse music by community-applied tags to discover themed playlists and artists
User Social Data
Access user friends, listening comparisons, and shared music taste data
Scroll within the panel for all 8 ·
Semantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Lastfm Context
JSON-LDSpectral Rules 2
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
Last.fm API Rules
SPECTRALLast.fm API Rules
SPECTRALJSON Schema 8
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
Artist
JSON SCHEMALast.fm Album
JSON SCHEMALast.fm Artist
JSON SCHEMALast.fm Tag
JSON SCHEMALast.fm Track
JSON SCHEMALast.fm User
JSON SCHEMAScrobble
JSON SCHEMATrack
JSON SCHEMAScroll within the panel for all 8 ·
JSON Structure 3
JSON Structure captures the data shapes in a form built for tooling — a complement to JSON Schema that keeps the model machine-legible.
JSON Structure definitions describing this provider's data shapes.
Lastfm Album Structure
JSON STRUCTURELastfm Artist Structure
JSON STRUCTURELastfm Track Structure
JSON STRUCTUREExamples 9
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Artist Getinfo Response
EXAMPLELastfm Album Getinfo Example
EXAMPLELastfm Track Getinfo Example
EXAMPLETrack Scrobble Request
EXAMPLEScroll within the panel for all 9 ·
Security Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Use Cases 6
What developers actually build with this provider — captured so the catalogue answers 'what is this for', not just 'what does this expose'.
What developers build with this provider.
Music Player Scrobbling
Record tracks played in music apps to Last.fm user profiles for history and recommendations
Music Metadata Enrichment
Augment music catalogs with artist bios, album art, tags, and similar artist data
Personalized Charts
Display weekly, monthly, or all-time listening charts for users in applications
Music Discovery Features
Power recommendation engines with similar artist and track data from Last.fm
Social Listening
Show what friends are listening to and compare music tastes between users
Geographic Music Trends
Display top artists and tracks by country or region for localized music features
Resources
Every other property we hold for Last.fm — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 3
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 14
Pagination, idempotency, versioning, errors, and events
Scroll within the panel for all 14 ·
Build 18
SDKs, sample code, and the tooling you integrate with
Scroll within the panel for all 18 ·
Access & Security 3
Authentication, authorization, and security posture
Operate 4
Status, limits, changes, and where to get help
Commercial 5
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
Other 2
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/lastfm · machine-readable index on apis.io
This is an independent, third-party profile of Last.fm, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.