Algolia Usage and Cost Review

Overview

This skill correlates current Algolia billing and usage evidence with application behavior. It deliberately avoids embedding plan names, prices, free allowances, or assumptions that indexing is unmetered because commercial terms can change.

Prerequisites

• A named repository, environment, and Algolia application or index in scope
• The local lockfile and installed client types as implementation authority
• A safe read-only query or explicitly disposable test target
• Current first-party documentation for any provider behavior that affects the change

Tool Discipline

Use Read, Glob, and Grep to inspect local code, configuration names, tests, and dependency versions. Use WebFetch only for current official Algolia documentation. Use Write or Edit only after identifying the target files, constraints, and verification plan.

Current Contract