Using Pickaxe’s direct billing with Replicate instead of my API key it always fails please help ASAP. Tried with all Flux models in replicate and it fails multiple times.
Hi,
I’ve just tested this and it seems to work alright, both using our API key and a custom one.
Did you make any change recently? We did not change anything with the Replicate action recently.
2 Likes
Have the calculations been fixed yet for Replicate? I am running a mass outreach campaign that relies on these Pickaxes, hence the urgency. I am currently being charged almost two dollars per action when it should be five cents per action. I need the difference refunded as well please.
hi there ! on our end it doesn’t seem that the calculations are off, sometimes extra runs can be triggered based on model/slug differences. so just a reminder: make sure we’re using the format of
‘’‘black-forest-labs/flux-schnell’‘’ as opposed to '''https://replicate.com/black-forest-labs/flux-schnell'''
if there are any other issues please let us know and we’re happy to help (-:
1 Like
Hi @carsondev, thanks for responding so quickly. So you are saying since I put the https:// the first time it can accidentally force multiple action retries i.e. 15 times? That would equate to $1.50 for one action explaining what happened.
Actually at 5 cents per action it force retried one action 35 times for the two actions each to equal 3.49 dollars. Around 70 retries is that accurate?
Yes ! That is what happened, sometimes model providers/MCP/Action hosts can be a little picky on how the "slug’ is handled.
(In your case here it’s the inclusion of the ‘https://url.com’ but it could have happened if there was an extra hyphen/backslash and it has happened to me in dev environments before, so you’re not alone)
I’ll PM you with regards to specifics for the two runs we’re talking about so I don’t share any of your personal sessionIds or action costs (-:
2 Likes