Can I look up a track by ISRC with the Odesli API?

Yes. Where you do not pass url, the docs require platform, type and id together. isrc and upc are both listed as supported platform values, and type accepts song or album, so an ISRC lookup is platform=isrc with type=song and the ISRC as id. The response returns linksByPlatform plus per-platform identifiers in entitiesByUniqueId.

What are the rate limits for the Odesli API?

Without an API key the documented rate limit is 10 requests per minute. Odesli's docs say the limit with an API key is higher, without publishing a number. The same docs add that while the v1-alpha.1 namespace is deprecated, requests are subject to stricter per-IP daily limits and over-quota requests return 429 Too Many Requests. Cache responses where you can, since track-to-link mappings are stable.

Is the Odesli API being retired?

Odesli's API doc carries a deprecation notice for the whole v1-alpha.1 namespace, giving an announced retirement date of July 31, 2026, after which it says all v1-alpha.1 endpoints return 410 Gone. The endpoint was still returning HTTP 200 with full link data when Jentic last checked it on 2026-08-12. Treat the surface as deprecated but answering: handle 410 and 429 responses in your agent's error path.

Is there an Odesli MCP server?

You don't need an MCP server to give your agent the Odesli API. Jentic connects it directly from the API Directory: import Odesli, store your optional key once, and your agent calls the /links operation without another server's tool definitions loaded into its context.

Why is there no official OpenAPI specification for the Odesli API?

Odesli documents the API as a help-centre page rather than a machine-readable file: the reference is a Notion doc reached from odesli.co/help and from the songlink/docs repository on GitHub, and no OpenAPI document is published alongside it. Jentic wrote and validated the specification in the API Directory from that documentation, covering the single GET /links operation and its url, platform, type, id, userCountry, songIfSingle and key query parameters.

How do I convert a Spotify link to other services through Jentic?

Search Jentic for 'convert music link', load the schema for the /links operation, and execute with the Spotify URL as the url parameter. The response returns linksByPlatform, keyed by platform, with a url for each match; read the key for the service you want.

Which streaming services does the Odesli API support?

The documented platform list is spotify, itunes, appleMusic, youtube, youtubeMusic, google, googleStore, pandora, deezer, tidal, amazonStore, amazonMusic, soundcloud, napster, yandex, spinrilla, audius, anghami, boomplay, audiomack, bandcamp, plus isrc and upc as identifier types. A platform key appears in the response only where a match was found, and userCountry sets the country used when searching streaming catalogues.

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

Yes. The Odesli API exposes a single read-only operation, the /links endpoint, with no resource id in the path, so you scope access by operation from your own self-hosted Jentic One instance. You write the rules that decide the agent may call only the links-resolution operation, turning any music URL or platform ID into matched cross-service links, and nothing else. Because your Jentic One holds the optional key query parameter and appends it at request time, the agent never sees the credential and cannot reach operations you have not allowed.