Visiblee CLI

Track how your brand appears in AI assistant answers — ChatGPT, Gemini, Perplexity, Google AI Overviews — straight from your terminal, or let an AI agent (Claude Code, Cursor, Codex) drive it for you.

npm install -g @visiblee/cli
visiblee login
visiblee visibility

Login (no API keys to fiddle with)

visiblee login

Opens your browser, you approve access on visiblee.ai, and you're done — the CLI stores a credential in ~/.visiblee/config.json (mode 0600). Under the hood this is an OAuth 2.1 PKCE flow; the token is a revocable key you can remove any time in Settings → API or with visiblee logout.

Non-interactive / CI / agents — skip the browser with an existing key:

visiblee login --api-key vk_live_xxx
# or, per-invocation:
export VISIBLEE_API_KEY=vk_live_xxx

Check status any time:

visiblee whoami

Commands

| Command | What you get | |---|---| | visiblee projects | List your projects | | visiblee project <name> | Project detail: brand terms, competitors, engines, regions | | visiblee visibility [name] | Headline report — score, trend, per-engine, share of voice, best/worst prompts | | visiblee competitors [name] | Competitor leaderboard (who AI mentions most) | | visiblee mentions [name] | Recent brand/competitor mentions pulled from AI answers | | visiblee prompts [name] | Tracked prompts (search queries) | | visiblee prompt-add <text> [name] | Add a tracked prompt (--category --intent --importance) | | visiblee prompt-edit <promptId> [name] | Edit a prompt; --pause/--resume to toggle tracking | | visiblee prompt-rm <promptId> [name] | Delete a tracked prompt | | visiblee sources [name] | Top web domains AI cites for your prompts | | visiblee suggestions [name] | Recommended GEO actions to improve visibility | | visiblee engines / regions | Reference IDs for --engine / --region filters | | visiblee track-engines <ids> [name] | Set the engines a project tracks (comma-separated, replaces set) | | visiblee track-regions <ids> [name] | Set the regions a project tracks (comma-separated, replaces set) |

Project is referenced by name, domain, or ID — partial names work (visiblee visibility acme). If you have one project, you can omit it entirely.

Common flags: --engine <ids>, --region <ids> (comma-separated, see visiblee engines/regions), -n/--limit, and --json on everything.

For AI agents

Two ways to let an agent use Visiblee:

1. MCP (recommended for Claude / Cursor / ChatGPT)

visiblee mcp install            # prints copy-paste setup for your client

The agent gets the full Visiblee toolset natively — reading visibility data and managing what a project tracks (add/edit/delete prompts, set tracked engines and regions). Claude.ai supports a browser-OAuth connector (no API key to paste) at https://api.visiblee.ai/mcp/connect.

2. The CLI with --json

Every command supports --json, emitting structured data agents can parse:

visiblee visibility "My Brand" --json
visiblee competitors "My Brand" --json

The Claude Skill

For clean, consistent answers (and correct interpretation of the numbers), install the Visiblee Skill so Claude knows the discovery flow, what each metric means, and how to present results. Copy skill/visiblee/ into ~/.claude/skills/ (user-wide) or your project's .claude/skills/.

Environment variables

| Var | Purpose | |---|---| | VISIBLEE_API_KEY | Use this key instead of a stored login (CI/agents) | | VISIBLEE_API_BASE | Override API base URL (default https://api.visiblee.ai) | | VISIBLEE_CONFIG_DIR | Override config location (default ~/.visiblee) | | NO_COLOR | Disable colored output (also --no-color) | | VISIBLEE_DEBUG | Print extra error detail |

Development

npm install
npm run build      # tsc → dist/
npm run dev -- visibility --json
npm test           # unit + end-to-end (mock API) tests