Hey Product Hunt 👋 I built WireQuill because API documentation has a habit of describing what an API is supposed to do while the application keeps changing underneath it. WireQuill takes a different approach: it sits between your client and backend as a local reverse proxy, observes real HTTP traffic, and builds an OpenAPI 3.1 contract as you use your app. No handwritten spec. No annotations. No account. No cloud service. No traffic upload. The first release deliberately focuses on one workflow: Traffic → OpenAPI → Live Docs WireQuill discovers endpoints, parameters, request/response schemas, status codes, media types, and authentication from observed behavior. The inference is intentionally conservative rather than inventing validation rules from a few samples, and common sensitive values are redacted before examples are persisted. It’s open source under Apache 2.0, and I’d especially love feedback from people who work with APIs: how useful is this workflow in your day-to-day development, and where should it go next? Contract diffing, request replay, runtime-derived fuzzing, and local mocks are some of the directions I’m exploring. Thanks for checking it out!

WireQuill

Turn real HTTP traffic into live OpenAPI docs

Turn real HTTP traffic into live OpenAPI docs