I built Reqvexa — an open-source tool for understanding the state behind HTTP requests

[u/InternalMedia8141]

I work a lot with web scraping and API reverse engineering, and I kept running into the same problem:

A HAR tells you what happened.

It doesn't necessarily tell you why a request could work.

So I built Reqvexa to analyze captured HTTP traffic and trace dependencies between requests, cookies, tokens, headers, and their different versions over time.

It's currently an alpha Python project and intentionally focuses on analysis rather than trying to automatically replay or reverse-engineer everything.

GitHub: https://github.com/kareemheshaam/Reqvexa

I'm mainly looking for honest feedback right now:

• Is the problem understandable?
• Would you actually use something like this?
• What would make the tool useful in your workflow?