Hi spxneo, this is the author of the tool here. Thank you for voicing your opinion. We actually talked to a lot of individuals and we found that particularly p

Hi spxneo, this is the author of the tool here. Thank you for voicing your opinion. We actually talked to a lot of individuals and we found that particularly people who are part of frontend team or part of a QA/QE or CRE team who are not the primary developers of the backend/api were most interested in the LLM to API workflow feature, partly because going through the OpenAPI spec and understanding each endpoint is a lot of work. What our tool does it that it not only identifies the right endpoints and chain them but also pre-fills the request parameters or request body which gives them a chance to quickly experiment with backend. Of course you always have the option of drag and drop. But we hope that one day using LLMs will get commoditized with models being quite good and then that day a natural language translation will seem obvious Aside from that one of the major problems that we found that not a lot of folks want to expose their api authentication credentials or in-development/private apis to tools like postman or zappier. So giving an IDE like experience that works as a local desktop app helps alleviate a lot of privacy issues. Graphical representation of end to end tests was also a big ask