Unexpected operation usage when running multiple low-traffic Algolia indices

The goal is to lower monthly expenses for a low‑traffic search workload by determining whether merging several Algolia indices into a single index that uses filterable attributes can reduce the total number of stored records enough to remain within the Free tier quota.

Constraints include the Free tier limits of 10,000 records and 10,000 operations per application, where each index contributes to the overall record total, and the uncertainty that consolidating indices may increase relevance‑tuning complexity, potentially offsetting any storage savings.

Does merging indices reduce the total stored records below the Free tier threshold?

Will the added relevance‑tuning complexity negate the cost savings from fewer records?

Are there any hidden operation cost impacts when using filterable attributes instead of maintaining separate indices?