Fetch annotations attached to a Genius song or web page using the referents endpoint
domain: docs.genius.com · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Obtain a Genius API client access token by registering an API client on the Genius developer site
Identify the target content by its `song_id` (from a prior song search/lookup) or, for annotated web pages, its `web_page_id` — the referents endpoint accepts only one of the two, not both
Call the referents endpoint with the chosen `song_id` or `web_page_id`, using `per_page` and `page` to paginate results for heavily-annotated songs
Set `text_format` (e.g. dom, html, markdown, or plain) to control how returned annotation body text is formatted for your rendering layer
For each referent, read its associated annotations to get the actual annotation body/content, and its fragment (the highlighted source text) to know what the annotation is attached to
Optionally filter by `created_by_id` if you need annotations authored by a specific Genius user rather than all annotations on the content
Known gotchas
A referent can have more than one annotation attached to the same fragment (e.g. both an official artist annotation and a community one) — code that assumes one annotation per fragment will drop data
song_id and web_page_id are mutually exclusive on this endpoint; passing both is invalid, not additive
Annotation body content can include rich formatting/embedded markup — request the `text_format` your renderer actually supports rather than parsing raw DOM output as plain text
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?