Jovie, for your agents.

Q: Does the CLI require an account or API key?

No. Every command is anonymous. The only writes are profile create, which makes an unclaimed profile the creator claims by verifying their Spotify artist, and the report commands, which file bugs and feedback. The CLI does not log in, cache responses, or send telemetry.

Q: Which Node.js version does it need?

Node.js 24.21.0 or later, including Node 26. That matches the published package engines field.

Q: Can I point it at another Jovie deployment?

Yes. Pass --base-url with an http or https origin and no path, credentials, or query parameters.

Q: What happens when a command fails?

Successful commands exit 0. Request or response failures exit 1. Invalid command-line usage exits 2.

Give any creator a Jovie profile from their Spotify link, then read public profile data. One package: CLI, MCP server, and agent skill. No account or API key.

Install the CLI Public API

Install

Install globally, or run it with npx from any agent. The CLI is anonymous.

npm install --global @jovie/cli
jovie --help
jovie --version

No accountNo API keyMCP serverJSON output

What You Can Do

Give a creator a profile

jovie profile create <spotify-artist-url>

Create a Jovie profile from a Spotify artist link. You get the profile URL and a claim link the creator opens to take ownership.

Plug Jovie into an agent

npx -y @jovie/cli mcp

Run the same commands as MCP tools, or run jovie init to install the Jovie skill into every agent on this machine.

Get a profile

jovie artist get <username>

Fetch the structured public profile for a real Jovie username. Add --json when you want to pipe the response into another tool.

Give a profile to an agent

jovie artist llms <username>

Fetch the profile’s public llms.txt context so an agent can understand the creator without scraping a profile page.

Build against Jovie

jovie api openapi

Read the canonical public OpenAPI contract directly from the terminal.

Give Jovie to an agent

jovie docs llms

Fetch Jovie’s machine-readable documentation. Use --full when the complete documentation context is useful.

CLI Reference

Every command accepts --base-url and --json. --json emits JSON for API responses and wraps text resources as {"content":"..."}.

jovie profile create <spotify-artist-url>: POST /api/agents/profiles
jovie artist get <username>: GET /api/v1/{username}
jovie artist llms <username>: GET /{username}/llms.txt
jovie api openapi: GET /api/v1/openapi.json
jovie docs llms: GET /llms.txt
jovie docs llms --full: GET /llms-full.txt
jovie mcp: The commands above as MCP tools over stdio
jovie init: Installs the Jovie skill into Claude, Codex, OpenClaw, and Hermes
jovie skill: Prints the Jovie SKILL.md for agents

Maintainer note: package publication is main-only and provenance-required. A local checkout can run the same command surface with pnpm --filter @jovie/cli dev.

Questions

Does the CLI require an account or API key?

Which Node.js version does it need?

Can I point it at another Jovie deployment?

What happens when a command fails?

Jovie, for your agents.

Install the Jovie CLI and give a creator a profile from their Spotify link.

Install the CLI

Get product updates

New features and improvements from Jovie.