Molly CLI

What is the Molly CLI?

The Molly CLI is a lightweight wrapper around Molly's REST API. Every command maps 1:1 to an HTTP call against the base URL:

https://app.iamolly.ai/api/molly/v1

Requests are authenticated with a Bearer API key (format mk-...). There's no daemon, no background process, no telemetry — just your terminal talking to your Molly.

Install

One line. The install script detects your OS and architecture, downloads the right binary, and places it on your PATH (typically /usr/local/bin/molly).

curl -fsSL https://iamolly.ai/cli/install.sh | sh

Verify the install:

$ molly --version
molly 1.x.x (stable)

Authenticate

Grab an API key from your dashboard at app.iamolly.ai, then run:

$ molly auth
Paste your API key (mk-...): mk-********************************
✓ Key verified. Saved to ~/.molly/config.json

The key is stored locally in ~/.molly/config.json with 0600 permissions and sent as a Bearer header on every request:

Authorization: Bearer mk-your-key-here

You can also override the stored key per-invocation with the MOLLY_API_KEY environment variable — handy for CI:

MOLLY_API_KEY=mk-... molly chat "hello"

Commands

Every subcommand maps directly to a REST endpoint:

molly chat

Send a message to the default model, molly. Under the hood this is a POST /chat/completions request.

$ molly chat "Summarize this repo's README in 3 bullets"
# equivalent to:
# POST https://app.iamolly.ai/api/molly/v1/chat/completions
# { "model": "molly", "messages": [{ "role": "user", "content": "..." }] }

Streaming

Add --stream to render tokens live as they arrive:

molly chat --stream "Write a haiku about uptime"

Piping

Read the prompt from stdin for scripted workflows:

git diff | molly chat "Review this diff for bugs"

molly models

Lists model IDs available to your key via GET /models.

$ molly models
ID       OWNED BY
molly    molly

molly usage

Shows your token consumption and remaining quota via GET /usage.

$ molly usage
Period       current billing cycle
Requests     1,284
Tokens in    412,006
Tokens out   198,441
Quota        62% remaining

Add --json to get raw JSON for dashboards and alerts:

molly usage --json | jq '.tokens_out'

molly whoami & molly keys

molly whoami confirms which account and key the CLI is currently using — useful when juggling multiple environments.

$ molly whoami
Account   you@yourcompany.com
Key       mk-****...9f2a  (active)
Base URL  https://app.iamolly.ai/api/molly/v1

molly keys manages locally stored keys:

$ molly keys list          # show saved keys (masked)
$ molly keys add           # save an additional key
$ molly keys use <name>    # switch active key
$ molly keys remove <name> # delete a key locally

Configuration

All state lives in a single file: ~/.molly/config.json.

{
  "api_key": "mk-...",
  "base_url": "https://app.iamolly.ai/api/molly/v1",
  "default_model": "molly"
}

Environment variables always win over the config file:

• MOLLY_API_KEY — override the stored key.
• MOLLY_BASE_URL — point at a different deployment.

Uninstall

Removing the CLI is as simple as installing it. Delete the binary and, optionally, your local config:

# remove the binary
sudo rm /usr/local/bin/molly

# remove local config & saved keys (optional)
rm -rf ~/.molly