api-contract-qa

Validate live API responses by capturing network traffic with Chrome DevTools MCP and comparing it against api-contracts-*.md files to detect frontend-backend integration drift. The process checks envelope structures and field types, outputting a Markdown QA report.

API contract drift occurs when runtime backend responses no longer match frontend TypeScript definitions. Catch this drift by matching live network requests to proxy routes and validating the response envelope, field presence, and data types against documented contracts.

Generate a QA report by capturing live API calls and checking them against api-contracts-[feature].md files. The output is a Markdown report with endpoint-by-endpoint results, actionable alignment guidance, and severity labels like BLOCKER, WARNING, and INFO.

Yes, you can validate API response envelopes using Chrome DevTools MCP to capture live traffic. The validation process checks the success, data, message, and requestId fields, verifying their presence and types against the defined TypeScript contracts.

Yes, the API validation process works by matching network requests to frontend proxy routes such as /api/backendProxy. It captures the live responses passing through these routes and validates them against the expected contract fields and types.

The best way to flag API response mismatches is to validate live traffic against api-contracts-*.md files and generate a Markdown report. This report uses severity labels like BLOCKER, WARNING, and INFO to prioritize backend alignment tasks effectively.