canonical: https://jentic.com/apis/theaudiodb.com/theaudiodb

# TheAudioDB API

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.

## For AI agents

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

## Scope

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

## Capabilities

- 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
- Monitor TheAudioDB API operational status and events

## Use cases

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

Example prompt: 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.

Example prompt: 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.

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

## Key endpoints

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

## Key resources

- **Search** — Search for artists, albums, and tracks by name
- **Lookup** — Look up specific artists, albums, or tracks by ID
- **List** — List discographies, music videos, top tracks, and trending items

## Why Jentic

- **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 handling:** 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.
- **Discovery method:** 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.

## Related APIs

- **Cloudinary** — Alternative media API
- **Mux** — Alternative media API

## FAQ

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