LLM Pulse CLI: query AI visibility data from the terminal

The LLM Pulse CLI is a native Rust application for querying your AI visibility data from a terminal. Use it for scripts, recurring exports, CI jobs, and quick checks without opening the dashboard. It is available on Scale plans and above.

With the LLM Pulse CLI, you can:

• Pull your visibility, citation, and competitor data from the command line
• Script recurring reports and pipe results into your own tools
• Wire AI visibility checks into CI pipelines and automations
• Work with your data without opening the dashboard

What it does

• Access every LLM Pulse REST operation from your terminal
• Script automated reports and data exports on a schedule
• Query metrics, dimensions, Search Console, AI traffic, recommendations, GEO Writer tasks, and webhooks
• Create and manage prompts, competitors, collections, projects, and annotations
• Output data as JSON, a terminal table, or CSV

How to use it

1. Download the archive for macOS, Linux, or Windows from GitHub Releases
2. Extract the llmpulse binary and place it somewhere on your PATH
3. Run llmpulse login and enter an API key from User Menu > API Keys
4. Check your project with llmpulse status
5. Get visibility metrics with llmpulse metrics summary --project-id ID --range 30
6. Run llmpulse --help to see every command

Developers with Rust installed can also build it from source:

cargo install --git https://github.com/LLM-Pulse/llmpulse-cli --locked

Common use cases

• Automated monitoring: run a cron job that checks visibility metrics daily and alerts on drops
• Data exports: schedule weekly CSV exports of prompt performance for reporting
• CI/CD integration: check whether AI visibility metrics meet a threshold before deploying content changes
• Quick lookups: check a specific metric without switching to the browser

Tips & notes

• Requires an API key and a Scale or Enterprise plan
• Uses the REST API and its 300 requests-per-minute rate limit
• llmpulse login stores the key in ~/.llmpulse/config.json with owner-only file permissions
• API keys can also come from LLMPULSE_API_KEY, which is useful in CI
• The CLI rejects unencrypted remote API URLs; plain HTTP is allowed only for localhost development
• Combine JSON output with tools such as jq, or use --format csv for exports
• The same API key works for the CLI, REST API, official SDKs, headless MCP, and the Data Studio connector