Hi, Nick here from SideGuide. Thanks for your questions and suggestions.
1. As of right now it seems like 90% of the responses can infer the language pretty well from the issue context. Although we are working hard to improve this.
2. We use the issue's labels to identify the issue type and choose an appropriate prompt depending on what type it is. Thanks for the suggestion, will add more screenshots about that asap.
3. We're currently only using GPT-3 (davinci-003) on production. But we are currently testing ChatGPT too, but we don't think it is ready yet due to it is down time/rate limiting and lack of fine-tuning capabilities. Because this is still an early MVP, we haven't gotten around to filtering abusive responses just yet.
Hey there! So, kinda of, we definitely took inspiration from RunKit and in the future we want to support different languages. Our main goal right now is to focus on the core developer experience, illustrating how one can use a company's API with a real use case, instead of trying out a single independent API endpoint. Once, we nail that, we would like to move to new languages.
I took a quick look at your podcast API product. First, this seems awesome! Would love to try it. Second, would love to see a web example consuming your API (if you don't have one). Maybe that's something that you could use SideGuide for and would be more aligned with our current state. Although I totally see why it would be awesome to execute all the api endpoints in different languages. Will keep that in mind and maybe explore that in the future.