Sumo.Ling23693Q: BYOK, API and Credits Question
Wanted to know if the output produced from BYOK will be of similar or worse quality compared to using Krisspy's credit? Which other platform do you recommend we can integrate with BYOK feature? Do you have a guide on this?
Can we propose to have a carry-forward/roll-over credit system for a max of one or two months? Just to not waste our previous unutilized credits, if any available.
Besides, do you think that in the (near?) future AI technology gets cheaper and the credit per screen will be reduced for LTD users like us? i.e. One new screen can be reduced to 5 credits and an alteration will cost like 2-3 credits?
Any plan for an API endpoint for quick generation of 3-5 screens?
Lastly, we should be having HiFi for web and React code export by the end of this month? Does it support TailwindCSS or styled library?
Thanks and good luck!
Sofiane_Krisspy
Feb 25, 2025A: We're planning to integrate Anthropic for the BYOK feature, and it should be available around March. We're currently adapting the agent to make it work, and we hope to maintain the same quality level.
Regarding rollover credits, this is a frequent request. While it's not available today, we are considering a kind of "credit savings system" that could allow users to recover unused credits for one month, for example. So yes, this is something we find interesting.
On the topic of credit reduction, I believe another user has already asked about this, and we are actively working on providing a performance selection option, which would allow us to lower the credit cost per screen.
I didn’t fully understand the need for the API feature—where would the generated screens be sent? Could you clarify that?
As for HiFi for web, it has already been activated—we merged LoFi and HiFi together.
The React code export is still planned for the end of the month, though with testing, it will likely be available next week.
And yes, TailwindCSS can be used with classNames.
Thanks for your questions and support! 🚀