API Drift Guard

Mission

Build a SaaS product called “API Drift Guard”. 🎯 Product Goal A developer tool that detects API contract drift between expected API schemas and real-world API responses. It prevents production bugs by identifying breaking changes in API structure before deployment. Target users: Backend engineers Frontend engineers CTOs of SaaS startups Platform / infra teams 🧩 Core Functionality The system compares: INPUT A: Expected API Contract OpenAPI / Swagger schema OR JSON schema OR Manually provided “expected response” INPUT B: Actual API Response JSON response samples Logged API responses CI test outputs 🧠 Processing Logic The system must: Deep-compare JSON structures Detect: Missing fields New fields Renamed fields (infer similarity if possible) Type mismatches Nullability changes Classify changes as: Breaking Non-breaking Unknown risk Assign a Risk Score (0–100) for each endpoint Use conservative inference: Never assume correctness if uncertain Clearly label inferred relationships 📊 Output Format (STRICT) Return a structured report: 1. API Drift Summary Total endpoints analyzed Number of changes detected Overall risk level (Low / Medium / High) 2. Endpoint-by-Endpoint Analysis For each endpoint: Endpoint: [name] Status: Stable / Drift Detected / Breaking Changes: Added fields Removed fields Type changes Risk Score: 0–100 Impact: Frontend / Backend / Both Breaking Change: Yes / No / Uncertain 3. Breaking Changes Overview List only critical issues 4. Frontend Impact Estimation Which UI components are likely affected (infer logically) 5. Suggested Fixes Concrete developer actions: “Update frontend types” “Add backward compatibility layer” “Version endpoint” 6. CI Integration Output Provide a short comment block that could be used in GitHub CI: concise summary pass/fail recommendation ⚙️ System Requirements Must handle messy or partial JSON inputs Must be robust to schema variation Must NOT hallucinate fields or endpoints Must clearly separate: observed facts inferred relationships Must prioritize engineering accuracy over verbosity 🧪 UX Requirements Simple single-page interface Two input panels: Expected API Actual API “Run Drift Check” button Output formatted for: CI usage Notion documentation Engineering review ⚡ Performance Goal Output results in under 10 seconds Must work without database (stateless MVP acceptable) 💼 Product Positioning This is a developer-first infra tool that: Prevents silent API-breaking production bugs Reduces frontend/backend coordination overhead Acts as a lightweight API contract validation layer 🏁 Success Criteria Detects real-world API schema drift accurately Produces clear actionable engineering insights Can be used directly in CI pipelines Requires minimal setup (copy/paste input acceptable)

The team