API

jellyfindex exposes the whole directory as static, read-only JSON. No auth and no rate limit. It's just plain files, regenerated on every deploy.

Endpoints

A machine-readable index of these is also available at /api/v1.json.

Response shape

List endpoints wrap entries in an envelope with generatedAt and count. Each entry carries every field from its meta.yaml, plus:

• id — the entry's slug.
• url — its page on jellyfindex.
• description — the long-form write-up, as plain markdown.
• logo / banner / previewImages[].image — absolute URLs to the optimized images.
• repoStats — cached GitHub stars, last commit date, and archived status for the entry's source repo (refreshed daily), or null if it has no GitHub link.

Example

curl https://jellyfindex.com/api/v1/clients/jellysee.json

Fair use

This exists so you can build tools, bots, and integrations on top of the directory, not so you can stand up a copy of jellyfindex itself. Please don't use this data to launch a competing site with the same concept and dataset, reskinned or otherwise. Prefer building on the community instead of around it. If you want to help grow the list, contribute an entry.

The code itself is open source under the GNU GPL v3. You're free to reuse, modify, and redistribute it, including for another project, as long as your project stays GPL-licensed too and credits the source, per the license terms. The curated dataset is a separate matter: it's maintained with real effort and protected as a database compilation under EU law, so please don't extract it wholesale to power a from-scratch competing directory. If you're planning something and aren't sure it's fine, just ask: contact@jellyfindex.com.