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.