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

Yes. The API is mostly read and analysis operations, so you can write a rule that allows only lookups and feature extraction and leaves webhook changes out. Every call the agent makes is logged, so you can see exactly which tracks it analysed.

What authentication does the Music Metadata API use?

The Music Metadata API authenticates with an API key sent in the X-Api-Key header per its OpenAPI spec. Through Jentic the key is stored encrypted by your own instance and added to each request at call time, so it never appears in the agent's prompt or logs.

Can I use the Music Metadata API as a Spotify audio-features replacement?

Yes. Dedicated endpoints return audio features in a Spotify-compatible shape by identifier, including a batch form, so code written against the deprecated Spotify audio-features endpoint can switch over. You can also look up tracks by ISRC or MusicBrainz ID when you do not have a Spotify ID.

What are the rate limits for the Music Metadata API?

The OpenAPI spec does not state request rate limits for the Music Metadata API. For current limits and fair-use guidance, check the provider documentation at https://freqblog.com.

How do I analyze a track through Jentic?

Import the Music Metadata API from the Jentic API Directory, then have your agent issue a request such as 'get the BPM and key for this track'. Jentic matches the intent to the lookup operation and returns its input schema so the agent builds the correct request, with your stored key injected at call time. To run it on your own infrastructure, install Jentic One from its GitHub repo.