Public profile data, in the open.

Quickstart

Fetch one public creator's structured profile with a normal HTTP GET request. Replace {username} with the creator's public Jovie handle.

curl https://jov.ie/api/v1/{username}

The response includes the profile identity plus public releases, upcoming events, merch, and related resource links. Unknown or non-public profiles return a JSON 404 response.

Agent quickstart

Start from the same profile endpoint as the quickstart above, then follow the resource links in the response. Every surface below is anonymous and read-only; owner-only tools require authenticated profile ownership and are never part of this quickstart.

For agent context, read /llms.txt or a specific profile's {username}/llms.txt, and run the same jobs from a terminal with the /cli.

Machine-readable resources

• Public API Capability Index

  A stable, non-enumerating 200 response describing the anonymous read-only API.

• OpenAPI 3.1 contract

  The machine-readable contract for the public profile API.

• Jovie CLI and MCP server

  Anonymous `jovie` commands for agents: read public profile data and create claimable profiles.

• API Versioning And Deprecation Policy

  Active v1 lifecycle boundary, additive versus breaking changes, and future Deprecation and Sunset signals.

• Integrations

  Account integrations and the capabilities each supports.

• llms.txt

  A concise guide to Jovie’s public site and agent surfaces.

• llms-full.txt

  The expanded version of the site guide.

• Jovie Docs

  Product help and getting-started guidance.

Public by design

This page documents Jovie's public profile surface: anonymous GET access to data a creator has made public. It does not add a write API, credentials, or a separate developer account. Keep private or sensitive information out of requests and use the OpenAPI contract as the source of truth.

Profile requests are limited to 100 per client IP in a fixed 60-second window. Read the API reference for the current RateLimit and Retry-After response contract.

Version v1 is active. A policy Link relation points to lifecycle guidance; active v1 responses do not claim Deprecation or Sunset.

For a human-oriented overview, visit Support.