How do AI credits work, and which actions consume credits?

AI credits are consumed when a workflow runs an AI-assisted operation. The exact credit use depends on the module, action, file count, article count, field count, or processing scope. The product shows available credit information so users can monitor usage before and during a trial or organisation plan.

Examples of credit-consuming actions include AI search generation, AI screening or full-text processing, risk-of-bias processing, AccuSynthesis extraction, AQUA processing, AccuScripter structure generation, and AccuScripter writing generation.

AccuSearch credit use is typically tied to search or AI search-generation actions. AccuScreener credit use can be tied to article-level AI screening or file-level full-text processing.

RoB Master and AQUA credit use is typically file-based. AccuSynthesis credit use can depend on files, extraction fields, or the configured extraction scope. AccuScripter credit use can depend on file count and generated structure or writing operations.

Manual review, ordinary navigation, editing already generated text, and downloading existing exports generally do not consume credits unless they trigger a new AI run.