Prowl
80/100
prowl
Benchmarked Sep 28, 2026

setlist.fm API

<p> The setlist.fm API has been designed to give you easy access to setlist data in order to build fancy websites and other applications. Before starting to use the API, be sure to ... <ol> <li>... un

dataapi platform_profile
Benchmark Your API

Score Breakdown

Latency10/10
Parseability9/10
Consistency8/10
Documentation8/10
Auth Simplicity8/10
Token Efficiency8/10
First-Try Success8/10
Error Clarity6/10

Benchmark Analysis Log

Full LLM thinking from the 4-phase benchmark pipeline.

Analyze
{
  "service_type": "platform",
  "base_url": "https://api.setlist.fm",
  "auth_method": "api_key",
  "auth_config": {
    "header": "x-api-key",
    "notes": "API key obtained via a setlist.fm user account; required on all requests"
  },
  "endpoints": [
    "/rest/1.0/search/setlists",
    "/rest/1.0/setlist/{setlistId}",
    "/rest/1.0/artist/{mbid}/setlists",
    "/rest/1.0/venue/{venueId}/setlists",
    "/rest/1.0/user/{userId}/attended",
    "/rest/1.0/search/artists",
    "/rest/1.0/search/venues"
  ],
  "pricing_model": {
    "type": "free",
    "details": {
      "notes": "Free API access for registered users, subject to terms and attribution requirements"
    }
  },
  "rate_limits": {
    "notes": "Fair-use limits apply; typical usage limits around 2 requests/second and daily caps. Consult official docs for current values."
  },
  "capabilities": [
    "Search setlists by artist, venue, date, city, country, and tour",
    "Retrieve setlist details for a given setlist ID",
    "Look up artist setlists by MusicBrainz ID (MBID)",
    "Look up venue setlists by venue ID",
    "Retrieve a user's attended concerts and setlists",
    "Search artists and venues",
    "Music catalog and live performance data"
  ],
  "raw_analysis": "setlist.fm is a community-driven database of live concert setlists and related concert metadata. The setlist.fm API provides programmatic access to this dataset, enabling developers to build websites and applications that consume setlist data, concert history, artist and venue information, and user attendance records.\n\nThe API is RESTful, returns JSON (and supports XML in some versions), and requires an API key tied to a setlist.fm user account. Authentication is handled via an x-api-key header. The base endpoint is https://api.setlist.fm/rest/1.0/.\n\nKey use cases include: concert tracking apps, music discovery and fan sites, artist tour analytics, venue and festival aggregators, playlist generation based on live performances, and music journalism/research tools. Common endpoints cover setlist search and retrieval, artist setlists by MBID, venue setlists by venue ID, and user attendance data.\n\nThe platform is mature and widely used in the music/concert data ecosystem. Data is community-contributed and linked to MusicBrainz for artist/venue identification, which improves cross-referencing. The API is free to use with attribution and fair-use rate limits; high-volume commercial use may need to respect terms or contact the maintainers.\n\nIntegration considerations: the API key must be kept secret; requests are subject to rate limits; responses can be paginated; and results depend on community data quality and completeness. As a platform in the music/live-events data category, it complements streaming services, ticketing platforms, and music metadata providers."
}
Execute

1/3 tests passed

TestEndpointStatusLatency
website_uptimeGET /200124ms
robots_txtGET /robots.txt40460ms
llms_txtGET /llms.txt40460ms
Interpret
{
  "overall": 74,
  "dimensions": {
    "token_efficiency": 8.5,
    "first_try_success": 8.0,
    "response_parseability": 9.0,
    "error_clarity": 6.5,
    "doc_quality": 7.5,
    "auth_simplicity": 7.5,
    "latency": 9.5,
    "consistency": 7.5
  },
  "pricing_normalized": {},
  "issues": [
    "No robots.txt (404) — search/agent crawlers have no guidance",
    "No llms.txt (404) — no agent-optimized documentation index",
    "Missing security headers on root response",
    "Auth model not fully described; free access requires registration with attribution terms",
    "No status page or uptime signals referenced in checked endpoints"
  ],
  "recommendations": [
    "Publish /llms.txt summarizing endpoints, auth, and attribution requirements for agent onboarding",
    "Add robots.txt with clear crawl permissions for agent tooling",
    "Document the API key/registration flow with a copy-paste quickstart (curl + JSON example) to reduce first-try friction",
    "Surface rate limits and error code semantics explicitly so agents can handle failures without guessing",
    "Add security headers (HSTS, CSP, X-Content-Type-Options) for trust signal parity with premium APIs",
    "Link a status page or uptime badge to improve consistency perception",
    "Publish a MusicBrainz-ID mapping note for setlist.fm / Last.fm ecosystem interoperability"
  ]
}

Agent Readiness

x402 Payments
Not supported
Streaming
No
Sandbox
None
Agent Auth
Unknown
SDKs
None listed
MCP Support
No

Embed your Prowl badge

Show your live agent-readiness score on your own site. Free, no auth — it updates as your score changes.

Prowl agent-readiness badge
<a href="https://prowl.world/service/setlistfm-api">
  <img src="https://prowl.world/badge/setlistfm-api.svg" height="56" alt="Agent-readiness on Prowl">
</a>

Options: ?style=light|dark · ?size=sm|md · ?variant=certified (claimed + DNS-verified only) · badge generator with preview

Want the full interactive view?

See operational metrics, LLM evaluations, agent readiness, and more.

Open in Dashboard