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://jentic.com/install.sh?src=apis&api=%2Fapis%2Fsetlist.fm%2Fsetlist-fm" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fsetlist.fm%2Fsetlist-fm" | 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 One

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?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring setlist.fm by hand means constructing each REST path under /rest/1.0 and handling artist, venue, and setlist lookups yourself. Through Jentic you install once, import setlist.fm from the API Directory, and your agent calls it.

Permission scoping

setlist.fm puts the artist mbid, venue id, and setlist id in the URL path (/1.0/artist/{mbid}, /1.0/venue/{venueId}), and all its operations are read-only lookups, so a rule can pin your agent to the search and lookup operations it needs. You choose the operations it may call, so it holds only that read access.

Credential isolation

setlist.fm needs no stored secret for these read operations, so there is no credential for the agent to hold; its prompt, logs, and context stay free of any key.

Intent-based discovery

Agents search Jentic by intent such as 'search for an artist' or 'get an artist's setlists', and Jentic returns the matching setlist.fm operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

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 your Jentic One instance 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 through Jentic One, the self-hosted execution layer, 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.

Can I limit what my agent is allowed to do with the setlist.fm API?

Yes. Because you run Jentic One yourself, your own rules decide which setlist.fm operations the agent may call, and every setlist.fm endpoint is a read-only lookup that takes identifiers like the artist mbid or venue id in the URL path. You can pin the agent to just the search and lookup calls it needs, such as GET /1.0/search/artists or GET /1.0/artist/{mbid}/setlists, so it holds only that read access and nothing more. Since these operations need no stored secret, there is no credential for the agent to hold either.

setlist.fm API

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

Developer 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.

Not supported: Does not handle payments, communications, or crm - use for developer tools only.

<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>... understand how setlist.fm works (the <a href="https://www.setlist.fm/faq">FAQ</a> and the <a href="https://www.setlist.fm/guidelines">Guidelines</a> are a good starting point),</li> <li>... read this do. The API exposes 15 endpoints.

Jentic One on Github View OpenAPI Document