{"data":{"slug":"algolia","failure_modes":[{"pattern":"Search operations count toward record quota","impact":"Agent search-heavy workflows hit billing limits unexpectedly. Service degrades (slower, then blocked) without clear error until quota is fully exhausted.","frequency":"common","workaround":"Monitor operations dashboard proactively. Cache frequent queries client-side. Implement query deduplication — agents often search the same thing repeatedly in a loop.","category":"rate-limiting","severity":"high","description":"Algolia's pricing model counts both records AND operations. High-volume agent queries can silently exceed the operations quota even with few records.","last_verified":"2026-03-11T19:08:09.523335+00:00","evidence_count":1},{"pattern":"Facet value limits silently truncate results","impact":"Agent category filtering misses items because facet enumeration is silently capped. Data analysis based on facets is incorrect.","frequency":"occasional","workaround":"Increase maxFacetHits in query parameters. Use browse endpoint for exhaustive enumeration. Never assume facet counts are complete.","category":"schema","severity":"medium","description":"Algolia limits facet values to 100 by default. Agents filtering by facets with >100 unique values get incomplete results with no warning.","last_verified":"2026-03-11T19:08:09.523335+00:00","evidence_count":1}]},"error":null}