canonical: https://jentic.com/apis/audiometa.io/audiometa

# audiometa.io Web API

The Audiometa API serves music metadata for artists, albums, and tracks, with catalog search and enrichment such as social stats, playcounts, and audio features. You can search across artists, albums, and tracks, fetch an artist with biography, genres, and country, pull an album with its label, UPC, type, and release date, and read a track with its playcounts and audio features. Tracks can also be browsed by musical key, by a tempo range, or by record label, with sorting and paging.

## For AI agents

Search music metadata for artists, albums, and tracks, and read enrichment such as genres, playcounts, and audio features. Authenticates with a bearer token or an x-api-key header.

## Scope

Does not stream audio, host files, or sell music. Use for looking up music catalog metadata and audio features only.

## Capabilities

- Search across artists, albums, and tracks
- Get an artist with stats, biography, genres, and country
- Get an artist's albums, tracks, top tracks, and related artists
- Get an album with its label, UPC, type, and release date
- Get a track with its playcounts and audio features
- Browse tracks by musical key, tempo range, or record label

## Use cases

### Agent Music Metadata Lookup

An AI agent connected through Jentic searches the catalog for an artist or track and reads back structured metadata, so it can answer questions or enrich a record without scraping a music site. Because the response carries genres, playcounts, and audio features as fields, the agent acts on the data directly.

Example prompt: Search for an artist, then return their top tracks with each track's audio features

### Playlist by Audio Features

A music app browses tracks within a tempo range and by musical key, then sorts the results, so it can assemble a set that fits a mood or mix without hand-picking songs. The by-tempo and by-key browse endpoints make feature-driven selection a single call each.

Example prompt: Return tracks between 120 and 128 BPM in a given key, sorted by popularity

### Catalog Enrichment

A pipeline resolves a list of track or album ids to full records with labels, release dates, and playcounts, so another system can enrich its own music library. Unknown ids return a not-found response, which keeps the enrichment step predictable.

Example prompt: For each track id, fetch its album, label, and release date and attach them to the record

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/v1/search` | Search the catalog |
| GET | `/v1/artists/{id}` | Get an artist |
| GET | `/v1/artists/{id}/top-tracks` | Get an artist's top tracks |
| GET | `/v1/albums/{id}` | Get an album |
| GET | `/v1/tracks/by-tempo` | Get tracks by BPM range |
| GET | `/v1/tracks/{id}` | Get a track |

## Key resources

- **Artists** — Artist records with stats, biography, genres, country, albums, tracks, and related artists
- **Albums** — Album records with label, UPC, type, release date, and track listings
- **Tracks** — Track records with playcounts and audio features, browsable by key, tempo, or label

## AI readiness

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

- **Score:** 46 / 100
- **Maturity:** Foundational
- **Dimensions:**
  - Foundational Compliance: 69 / 100
  - Developer Experience & Jentic Compatibility: 65 / 100
  - AI-Readiness & Agent Experience: 21 / 100
  - Agent Usability: 94 / 100
  - Security: 55 / 100
  - AI Discoverability: 78 / 100
- **View full report:** https://jentic.com/apis/audiometa.io/audiometa/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **Setup:** Wiring the Audiometa API by hand means creating a key, deciding whether to send it as a bearer token or an x-api-key header, and handling the offset and limit paging on every list. Through Jentic you install once, import Audiometa from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** You choose which operations your agent may call, so you can allow catalog search and reading artist, album, and track records and leave anything else out. Audiometa carries the search query and ids in the request and path, so your rules bound which read operations run, and every call the agent makes is logged.
- **Credential handling:** Your Audiometa 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' or 'get a track's audio features', and Jentic returns the matching Audiometa operation with its input schema so the agent calls the right endpoint without reading the reference docs.

## Related APIs

- **Spotify Web API** — Music catalog, playback, and metadata for artists, albums, and tracks
- **MusicBrainz API** — Open, community-maintained music metadata encyclopedia
- **Last.fm API** — Listening data, scrobbles, and music recommendations

## FAQ

### Is there an Audiometa MCP server?

You don't need an MCP server to give your agent the Audiometa API. Jentic connects it directly from the API Directory: import it, store your key once, and your agent can search the catalog and read track metadata straight away, with no extra server to run and no tool definitions to load into the agent's context.

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

Yes. Write a rule that allows the search and read operations the agent needs, such as searching the catalog and fetching artist and track records, and nothing else, and every call it makes is logged. The whole API is read-only, so no rule gives the agent any way to change your data.

### What authentication does the Audiometa API use?

The Audiometa API authenticates with a bearer token (an amsk_ key), and it also accepts the same key in an x-api-key header, per its OpenAPI spec. Through Jentic the key is stored encrypted by your own instance and added at call time, so it never appears in the agent's prompt or logs.

### Can I find songs by tempo or musical key with the Audiometa API?

Yes. The by-tempo browse endpoint takes a tempo range and the by-key endpoint takes a musical key, both with sorting and paging, so an agent can assemble a feature-matched set of tracks. Each track also carries its audio features for further filtering on your side.

### What are the rate limits for the Audiometa API?

Each API key is limited to 100 requests per minute according to the API's own description, enforced per key rather than per account. For current limits, see the Audiometa documentation at https://audiometa.io/dashboard/api.

### How do I look up music metadata with the Audiometa API through Jentic?

Import the Audiometa API from the Jentic API Directory, then have your agent issue a request such as 'search for this artist and return their top tracks'. Jentic matches the intent to the search and artist operations and returns their input schemas so the agent builds the right calls, with your stored key injected at call time. To run it on your own infrastructure, install Jentic One from its GitHub repo.