AnswerLens

Audit product pages, review the report, and fix what AI assistants cannot read clearly.

Language: English / 简体中文

First-run FAQ

AnswerLens FAQ for new visitors and evaluators.

Use these answers before you run quickstart, add GitHub Actions, or compare AnswerLens with hosted dashboard tools.

What people ask first

Common questions

What does AnswerLens audit?

AnswerLens audits whether a product site is easy for AI systems to read, cite, compare, and recommend. It writes a share summary, scorecard, and recommendations your team can review.

Does AnswerLens scrape consumer AI apps?

No. AnswerLens keeps the non-goal explicit: no consumer AI UI scraping and no ranking guarantees on answer surfaces.

Do I need provider API keys to try it?

Not for a basic audit run. Provider keys are only needed when you want eval-mode benchmarking on top of the core site audit.

How do I start in under five minutes?

Start with the live demo report, run the sample-site demo locally, then use the 5-minute real-site quickstart before adding the GitHub Action.

How does pricing work today?

The project is open source, the CLI and Pages docs are public, and optional eval costs stay in your own provider account.

What to open next

Related proof pages

  • Pricing: see the open-source package and provider-cost model.
  • Security: review trust, secrets, and guardrails.
  • Compare: understand how AnswerLens differs from Profound, Peec AI, and Otterly.
  • Integrations: review the GitHub Actions setup path.
  • Docs: go deeper on activation, scoring, and Action usage.