Install Jentic One Beta

Connect the TheAudioDB API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the TheAudioDB 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%2Ftheaudiodb.com%2Ftheaudiodb" | 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%2Ftheaudiodb.com%2Ftheaudiodb" | 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 TheAudioDB API.

Search for an artist by name

Look up an artist by ID

List an artist's discography

Query and filter TheAudioDB API records by parameters

GET STARTED

Start building with TheAudioDB API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use TheAudioDB API for, with concrete tasks.

★ Media and Content Operations

Use the TheAudioDB API to perform media operations programmatically. The API provides 7 endpoints covering core functionality including search for an artist by name, search for an album by name, search for a track by name.

Call GET /search/artist/{text} to search for an artist by name

Automated Search Management

Automate search operations by combining multiple TheAudioDB API endpoints. Agents can search for an album by name and then search for a track by name in a single workflow.

Call GET /search/album/{text} to search for an album by name, then verify the result

AI Agent Integration via Jentic

AI agents discover and call TheAudioDB 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 apiKey tokens manually.

Search Jentic for 'search for an artist by name', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

7 endpoints — theaudiodb is a community-driven music database providing information about artists, albums, tracks, and music videos.

METHOD

PATH

DESCRIPTION

GET

/search/artist/{text}

Search for an artist by name

GET

/search/album/{text}

Search for an album by name

GET

/search/track/{text}

Search for a track by name

GET

/lookup/artist/{id}

Look up an artist by ID

GET

/lookup/album/{id}

Look up an album by ID

GET

/lookup/track/{id}

Look up a track by ID

GET

/list/discography/{artistId}

List an artist's discography

GET

/search/artist/{text}

Search for an artist by name

GET

/search/album/{text}

Search for an album by name

GET

/search/track/{text}

Search for a track by name

GET

/lookup/artist/{id}

Look up an artist by ID

GET

/lookup/album/{id}

Look up an album by ID

Why Jentic?

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

Setup

Wiring TheAudioDB by hand means passing your API key against www.theaudiodb.com and handling each search and lookup endpoint yourself. Through Jentic you install once, import TheAudioDB from the API Directory, store the key once, and your agent calls it.

Permission scoping

TheAudioDB is read-only and puts the artist, album, and track ids in the URL path (/lookup/artist/{id}, /list/discography/{artistId}), so a rule can pin your agent to lookups for one resource. You choose the operations it may call, so it only reaches the endpoints you include.

Credential isolation

Your TheAudioDB API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'search for an artist by name' or 'look up an album's tracks', and Jentic returns the matching TheAudioDB operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using TheAudioDB API through Jentic.

What authentication does the TheAudioDB API use?

The TheAudioDB API uses an API key passed in the `X-API-KEY` header. 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 search for an artist by name with the TheAudioDB API?

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

What are the rate limits for the TheAudioDB 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 search for an artist by name through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'search for an artist by name'. Jentic returns the matching TheAudioDB API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

How many endpoints does the TheAudioDB API have?

The TheAudioDB API exposes 7 endpoints covering search, lookup, list operations.

Can I limit what my agent is allowed to do with the TheAudioDB API?

Yes. Because you run Jentic One yourself, your own rules decide which TheAudioDB operations and credentials the agent may use. TheAudioDB is read-only and takes artist, album, and track ids in the URL path, so you can allow only the searches and lookups you need, such as GET /search/artist/{text} or GET /lookup/album/{id}, and pin the agent to a single resource like GET /list/discography/{artistId}. Any endpoint you do not include stays off limits, and the stored API key is injected only when an allowed call runs.

TheAudioDB API

Name: TheAudioDB API
Brand: TheAudioDB API
Availability: InStock

Official vendor OpenAPI document · agent-readyMediaVideo ProcessingapiKey7 EndpointsREST

For Agents

Programmatically search for an artist by name, search for an album by name. Covers 7 operations with apiKey authentication.

Use for: I need to for an artist by name, I want to for an album by name, Search for for a track by name, Find all look up an artist by id

Not supported: Does not handle payments, communications, or crm - use for media and content only.

TheAudioDB is a community-driven music database providing information about artists, albums, tracks, and music videos. It offers search, lookup, and listing endpoints for comprehensive music metadata. The API exposes 7 endpoints secured with apiKey authentication.

Jentic One on Github View OpenAPI Document

Connect the TheAudioDB API to your agent

Capabilities

Start building with TheAudioDB API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

TheAudioDB API