Skip to content
APIStead
MediaBundle v1

Spotify Artist Research

Search an artist, map the full discography and find adjacent playlists.

$0.03-$0.15

estimated cost / run

5

API steps

-

measured success rate

Preview

paid run not yet recorded

What this bundle does

Music research starts with a name, but a name is not an artist id. An agent needs to search the catalogue, disambiguate the result, then walk outward from the artist into releases, adjacent artists and curated playlists.

This bundle combines five routes from the Spotify API v2 listing. The agent searches for the artist, resolves the canonical profile, reads the complete discography, finds related artists and collects the artist's playlist sections. Every call returns normalized JSON with a source and retrieval timestamp. Playlists return every ordered track with no song limit, and each route is priced at $0.03 per call.

Workflow

  1. 1

    Search for the artist and resolve the correct Spotify id.

    Spotify API v2 for AI Agents
    GET/spotify/search$0.03
  2. 2

    Fetch canonical artist metadata, image and world rank.

    Spotify API v2 for AI Agents
    GET/spotify/artist$0.03
  3. 3

    Read the artist's complete release discography.

    Spotify API v2 for AI Agents
    GET/spotify/artist/discography$0.03
  4. 4

    Find adjacent artists for recommendations.

    Spotify API v2 for AI Agents
    GET/spotify/artist/related$0.03
  5. 5

    Collect the artist's playlist sections.

    Spotify API v2 for AI Agents
    GET/spotify/artist/playlists$0.03

Agent prompt

Paste this into an agent that can call HTTP tools and pay x402 challenges.

copy into your agent
You are a music research agent. When the user names an artist:

1. Call the Spotify search route with the artist name and type=artist. If more than one strong match appears, ask the user to choose or use the most specific result.
2. Call the artist route with the chosen Spotify artist URL or id. Keep the name, image, followers, monthly listeners and world_rank values.
3. Call the artist discography route. Keep albums, singles, compilations and appearances; mark complete when the response says the full discography was read.
4. Call the related artists route. Keep a short list of adjacent artists with names and ids.
5. Call the artist playlists route. Keep playlists owned by or associated with the artist, including discovered-on and featuring sections when present.
6. Return one object with: artist, discography, related_artists, playlists, source and retrieved_at.
7. If a route returns 402, read the quoted price and network before paying. Never pay more than the amount shown in the challenge.
8. If a route returns an error, report which step failed and do not invent a value.

Example output

Illustrative output. Sample values come from the preview routes, not a live run.

application/json
{
  "artist": {
    "id": "4tZwfgrHOc3mvqYlEYSvVi",
    "name": "Daft Punk",
    "url": "https://open.spotify.com/artist/4tZwfgrHOc3mvqYlEYSvVi",
    "world_rank": 98
  },
  "discography": {
    "albums": [
      {
        "name": "Random Access Memories",
        "release_date": "2013-05-17"
      }
    ],
    "singles": [
      {
        "name": "Get Lucky",
        "release_date": "2013-04-19"
      }
    ],
    "complete": true
  },
  "related_artists": [
    {
      "name": "Justice",
      "id": "1dRNo1n3b2p9c1xW7m8kQe"
    }
  ],
  "playlists": [
    {
      "name": "Daft Punk Essentials",
      "track_count": 50
    }
  ],
  "source": "spotify",
  "retrieved_at": "2026-11-12T00:00:00Z"
}

Use cases

  • Build an artist profile for an editorial feature
  • Power a recommendation agent with discography and related artists
  • Find curated playlists for a release campaign
  • Research a catalogue before a licensing or sync conversation