If Product A gets 500 credits and Product B gets 250 Credits, then Customers get 750 credits if they stack them.
Does PickAxe understand how to differentiate between both, or can all 750 credits be used for Product B? I ask because Product B is a more expensive image generation model.
We would like PickAxe to allow only 250 credits to be used towards it instead of 750 credits. Ensure the 500 credits stay with Product A, the lower image generation model.
Also, how would this work if we implemented a monthly credit purchase? Which PickAxe, or do they count for any product you stack?
@ab2308 @Ned.Malki @stephenasuncion @admin_mike This is super important to keep costs down. Any solution to this? Can we lock in credits to a particular PickAxe in a studio so if multiple are purchased, even when they stack, they can’t all be used on one PickAxe out of the bunch? Some AI models are costly
@stephenasuncion, do you have anything on this? I need to know soon because Flux 1.1 Pro API is $.04 per image generation, which is very expensive.
Is the only solution right now to put the Flux 1.1 Pro generator in a different studio away from the Flux Schnell image generator since that is dirt cheap if there is no way to differentiate credits between the two?
This isn’t ideal, but at least I know the current limitations if your system can’t differentiate between credits being tied to one PickAxe in a studio.
One hundred image generations would still be $4 for the Flux Pro 1.1 if my studio allows users to use the 500 image generations from Flux Schnell for the advanced Pro PickAxe, 600 images, or $24 monthly, which is very expensive. I only want them to be able to use the 100 on Pro and 500 on Schnell, not combine all 600 and be able to use all on Pro if they buy both PickAxes. Does this make sense?
1 Like