CLI

The javinfo CLI is a native binary for Linux and macOS that puts the javinfo API in your terminal. It covers three jobs: quick lookups, playing titles over your local network, and building a Kodi/Jellyfin library from the files you already have.

Install

One line, no Rust toolchain needed:

curl -fsSL https://javinfo.dev/install.sh | bash

The script detects your OS and CPU, downloads the matching prebuilt binary, verifies its checksum, and installs to ~/.local/bin. Make sure that directory is on your PATH.

Prefer something else?

• Prebuilt binaries: grab an archive from the Releases page. Linux x86_64, Linux arm64, and macOS Apple Silicon are shipped; macOS Intel and Windows need a source build.
• From source: cargo install --path . (Rust 1.85+), or cargo build --release and use target/release/javinfo directly.

Set up your key

Get a key (starts with jvi_) from the dashboard, then:

javinfo login                    # prompts for the key
# or non-interactively:
javinfo login --api-key jvi_your_key_here
# or skip login entirely with an env var:
export JAVINFO_API_KEY=jvi_your_key_here

login also scans your PATH for video players (vlc, mpv, ffplay, iina, …) so the open command knows how to launch one later. The key is stored in ~/.config/javinfo/config.toml with mode 0600.

Look up a title

movie resolves a DVD code through the API's provider waterfall and prints a human summary:

javinfo movie EBOD-391
javinfo movie SSIS-001 --json          # full JSON response
javinfo movie CAWD-001 --providers fanza,missav   # pin providers

Play over your LAN

open starts a local re-streaming daemon (if needed) and prints a play URL that any device on your network can open:

javinfo open EBOD-391
javinfo open EBOD-391 --with vlc       # launch the player too
javinfo open EBOD-391 --with mpv

The URL points at http://<your-lan-ip>:8787/s/<token>/EBOD-391.m3u8. The daemon fetches the stream from the provider, injects the right headers, caps the quality (--max-height 1080 by default), and re-serves it locally. Each session uses an opaque token, so codes alone can't access the daemon. Daemon lifecycle:

javinfo serve start                    # run in the background
javinfo serve status
javinfo serve stop

Organize your library

nfo scans a folder (or a single file), matches each DVD code to the API, and writes Kodi and Jellyfin sidecars (.nfo metadata, poster, fanart, thumb, and trailer) next to your videos:

javinfo nfo ~/Videos/JAV --dry-run     # preview the plan, change nothing
javinfo nfo ~/Videos/JAV --write       # also create a folder and rename: SSIS-001/SSIS-001.mp4
javinfo nfo ~/Videos/SSIS-001.mkv      # single file

Nothing is renamed or moved unless you pass --write, and existing .nfo files are left alone (--force refreshes them). Metadata comes from fanza,dmm by default; --write torrent switches to javdb and also drops torrent and magnet files.

Check your setup

status shows what the CLI knows about your local setup: key source (masked), configured players, and whether the serve daemon is running:

javinfo status
javinfo status --json

Make it yours

The CLI is open source (MIT). Did we miss a feature you want? Customize it. Pull requests are welcome, or fork it and make it your own. Steal the source code: github.com/javinfo/cli.

Next

• Read the API docs for everything the CLI wraps.
• See providers to understand where metadata and streams come from.
• Check rate limits & billing: the CLI bills per successful lookup, same as the REST API.