Costs and billing

Two different bills

The licence is what you pay us, once a year. It covers the software, updates and support, and it’s the same feature set on every tier — only the number of sites changes.

Usage is what you pay Anthropic and, if you connect one, a data provider. It goes directly to them at their published rate. We never see it, never mark it up, and never meter it, because the requests don’t pass through our infrastructure.

The Costs screen

Open Costs from the sidebar and you’ll see:

• Spend this month, broken down per provider
• Projected monthly, extrapolated from your current rate
• A request log — what was called, for which page, and what it cost

The figures come from the actual token counts returned with each response, not from an estimate applied afterwards.

Estimates before you spend

Every AI fix shows an estimated cost before you preview it, and a bulk operation shows the total for the batch. You approve the spend at the same moment you approve the change.

Scanning is always free of AI cost. A scan reads your site and runs the checks; the AI is only called when you ask for a specific fix to be written.

What it really costs

Roughly a cent per fix as a working figure. A concrete example: 120 pages, three fixes each, rescanned quarterly, works out at around five to six dollars for the year on top of the licence.

Content length and model choice move that number, which is why the plugin shows you the estimate rather than a marketing average.

Keeping it down

• Fix in batches. Bulk operations reuse context and cost less per page than one-at-a-time.
• Start with errors. Fixing the highest-severity issues first gets most of the benefit for a fraction of the calls.
• Use deterministic fixes freely. Around half the fixable checks need no AI at all and cost nothing.
• Set a spend limit at Anthropic. Their console lets you cap monthly usage, which is a harder guarantee than any setting we could offer.

Next: Reading your Analytics →