Building a "Semantic" API Proxy: How I handled privacy and 200 OK "Lies"

I’ve spent the last few weeks building Inspekt, an AI-powered proxy that tells you why an API failed instead of just giving you raw logs. I hit 100 upvotes on Product Hunt today, and the "Day 1" feedback has already forced me to rethink my architecture. The "200 OK" Problem: Standard monitors only trigger on 4xx/5xx codes. But what about GraphQL or certain REST APIs that return a 200 OK with an errors array hidden in the payload? Inspekt solves this by analyzing the semantic meaning of the res