Verified purchaser
Refund requested due to bugs, BYOK confusion, and exposed API keys
I’m giving Syllabbles 3 tacos because I have not tested every feature, so this is based only on my early experience.
The product has potential, but I ran into several serious issues almost immediately. My OpenAI API key did not work properly, and I did not receive a clear explanation or troubleshooting support for why it was failing. My first eBook generation also failed, which made it difficult to trust the product for professional content creation.
The biggest concerns for me are transparency and security. I could not clearly see when my own API key was being used, how credits or usage were being handled when generations failed, or whether failed outputs still consumed credits. That lack of clarity is a problem for a BYOK product.
I was also concerned to see my secret API keys visible in the interface instead of being properly masked. API keys should be protected by default. Seeing them exposed raised questions about how securely credentials are being stored, displayed, and processed.
I also expected certain BYOK-supported features to be available based on the AppSumo listing, but after activating the product, the backend appeared to show some of those features as only available on a higher tier. That mismatch was one of the main reasons I decided to request a refund.
I have not tested the full platform, but based on the early bugs, unclear BYOK behaviour, failed generation, limited transparency around usage, and visible API keys, I do not feel confident using this professionally.
Magnus_Syllabbles
May 6, 2026Thank you for your feedback.
In many cases when a user’s API key does not work, it is due to no or low credit balance on the provider side. For example, a ChatGPT subscription and an OpenAI API billing balance are separate, so if you are using your own OpenAI key in Syllabbles, you would need active API credits in your OpenAI platform account for generations to succeed. The same applies to other providers where relevant. If that was not the issue in your case, please reach out to us and we will take a closer look at your account.
On usage credits, Syllabbles is not currently metered on tokens/credits. We count creations/outputs instead, while managing provider usage differently on the backend. That said, we understand why this is useful for BYOK use cases, and we will look into implementing it in a more transparent way in the future especially for BYOK cases.
On the API key visibility concern, keys are only visible when the account owner opens that specific entry for editing. Otherwise, they are hidden. Even so, we agree this can be improved further, and we can move toward permanently masking them and limiting edits to delete/replace only.
On BYOK features, Brand Voice, Humanize Content, and AI Model Selection are available via BYOK on Tier 1 and Tier 2 according to the AppSumo listing, and once a supported key is added, those features should activate accordingly in the account.
Thank you again for taking the time to share your experience.