Developer workflows

Video encoding CLI for scripts, CI jobs, and local automation

Automate video compression from terminals, deployment jobs, content pipelines, and scheduled scripts with a Convertrilo CLI workflow.

The CLI exposes the same API primitives developers already need, then makes login, encode, wait, status, cancel, balance, doctor, and download workflows easy to compose in shells and CI.

Install, login, encodeautomation
npm install -g @convertrilo/sdk
convertrilo login --open

convertrilo encode https://example.com/input.mp4 \
  --codec h264 \
  --resolution 1080p \
  --quality better \
  --wait

Run encoding from CI, cron, and internal tooling.

Wait for completion with terminal progress without writing polling loops every time.

Download CDN outputs or send results to configured storage.

Share repeatable commands between engineering and operations teams.

Workflow

Built for jobs that should run without a human babysitting a tab

Each automation page maps to the same production path: API request, durable job row, queue, Rust worker, storage upload, terminal event, and reconciliation.

  1. Step 1

    Install @convertrilo/sdk from npm to get the convertrilo and convertrilo-mcp binaries.

  2. Step 2

    Run convertrilo login or convertrilo init to save an API key from Developer Settings.

  3. Step 3

    Run an encode command with explicit codec, resolution, and destination settings.

  4. Step 4

    Use human output for operators, or --json, --field, --job-id-only, and --download-url-only for scripts.

CI-friendly output

JSON and field-only output keep scripts clean, while normal terminal mode shows readable status, progress, and download URLs.

Local credential storage

The login command stores credentials at ~/.convertrilo/config.json, and environment variables can still override config in CI.

Same package as MCP

The npm package also installs convertrilo-mcp, so teams can use one package for scripts, agents, and MCP clients.

Automation questions

Is the Convertrilo CLI available today?

Yes. Install @convertrilo/sdk from npm to get the convertrilo CLI and convertrilo-mcp server.

Where do users get an API key?

Run convertrilo login --open. The CLI opens Developer Settings, then saves the key locally for future CLI and MCP use.

Why use a CLI if there is an SDK?

A CLI is useful for shell scripts, CI jobs, content operations, and one-off automation where writing a custom Node service is unnecessary.

Will CLI jobs support the same encoding settings?

Yes. CLI commands support the same core codec, resolution, quality, priority, VMAF, two-pass, and S3 output options exposed by the API.

Related automation pages

Start with a real estimate

Choose your codec, resolution, FPS, bitrate, quality, and optimization settings. Convertrilo shows the NEU estimate before credits are reserved, and failed jobs release reserved credits back to your balance.