Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the SimpMusic Lyrics API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Flyrics.simpmusic.org%2Flyrics-simpmusic" | shStep 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Flyrics.simpmusic.org%2Flyrics-simpmusic" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
What an agent can do with SimpMusic Lyrics API.
Look up synced or plain lyrics by video id
Search lyrics by free text, song title, or artist
Fetch community translations by video id and language
Contribute a new lyric or a translated lyric
Vote on the accuracy of a lyric or a translation
GET STARTED
Patterns agents use SimpMusic Lyrics API for, with concrete tasks.
★ Serve lyrics to an AI agent
An AI agent integration created through Jentic needs the words to a track. The SimpMusic Lyrics API returns synced or plain lyrics for a video id and supports search by title or artist, so the agent can fetch and display lyrics inside a music or chat experience without maintaining its own lyrics store.
Search lyrics by song title, then fetch the synced lyrics for the matching video id
Show translated lyrics
Listeners often want lyrics in another language. The SimpMusic Lyrics API fetches community translations for a video id and a specific language, so an automation can present a translated version alongside the original and fall back to the plain lyrics when no translation exists.
Fetch the translated lyrics for a video id in a chosen language
Crowdsource lyric contributions
Missing or wrong lyrics improve through contributions. The SimpMusic Lyrics API lets a caller submit a new lyric or translation and vote on accuracy, so an agent can add lyrics it has verified and raise the ranking of correct entries, with contribution calls signed by an HMAC header.
Submit a new lyric for a video id and vote on an existing translation
10 endpoints — the simpmusic lyrics api serves synced and plain song lyrics along with community-contributed translations.
METHOD
PATH
DESCRIPTION
/v1/search
Search lyrics
/v1/{videoId}
Get lyrics by video ID
/v1
Create a new lyric
/v1/vote
Vote for a lyric
/v1/translated/{videoId}
Get translated lyrics by video ID
/v1/translated
Create a translated lyric
/v1/search/artist
Search lyrics by artist
/v1/search
Search lyrics
/v1/{videoId}
Get lyrics by video ID
/v1
Create a new lyric
/v1/vote
Vote for a lyric
/v1/translated/{videoId}
Get translated lyrics by video ID
/v1/translated
Create a translated lyric
/v1/search/artist
Search lyrics by artist
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the SimpMusic Lyrics API by hand means signing contribution requests with an HMAC header while leaving read and search calls unauthenticated. Through Jentic you install once, import SimpMusic Lyrics from the API Directory, store the signing key once, and your agent calls it.
Permission scoping
The video id sits in the URL path for reads, so a rule can keep your agent read-only by allowing only the lookup and search operations. You choose the operations it may call, so contribution operations like creating lyrics or voting are not included unless you add them.
Credential isolation
Your SimpMusic signing 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.
Intent-based discovery
Agents search Jentic by intent such as 'get lyrics by video id' or 'search lyrics by artist', and Jentic returns the matching SimpMusic Lyrics operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Alternatives and complements available in the Jentic catalogue.
Specific to using SimpMusic Lyrics API through Jentic.
What authentication does the SimpMusic Lyrics API use?
The read and search endpoints of the SimpMusic Lyrics API are public and need no credential, while the contribution endpoints that create lyrics, add translations, or vote require an HMAC signature in the X-HMAC header, per its OpenAPI spec. Through Jentic the signing key is stored encrypted by your own Jentic One instance and injected at call time.
Can I search for lyrics with the SimpMusic Lyrics API?
Yes. The search endpoint accepts free text, and dedicated endpoints search by song title or artist, so an agent can find a track and then fetch its synced or plain lyrics by video id.
What are the rate limits for the SimpMusic Lyrics API?
The SimpMusic Lyrics API spec documents a limit of 30 requests per minute per IP address, applied across all endpoints, with rate-limit headers returned on responses. Design agent flows to stay within that ceiling and back off when it is reached.
How do I fetch song lyrics through Jentic?
Install Jentic One on your own infrastructure with `curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh`, then import the SimpMusic Lyrics API from the API Directory and search for 'get song lyrics by video id'. Reads need no credential, and storing the HMAC key once lets your agent contribute too. To run it on your own infrastructure, install Jentic One from its GitHub repo.
Is there a SimpMusic Lyrics MCP server?
You don't need an MCP server to give your agent the SimpMusic Lyrics API. Jentic connects it directly from the API Directory: import it, and your agent calls the public read endpoints or signs contributions, with operations discovered on demand instead of loaded into the agent's context.
Can I limit what my agent is allowed to do with the SimpMusic Lyrics API?
Yes. The video id sits in the URL path for reads, so a rule can allow only the lookup and search operations, keeping the agent read-only while contribution operations like creating lyrics or voting stay out of reach unless you add them. Every action it takes is recorded in an audit log.
Know of an official OpenAPI document? Contribute it →
For Agents
Look up and search synced or plain song lyrics, fetch community translations, and contribute lyrics or votes through the SimpMusic Lyrics API.
Use for: Get the lyrics for a given video id, Search lyrics by song title, Find lyrics by artist name, Fetch a translation of a song in a language
Not supported: Does not stream audio, host music files, or manage playlists. Use for retrieving, searching, and contributing song lyrics and translations only.
The SimpMusic Lyrics API serves synced and plain song lyrics along with community-contributed translations. It lets a caller look up lyrics by video id, search by free text, song title, or artist, fetch translated lyrics by language, and contribute new lyrics, translations, and votes. Read and search endpoints are public, while contribution endpoints are signed with an HMAC header.
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.
Base layer of spec validity and structural soundness.
Aggregated quality score from linter diagnostics, weighted by severity.
Percentage of `$ref` references that resolve successfully.
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
Structural correctness score based on schema issues using logarithmic dampening.
Clarity, completeness, and ingestion readiness for developers and tooling.
How richly the API is illustrated with examples.
Percentage of examples that conform to their schemas.
Percentage of operations with complete response definitions (success, client error, server error).
Health of API ingestion, bundling, and resolution within Jentic pipelines.
Semantic breadth, depth, and agent comprehension for AI systems.
Coverage of descriptions across API elements.
Coverage of RFC 9457 Problem Details for error responses.
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
Coverage of summaries across operations/tags/info.
Functional utility, complexity comfort, and AI orchestration readiness.
Agent comfort level based on API operational and structural complexity.
Trust, risk posture, and security compliance.
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
Findability, semantic richness, and reasoning readiness.
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>