Show HN: I made a credit system API (creduse.com)
I'm a solopreneur and I made it very easy to integrate a credit system into your apps and games using Creduse.
I built Creduse because more and more users want pay-as-you-go models, and founders need new ways to increase user engagement or nicely limit cost-intensive features (see AI).
Creduse is built by a developer for developers. I hope it will help as many startups as possible.
Feedback are very much appreciated.
Francesco
23 comments
[ 3.1 ms ] story [ 67.8 ms ] threadWould be amazing if you handled the buying of additional pay as you go credits for us too - that’s the next thing we’d need to build.
Sent you a chat with some queries - we need to use cycles and payg in combination, and the api call to get remaining credits should include the cycle start and renewal date, with the different credit types remaining too.
The option to choose which credit type subtract should come from by default would be good too - to allow users to use their cycle credits first and then eat into their payg back up credits.
About the `get-active-balance` endpoint - you're right, it's pretty basic at the moment. It just gives you the total active balance and user ID. It doesn't break down cycle vs PAYG credits or show cycle dates yet.
I've add it to the top of my pipeline. I'll be working on improving this endpoint to give you more detailed info about the user's credit balance.
Regarding the option to choose which credit type to subtract from, I'll keep this in mind and consider its feasibility. Can't promise anything on this just yet, but I appreciate the idea.
I really like your suggestions though! It's exactly the kind of feedback I'm looking for. Thanks for bringing this up, and thanks for subscribing!
By "handled the buying of additional payg credits" do you mean the payment processing?
Probably something you'll need to grow support for if you want this to be a drop-in solution for mobile devs.
[1] https://medium.com/@ronaldmannak/how-to-validate-ios-and-mac...
Couple of questions: shouldn't my customers be taking care of this since I don't know their architecture? I think mobile devs can hugely benefit from Creduse, can you point me on how to support them for this scenario?
open to discuss via email if you prefer: francesco@creduse.com
I want to implement Creduse into a free ai character chatbot I've created in the past (hellspitching .com) to showcase its use.
You can find a lot more details on doc.creduse.com