CLI / local and JSON-first

CHECK WHAT AI RECOMMENDS.

Audit a site's AI readiness without a key, or use your own provider keys to measure whether AI engines recommend a brand and its products. Results and captured evidence stay local.

See commands →Read as Markdown

START WITH AN AUDIT.

The audit makes no AI calls. Run the published package directly:

npx optifeed-radar audit yourbrand.com

To develop Radar from source instead:

git clone https://github.com/optifeed/optifeed-radar.git
cd optifeed-radar
npm install
npx tsx src/cli/index.ts audit yourbrand.com

COMMANDS.

Command	Purpose	Calls AI?
`audit <domain>`	Check robots.txt, llms.txt, structured data, metadata, and sitemap.	No
`check <domain>`	Generate buyer questions, ask configured engines, and estimate AI visibility.	Yes
`shopping <domain>`	Compare your supplied product order with the engines' recommended order.	Yes
`queries <domain>`	Show or export the buyer-question pack.	Depends
`diff <domain>`	Compare the two latest saved visibility runs.	No
`sources <domain>`	Show domains cited in a saved run and the brand's source share.	No
`config`	Show which provider keys are present without printing their values.	No

CONTROL THE RUN.

01 / QUICK

Start smaller

npx optifeed-radar check yourbrand.com \
  --quick --max-cost 0.20 --yes

Quick mode uses a smaller prompt pack. The cap is checked before each provider call and any measured overshoot is reported.

02 / JSON

Give results to an agent

npx optifeed-radar check yourbrand.com \
  --quick --json --yes

Use JSON output for scripts and agents. Use --report report.html when a self-contained human report is more useful.

03 / PRODUCTS

Compare your shelf with AI's shelf

npx optifeed-radar shopping yourbrand.com \
  --products "Product A, Product B, Product C" --yes

List products best first. Radar treats that as your ranking and reports the delta against the order AI engines recommend. It does not import or discover your catalog.

YOUR KEYS.

Set at least one of OPENAI_API_KEY, ANTHROPIC_API_KEY, GOOGLE_API_KEY, or PERPLEXITY_API_KEY in the environment or a local .env file. Radar sends requests directly to the configured providers and stores snapshots locally.