prelive

Official command-line interface for the Prelive public API.

Install

npm install -g prelive-cli

Or run on demand:

npx prelive-cli --help

Quickstart

# Save your API key locally (~/.config/prelive/config.json)
prelive auth login --api-key prl_live_…

# Verify
prelive me

# Generate stream titles + descriptions + hashtags
prelive content stream-info "Elden Ring" --description "no-hit attempt #4"

# Transcribe an audio/video URL
prelive transcribe --url https://example.com/clip.mp3 --language en

# Schedule a social post
prelive posts schedule \
  --content "Going live soon!" \
  --platforms twitter,tiktok \
  --at 2026-04-28T18:00:00Z

# List scheduled posts
prelive posts list --status PENDING

Auth resolution order

1. --api-key flag
2. PRELIVE_API_KEY env var
3. ~/.config/prelive/config.json (or %APPDATA%/prelive/config.json on Windows)

Get an API key at prelive.ai/settings/api-keys.

OBS setup

Two ways to configure OBS end-to-end (docks + ingest, no copy-pasting):

• CLI (prelive obs setup) — for users who already have the CLI + an API key.
• No-CLI installer — the prelive-obs-setup entry (src/obs-setup-app.ts). It uses loopback OAuth + PKCE: opens the browser to /authorize/obs, the user clicks Authorize, and it configures OBS. No npm, no CLI, no API key.

Package the installer into a single double-click binary (ops step; requires code-signing to avoid SmartScreen/Gatekeeper warnings):

npm run build            # emits dist/obs-setup-app.js
npx @yao-pkg/pkg dist/obs-setup-app.js \
  --targets node18-win-x64,node18-macos-arm64,node18-linux-x64 \
  --output prelive-obs-setup
# then sign: signtool (Windows) / codesign + notarytool (macOS)

License

Apache-2.0