spjain

Feel the same way with integralapi.co – we'll be going open source very soon but want to make sure we have everything "open source ready".

Can't give out code that can't be exposed to the public.

Nice concept – are you guys building any finetuning on top of this that could make this more relatable for my users when they got on my website.

That would be super helpful. Also curious which API you're using on the backend over here (guessing OpenAI's gpt-3.5 at the moment)

Speed of development on these guys is huge, and have enjoyed using their SDKs. Community is getting involved in building things like auto-retry with backoff and other pretty helpful features in SDKs. Big fan of these guys!

What's the thought process behind the product with API Keys? Why do you build those for your end user, and what's the goal of someone using that. Unless I'm misinterpreting.

Just built an External API Gateway anyone can use to build public APIs 10x faster.

Biggest thing – we'd love some feedback. Let us know where we can improve, any concerns, or feature requests!