check seo|aeo|geo|agents <domain> [--json] [--rescan] | Free check of one pillar, no sign-in: score, label, what to fix first and the suggestions count. --json prints the public API JSON. Exit 3 when rate-limited |
check risk <domain> [--json] | The penalty risk checker: practices Google, Bing and AI engines punish, each with its evidence, affected pages, a fix and the policy. Private to you, never cached; one free use per 30 days, or 30 an hour for your own projects when signed in. Exit 3 when the free use is spent |
check all [--project ID] [--wait S] [--json] | All four pillars of your project (signed in): the scores, pass/partial/fail counts and what to fix first, from the latest scan. With no completed scan yet it requests one and waits up to --wait seconds (180). Exit 3 while the scan still runs, 1 if it failed |
init [--token T] [--server URL] [--url U] [--brand B] [--category C] [--use-case U] [--app-root P] [--mcp claude|codex|cursor|none] [--yes] [--fix-deploy] [--no-pr] [--wait S] [--level 0|1|2|3 [--confirm-full-autopilot]] [--json] | Full setup, idempotent. Runs the deploy doctor after creating the project; --fix-deploy --yes lets it run vercel git connect (otherwise it only reports what it would run). --level turns Autopilot on for the repository (asked after the scan in a terminal); fixes are made by the Paradigma agent, hosted or in your GitHub Actions |
doctor deploy [--json] [--fix [--yes]] [--app-root P] | How the site is published and whether a merged PR goes live (exit 3 when it does not). See Deploys |
status [--json] | Account checklist and this machine's sign-in |
links [--json] | Hand-off links: GitHub App, Search Console, GA4, Slack, billing |
projects list|create|update [--project ID] [--url …] [--brand …] [--category …] [--use-case …] | Manage projects |
verify [--method dns|file|meta]... [--project ID] | Check domain ownership (exit 3 while unverified) |
tasks [--project ID | --repo owner/name] [--all] [--json] | The project's tasks with counts: status, title, PR link. Defaults to the project of the current checkout, else every project; --all adds finished ones. --json prints the API response ({projects: [{project, counts, tasks}]}) |
tasks start <task id> [--checkout] [--json] | Takes a task for your current agent and prints its brief: branch to create, allowed paths, diff budget, acceptance criteria, instructions and the finish commands. --checkout creates the branch from the default branch when the current directory is a clean clone of the task's repository |
tasks finish <task id> --pr URL | --done | --skip --reason R | --failed --reason R / tasks release <task id> | Closes a started task (the PR must be a github.com pull request URL; the reason is one line of at most 200 characters), or gives it back to the queue |
tasks prompt [--project ID] [--copy] | The prompt that hands a project's open tasks to an agent; --copy puts it on the clipboard (pbcopy, wl-copy, xclip or xsel) |
audit [--project ID] | Request a production audit |
sync gsc|bing|ga4|performance|plausible|posthog | Request a data sync |
indexnow [status|setup|on|off] [--project ID] | IndexNow: opens the key-file PR, then each production deploy tells Bing, Yandex, Naver, Seznam and Yep (not Google) which pages changed; status shows recent deploys (exit 3 until the key file is live) |
index [--project ID] / index requested <url>... / index check | Google index coverage (URL Inspection on your own Search Console connection) and today's up to 10 pages to request, each with its Search Console link where you click "Request indexing"; mark them as requested; run today's inspection batch now |
connect bing [--project ID] | Connect Bing Webmaster Tools with the Microsoft consent in the browser (no key to copy); the CLI waits for it. --key-env NAME or a piped key uses an API key instead |
connect ai [--project ID | --all] [--yes] [--own] | AI visibility. On Pro and Agency it is included: Paradigma samples Gemini, OpenAI, Claude, Perplexity, Google AI Overviews and AI Mode on its own accounts, so there is nothing to connect. With --own (or on other plans) it connects AI keys already in the environment (names shown, never values), then one OpenRouter consent covers the missing engines; your own keys then take over and bill your accounts |
connect <provider> [--key-env NAME] | Store a key: bing, crux, plausible, posthog --region us|eu --posthog-project ID, gemini, openai, anthropic, perplexity, dataforseo --login L [--location 2840] [--language en] |
geo prompts [list|add "TEXT"] | GEO questions |
geo schedule --engine E --daily 1|3|5|10 --accept-charges / --off | Automatic sampling on your provider key |
geo sample --engine E --prompt ID --accept-charges | One manual sample on your provider key |
alerts budget 0|1|2|3 [--org ID] | Weekly alert budget (organization owner) |
billing checkout --plan pro|agency / billing portal [--open] | Prints the hosted Stripe URL |
autopilot level 0|1|2|3 / autopilot pause [--reason R] / autopilot resume | Server-side Autopilot policy for the repository; level 0 needs --confirm-full-autopilot |
autopilot default 0|1|2|3|off [--org ID] | Workspace default level for every repository that follows it, new ones included; needs write access to every repository, level 0 needs --confirm-full-autopilot |
autopilot follow-default [--repo owner/name] | The repository follows the workspace default again (autopilot level makes it keep its own) |
mcp install --agent claude|codex|cursor | Connects the Paradigma MCP server to your agent |
fix --task <token> [--api-url URL] [--build CMD] [--test CMD] | Runs one fix that Paradigma dispatched to your GitHub Actions workflow; the Paradigma GitHub Action calls it. See GitHub Action |
doctor | Setup checks: Node, git, sign-in, the server and its pinned key |
logout | Removes the CLI credential from this machine |