
I built an AI-powered API Proxy to explain 4xx errors in plain English
Let’s be honest: 422 Unprocessable Entity is a nightmare when you're in the flow. I got tired of it, so I built Inspekt. It’s a headless proxy that intercepts failed API requests and injects human-readable AI fixes directly into the JSON response. The Tech Stack (The part they care about): Next.js (App Router) for the landing and dashboard. Vercel Edge Runtime for low-latency proxying. OpenAI SDK to generate the "Diagnosis" field in real-time. TypeScript for everything (obviously). How it works Instead of hitting your API directly, you hit the Inspekt proxy. If your API returns a success, it passes through. If it fails? Inspekt catches the error, asks an LLM what went wrong based on the schema/payload, and appends a _diagnosis field to the response. We are live on Product Hunt today and I’d love to hear your thoughts on the proxy architecture! Product Hunt: https://www.producthunt.com/posts/inspekt Live Site: https://inspekt-api.vercel.app
Continue reading on Dev.to
Opens in a new tab




