setlist.fm API

Name: setlist.fm API
Brand: setlist.fm API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentDeveloper ToolsSource Controlnone15 EndpointsREST

For Agents

Programmatically ., .. Covers 15 operations.

Use for: I need to ., I want to ., Search for a city by its unique geoid., Find all for artists.

Install Jentic One Beta

Connect the setlist.fm API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the setlist.fm API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with setlist.fm API.

Get a city by its unique geoId.

Search for artists.

Query and filter setlist.fm API records by parameters

GET STARTED

Start building with setlist.fm API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use setlist.fm API for, with concrete tasks.

★ Developer Tools Operations

Use the setlist.fm API to perform developer tools operations programmatically. The API provides 15 endpoints covering core functionality including ., ., get a city by its unique geoid..

Call GET /1.0/artist/{mbid} to .

Automated /1.0/artist/{mbid} Management

Automate /1.0/artist/{mbid} operations by combining multiple setlist.fm API endpoints. Agents can . and then get a city by its unique geoid. in a single workflow.

Call GET /1.0/artist/{mbid}/setlists to ., then verify the result

AI Agent Integration via Jentic

AI agents discover and call setlist.fm API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle none tokens manually.

Search Jentic for '.', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

15 endpoints — <p> the setlist.

METHOD

PATH

DESCRIPTION

GET

/1.0/artist/{mbid}

GET

/1.0/artist/{mbid}/setlists

GET

/1.0/city/{geoId}

Get a city by its unique geoId.

GET

/1.0/search/artists

Search for artists.

GET

/1.0/search/cities

Search for a city.

GET

/1.0/search/countries

Get a complete list of all supported countries.

GET

/1.0/search/setlists

Search for setlists.

GET

/1.0/search/venues

Search for venues.

GET

/1.0/artist/{mbid}

GET

/1.0/artist/{mbid}/setlists

GET

/1.0/city/{geoId}

Get a city by its unique geoId.

GET

/1.0/search/artists

Search for artists.

GET

/1.0/search/cities

Search for a city.

GET

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

setlist.fm API none credentials are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens — raw secrets never enter the agent context.

Intent-based discovery

Agents search by intent (e.g., '.') and Jentic returns the matching setlist.fm API operation with its input schema, so the agent can call the right endpoint without browsing docs.

Time to first call

Direct setlist.fm API integration: 1-3 days for auth handling, response parsing, and error cases. Through Jentic: under 1 hour — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Github

Alternative developer tools API

Choose Github when you need a different approach to developer tools operations

Alternative

Gitlab

Alternative developer tools API

Choose Gitlab when you need a different approach to developer tools operations

FAQs

Specific to using setlist.fm API through Jentic.

What authentication does the setlist.fm API use?

The setlist.fm API uses no authentication. Through Jentic, these credentials are stored encrypted in the MAXsystem vault and injected at execution time, so raw secrets never enter the agent context.

Can I . with the setlist.fm API?

Yes. Use the GET /1.0/artist/{mbid} endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the setlist.fm API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

How do I . through Jentic?

Install the Jentic SDK with pip install jentic, authenticate at https://app.jentic.com/sign-up, then search for '.'. Jentic returns the matching setlist.fm API operation with its input schema. Load the schema and execute the call — credentials are injected automatically.

How many endpoints does the setlist.fm API have?

The setlist.fm API exposes 15 endpoints covering /1.0/artist/{mbid}, /1.0/artist/{mbid}/setlists, /1.0/city/{geoid} operations.