OpenAI-Compatible Provider setup in BYOK settings
The shutdown of Straico proves that more flexibility is needed for BYOK settings.
Could you please add OpenAI-Compatible Provider setup in BYOK ?
OpenAI-Compatible setup (baseURL + API) is currently the standard for BYOK.
Why does this matter?
Freedom of Choice: Users are able to use their current AI Providers (you name it OpenRouter, Google AI Studio, Ofox, LLM Gateway, Runeware...)
No Reliability Trade-off: It’s a standard "plug-and-play" format, without degrading performance
Future-Proofing: Avoid be tied to a single provider’s roadmap.
Log in to comment and vote
Comments3
Eray Ocak
Aug 25
Hey there, thank you for your feature request! After some consideration, we are happy to announce that we’re adding support for custom OpenAI-compatible providers.
We’re also adding prebuilt templates for common providers such as OpenRouter, Vercel AI Gateway, and Cloudflare AI Gateway.
New custom provider options will become available to all users with BYOK feature in the following days.
FT
Aug 25
That's great news! Supporting OpenAI-compatible gateway providers is a massive win for flexibility.
Actually, for multi-step AI agentic tools, utilizing providers that offer an Open Responses-compliant API will be much more efficient. It unifies advanced agentic loops (like reasoning, native tool calling, and asynchronous execution) into a single API interface. This eliminates complex orchestration on your client side and makes your analytics agent future-proof.
Eventually, you can add the capability of persistent Agent Memory (Kai 3), using a memory middleware like Mem0 which injects these long-term memories into the Open Respones request context, allowing Kai to maintain deep, continuous knowledge without bloating your client-side architecture.
FT
Aug 25
The APIs of these Gateway providers are Open Responses-compliant:
OpenRouter
Vercel Al Gateway
Cloudflare Al Gateway
LLM Gateway