Get started

Quickstart

The current production path is app-issued token auth plus CLI execution. Sign into the app, generate a short-lived CLI token, and use the CLI for deterministic lead workflows.

Back to docs Open app

Authenticate the CLI

The Salesprompter app currently exposes token-based CLI authentication.

Generate a token from your signed-in app session, then log the CLI in against the main Salesprompter API URL.

salesprompter auth:login --token "$SALESPROMPTER_TOKEN" --api-url "https://salesprompter.ai"
salesprompter auth:whoami --verify

Run a real workflow

For a vendor-led workflow, start from a saved ICP and the Neon-backed lead pool rather than targeting a vendor domain directly.

salesprompter icp:export --program "$PROGRAM_ID" --out ./data/icp.json
salesprompter leads:qualified --icp ./data/icp.json --limit 100 --out ./data/leads.json
salesprompter leads:enrich --in ./data/leads.json --out ./data/leads-enriched.json
salesprompter leads:score --icp ./data/icp.json --in ./data/leads-enriched.json --out ./data/leads-scored.json
salesprompter sync:outreach --target instantly --in ./data/leads-scored.json --campaign-id "$INSTANTLY_CAMPAIGN_ID"

Use parser-friendly output

Humans and LLMs should share the same CLI surface. Agents should prefer compact JSON output and dry-run-first behavior.

`--json` emits compact machine-readable output
`--quiet` suppresses successful stdout payloads
Add `--apply` only when a dry run looks correct