Why it was built
I built this because I was tired of juggling Postman collections that lived in someone's cloud account, got out of sync with what was actually checked into source control, and couldn't be reasoned about or diffed like code. I wanted a tool that treats API collections as plain files in the team's repo — pullable, editable, pushable, diffable — while still giving me the everyday conveniences of a request client: headers, environments, JSON formatting, and codegen for whatever language I'm working in that day. The chaining feature came out of repeatedly needing to grab a token from one call and feed it into the next by hand; I wanted to click a value in a response and have it become a variable automatically. As a senior engineer who likes exploring an idea end-to-end, I wrote the Flask backend, the provider abstraction for Azure DevOps/GitHub, and the vanilla-JS frontend myself, with no build step, so the whole thing stays inspectable and easy to run anywhere.
