Watch artists for a label or a playlist curator
For: labels, managers, playlist curators and music newsletters who follow rising artists. One run is 2 calls and 3 credits.
Get an API key Run a step free
The job
Finding who is growing means reading each artist's listener and follower numbers in more than one place, then comparing them.
Web data or web intelligence?
Pages are made for listening, not for comparing. Structured answers give an artist's listeners, play count, tags and similar artists on one platform, and followers, track count and location on another, as fields you can sort.
The calls, in order
| Step | Call | What it gives you | Credits | Docs |
|---|---|---|---|---|
| 1 | POST /v1/music/lastfm/artist | listening: listeners, play count, tags, similar artists | 1 | Call and code |
| 2 | POST /v1/music/soundcloud/artist | audience: followers, tracks, likes, reposts, city and country | 2 | Fields |
What one run costs
fact The credits per call are the catalog's: 1 + 2 = 3 per run, so 3,000 credits per 1,000 runs. calculated At the plan prices on the pricing page that is about $23.88 per 1,000 runs on Production and $29.40 on Builder (plan price divided by its monthly credits, times the credits). The Free plan gives 100 credits a month with no card.Formula
Your runs a month
Real responses, step by step
fact Captured from https://api.foxapis.com on 19 November 2026 with the documented sample input of each call; every value below is from that response, shortened where long. The nightly check on the status page lists each of these calls as working.
Step 1: POST /v1/music/lastfm/artist
The input: {"artist":"Radiohead"}. A real response had these fields.
| Field | Value in that response |
|---|---|
name | Radiohead |
listeners | 8,521,189 |
playcount | 1,436,654,988 |
on_tour | false |
tags | rock |
similar_artists | Thom Yorke |
curl -X POST 'https://api.foxapis.com/v1/music/lastfm/artist' \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{"artist":"Radiohead"}'
Step 2: POST /v1/music/soundcloud/artist
The input: {"artist":"flume"}. A real response had these fields.
| Field | Value in that response |
|---|---|
user_id | 2,976,616 |
username | flume |
display_name | Flume |
followers | 2,228,944 |
following | 202 |
tracks_count | 412 |
curl -X POST 'https://api.foxapis.com/v1/music/soundcloud/artist' \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{"artist":"flume"}'
All of it as one script
The same 2 calls chained, with a key placeholder. Swap the inputs for your own.
// 2 calls, one job run. Put your key in YOUR_API_KEY.
const KEY = "YOUR_API_KEY", BASE = "https://api.foxapis.com";
async function call(method, path, input) {
const url = BASE + path + (method === "GET" ? "?" + new URLSearchParams(input) : "");
const r = await fetch(url, { method, headers: { Authorization: "Bearer " + KEY, "Content-Type": "application/json" }, body: method === "GET" ? undefined : JSON.stringify(input) });
if (!r.ok) throw new Error(path + " answered " + r.status);
return r.json();
}
const step1 = await call("POST", "/v1/music/lastfm/artist", {"artist":"Radiohead"}); // listening: listeners, play count, tags, similar artists
const step2 = await call("POST", "/v1/music/soundcloud/artist", {"artist":"flume"}); // audience: followers, tracks, likes, reposts, city and country
console.log({ step1, step2 });
What you could build
- A weekly sheet of listeners and followers for the artists you follow
- A similar-artists list to widen a watchlist
- A tag count to see which genres your list leans towards
Limits, plainly
One artist per call. The two platforms name artists differently, so you pass the name each one expects. We tested one artist on each on 19 November 2026.
Field lists and the rest of each data type: Every games and music field. Single calls with code in six languages: task APIs.
Other jobs: Track a product's open-source and launch momentum · Build a crypto and DeFi dashboard · Write a biomedical research brief · Analyse players and games for a gaming community · Give an AI agent structured answers instead of raw pages · Enrich a lead list with company and developer signals · Check a UK company and who controls it · Compare your app with a rival's on both phone stores · Profile a creator before a sponsorship · Check an open-source model and its repository before you adopt it · Profile a developer expert before you hire or sponsor · Check a person's claims before you hire or partner · Score a candidate against a role you describe · Prepare a sales brief on a company and score a prospect's message · Check how AI assistants show your domain · Research an investor before you pitch.
Source: live calls to https://api.foxapis.com on 19 November 2026. Values reflect that moment and those inputs. Credits per call are the catalog's.
How we calculate
- Cost per run and per 1,000 runs: The credits of each call in the run, added up (the catalog's credits per call), times 1,000 for 1,000 runs.
- Dollar figures: The plan's monthly price divided by its monthly credits, times the credits. Prices come from the plans file at build time and are never typed.
Data: the FoxAPIs catalog and plans, read 19 November 2026. Every other figure on this page is copied from the record, not calculated by us.
Run this free, then pay per call
Free to start: 100 credits, no card. Then from $10. Credits you buy never expire. Use them at your own pace. Get my free key
One call costs 1 credit. That is $7.96 per 1,000 calls on the Production plan and $9.80 on Builder (plan price divided by its monthly credits). The Free plan gives 100 credits a month with no card.
Building an AI agent?
- The FoxAPIs MCP server gives your agent every tool through one connection.
- Per-call pricing in credits: you pay for the calls your agent makes, with no seats.
- Free plan: 100 credits a month, no card, no monthly fee.