In the past, I was able to connect APIs from LLMs to my workspace so that the billing for usage goes to them. I tried it again now, using the same spot in settings>API, but now it only lets me generate API instead of connecting to external ones. Is there another way to do this?
I was counting on this feature to work with some of my clients. They want their own workspace for the chatbots we build together. But I don’t want the usage of their clients to go through me. For example, if they go over what they paid me in advance, I don’t want it to drain my credits and have to chase them to pay me back. If I can’t use an external API for it now, is there another way to isolate the usage of one studio so that it doesn’t impact other studios?
This is a great question. We have started to roll back BYOK support as you can see here, but that does put you in a tough position because it’d have been easier to use your client’s API keys. We have a solution coming in our next big update for this, but the short term solution would be to have your clients make Pickaxe accounts to allow for billing through us. Is there a reason that isn’t possible?
I’ll explain more of my use case for context in case it is helpful - some of the clients are 1:1 and others are course clients. For the 1:1, they want me to do the setup and ongoing management for them. For the course clients, they need a testing environment just to try things out and circulate to their testers before I put their project live in my main studio.
Having the clients open their own accounts would mean additional expenses for them and more headaches in account management for me, like many log ins and outs and difficulty in getting good statistics overall.
It’s exciting to hear about the new solution you are planning! I’d love to hear more. Do you plan to bring back the external API? And are you able to share a rough expected timeline?