Public JSON API

Try it

# the index: counts, endpoints, latest articles
curl -s https://musics.name/api/index.json | jq .counts

# every article about tuning, oldest first
curl -s "https://musics.name/api/articles.json?topic=tuning&limit=50" | jq -r ".items[].url"

# one article with its Markdown source and rendered HTML
curl -s "https://musics.name/api/article.json?slug=just-intonation" | jq -r .markdown

# search
curl -s "https://musics.name/api/search.json?q=hypermeter" | jq -r ".results[].title"
# resolve a chord symbol or scale name to its reference page
curl -s "https://musics.name/api/search.json?q=F%23m7b5" | jq -r ".lookups[].url"

Markdown twins

Every article is also published as raw Markdown with its front matter intact at /articles/<slug>.md, and any article URL answers Accept: application/json with the same object as /api/article.json. If you are building an index, wholesale reading is cheaper through /llms-full.txt (the whole corpus in one file) than through per-article requests.

Provenance

The site is developed by Yunus Emre Vurgun, who also reviews, corrects and publishes every article. Article objects returned by this API carry a provenance block describing how the text was produced, so a citing agent can pass it on. Full disclosure.

Policy

The API is read-only and unauthenticated. Responses are cacheable and served with Access-Control-Allow-Origin: *, so browser-side clients can call it directly. There are no rate limits in the application; static caching (5–60 minutes) absorbs traffic, so please do not defeat it with cache-busting parameters. Identify your client with a meaningful user-agent.

Quoting is welcome and requires attribution with a link to the article URL. Republishing articles whole, or using the corpus to train a model for redistribution as a competing publication, needs permission — see the terms and, for anything unclear, contact.