v0.0.67

Simpler pricing and faster repeat audits.

Changed

• New flat pricing: 50 credits per audit plus 2 credits per rendered page. Everything else that runs inside an audit is now included: AI content analysis, authority signals, technology detection, the editor summary, site metadata, domain stats, ad-block detection, dead-link checking, and report publishing. Keyword and content gap analyses stay optional add-ons at 25 credits each. A 50-page rendered audit costs exactly 150 credits, and the estimate you confirm up front is the price you pay.
• Publishing is always free. Publishing a report at any visibility, including flipping an existing report to public later, never costs credits.
• Failed audits are refunded automatically. If an audit fails or is cancelled before delivering a report, its charges are returned, including the base.
• Audits need a balance of at least 50 credits to start. Below that, the CLI runs the audit locally, tells you why, and skips cloud features instead of charging you partway.

Fixed

• The end-of-audit credits line now matches your ledger. It is built from the amounts the server actually charged, including the audit base, instead of client-side estimates that could overstate spend.
• Crawler user agents are modern browsers again. The random user-agent pool no longer includes decade-old browser versions that bot protection loves to challenge, so crawls of protected sites are far less likely to stall or get served challenge pages.
• Lower memory use on large audits. The audit engine now releases parsed pages it is not actively using, cutting the working set on 100+ page runs and avoiding severe slowdowns on memory-pressured machines.

New

• Per-phase timing breakdown. Run with --debug to see exactly where audit time goes (crawl, cloud analysis, rules, report). The same breakdown is stored with the run, which makes slow-audit reports much easier to diagnose.
• Repeat audits are much faster. Unchanged pages reuse cached rendering and AI analysis server-side. In our testing, re-auditing an unchanged 100-page site dropped from about 40 minutes to about 4.