Eliminate Costs of Unused Retrieval Latency in Your Cloud Chunks

Your pipeline fetched 10 chunks. Your LLM saw 3. You set TOP_K=10 on your vector store. Ten candidate chunks means more signal for the model — that's the logic. Then you run npx ragscope and the audit prints: WARN 51/100 █████░░░░░ my-rag-service │ "what are the pricing tiers?" │ │ ✗ precision 30 ██