What problem does it solve?
Ensures an HTTP/JSON endpoint behaves according to its spec by driving a running service end-to-end and validating the full response (status, headers, body, timing) with captured evidence.
Core Features & Use Cases
- Deterministic endpoint driving: Starts the server, polls readiness by hitting a real endpoint, and sends the actual request via curl.
- Transcript-based verification: Captures request/response artifacts into a structured evidence directory for auditing and debugging.
- Spec comparison via assertions: Uses a jq-based assertion grammar to validate response shape and headers, then classifies outcomes as spec violations vs environmental flake.
- Use case: Confirm that a route change (schemas, status semantics, headers, or error handling) still matches expectations before merging.
Quick Start
Run http-qa after your latest changes and tell it which endpoint scope to verify, then review the generated verdict and transcript evidence under .agent-history/oracle/.