@firecrawl/prometheus-cli

prometheus CLI

A thin command-line wrapper over a running Prometheus instance's /api/v1 surface. Ask Prometheus for verified, runnable Firecrawl code, manage self-healing scripts and their deployments — scheduled or on-demand API endpoints — or search and share collectors on the marketplace, without touching the web UI.

It has zero dependencies (Node ≥ 18, uses global fetch) and never embeds the agent; it just calls your instance.

Setup

Authenticate once by connecting your Firecrawl account — prometheus login opens the browser for the OAuth consent and saves a Prometheus API token to ~/.prometheus/config.json:

# or install the `prometheus` command first: npm i -g @firecrawl/prometheus-cli
node cli/bin.mjs login

# then ask for code (defaults to the hosted instance)
node cli/bin.mjs build "top 5 Hacker News stories with title, url, points"

prometheus whoami shows the connected team; prometheus logout forgets the token. For CI/headless use, mint a token in the web app's Settings and set PROMETHEUS_TOKEN (overrides the config file). PROMETHEUS_URL defaults to the hosted deployment (https://prometheus.firecrawl.dev); use prometheus login --url http://localhost:3000 for a local instance.

Ask for code

prometheus build "top 5 Hacker News stories with title, url, points"
#   → writes ./script.ts + ./sample.json, prints how it works

prometheus build "latest stable npm version of react" --json | jq -r .script > scraper.ts
#   → agent-friendly: emits the raw JSON contract for piping

build returns a verified Firecrawl-SDK script.ts (run with tsx script.ts, needs FIRECRAWL_API_KEY) plus a sample of the data it produced. When stdout is piped or --json is passed, it prints the JSON response instead of writing files.

Options: --schema f.json (enforce an output shape), --url URL (repeatable starting points), -o DIR (where to write artifacts), --model provider:id.

Manage scripts and deployments

A script is a versioned collector that self-heals when the target site changes — each heal appends a new version. A deployment is one way it runs for you: on a cron schedule, on demand as an API endpoint, or both. One script can have many deployments.

prometheus scripts create "OpenAI blog post titles + urls" --every daily@09:00 --name "OpenAI blog"
prometheus scripts create "..." --session build-abc123   # save a previous build (+ deploy with --every)
prometheus scripts create "competitor pricing" --no-schedule   # on-demand API endpoint only
prometheus scripts ls                                    # scripts with their nested deployments
prometheus scripts show <id> -o script.ts
prometheus scripts data <id> -o latest.json              # latest collected JSON, any deployment
prometheus scripts heal <id>                             # fix a broken script now
prometheus scripts fork <id>                             # stop tracking a marketplace listing
prometheus scripts rm <id>                               # archives its deployments too

prometheus deploy <scriptId> --every 6h                  # another deployment of an existing script
prometheus deploy <scriptId> --no-schedule --pin 3       # on-demand, frozen on version 3
prometheus deployments ls
prometheus deployments show <id>
prometheus deployments run <id> -o fresh.json            # fresh data, synchronously (the API trigger)
prometheus deployments data <id> -o latest.json          # last collected dataset, no fresh run
prometheus deployments pause <id> | resume <id> | rm <id>

Schedules: hourly · 30m · 6h · daily · daily@14:00 · weekly · monday@09:00 · any raw cron ("0 9 * * 1"). Times are UTC. --no-schedule makes a deployment on-demand only.

Self-heal (--heal): off · repair · rebuild · repair_then_rebuild (default). When a run fails, Prometheus re-derives a working collector and appends it as a new version — every track-latest deployment picks it up.

Marketplace

Reuse a collector someone already published — or share yours. search and show are public (no login); everything else needs prometheus login. marketplace is also available as market / mp.

prometheus marketplace search "hacker news"          # find published collectors
prometheus marketplace show <id> -o script.ts        # inspect; write the script locally
prometheus marketplace deploy <id> --track           # script that syncs the listing's updates down
prometheus marketplace deploy <id> --fork            # independent copy with your own self-heal
prometheus marketplace publish <scriptId> --handle me  # share a script (runs the sterility gate)
prometheus marketplace star <id> [--off]
prometheus marketplace unpublish <id>
prometheus marketplace me                            # your publisher profile + listings

Track vs fork: --track syncs the listing's latest approved version down before each run and the platform maintains it (self-heal off); --fork is an independent copy you own and self-heal. Both take --every / --no-schedule for your own terms. First publish needs --handle — your public, permanent publisher handle.

Add --json to any command for machine-readable output.