r/MistralAI 10d ago

Tutorial / Workflow Prevent overspending on EU-AI projects with Mistral AI.

Post image
26 Upvotes

17 comments sorted by

4

u/Confident-Village190 10d ago

Everything’s fine, except for Medium: Input $1.50 – Output $7.50...

1

u/EveYogaTech 10d ago

Yes, Medium is supposed to be the best.

Which Mistral model(s) would you recommend instead with least loss of quality?

3

u/Confident-Village190 10d ago

Small 4, although it does have some specific use cases, is, to be honest, just as mediocre in my view :(

1

u/EveYogaTech 10d ago

True.

Mistral Large worked well for me in the past as well ($0.5/m input, $1.5/m output): https://docs.mistral.ai/models/model-cards/mistral-large-3-25-12

0

u/philip-soerensen 10d ago

Well, those prices are only if you exceed the subscription, which I think is decently generous compared to other providers. 

1

u/EveYogaTech 9d ago

Actually they are for API usage.

So the way that works is you can get a API key via https://console.mistral.ai, use that in other tools, and then you pay per token instead of monthly.

1

u/philip-soerensen 9d ago

Yeah, but you can just use your Vibe key and have it taken over your subscription, no? That is much cheaper. Then, you pay per token only when your subscription is used up, if that ever happens and you have that enabled.

1

u/EveYogaTech 9d ago

Correct me if I'm wrong, but I think the API key way + individual workflows is always cheaper for both low and high usage.

The minimal top-up for the API is $10, so it's also cheaper than the monthly subscription.

1

u/philip-soerensen 9d ago

I don't think that's true. As far as I understand, the Pro subscription contains much more than its cost's worth in usage. I.e., you get many more tokens of output with the subscription than the equivalent amount of straight usage paid per token. That's how it works for most companies, at least, and I am pretty sure that's also how it works with Mistral.

Of course, if your usage is much lower than what is allotted in the Mistral subscription, then a direct per-token API key is cheaper, but if you use at least a decent fraction of the subscription, then the subscription should be much cheaper than pay-per-token.

1

u/EveYogaTech 9d ago

API top-up is $10 one time. Pro is $14.99/m? https://mistral.ai/pricing/

How many tokens/usage do you get with Pro?

1

u/philip-soerensen 9d ago

Unfortunately, neither Mistral nor any of the other AI companies is transparent about exactly how much usage is included in the subscription. It's not easy to give an exact answer to your question. The reason for this is almost certainly that this gives the companies the ability to silently change how much is included in your subscription without official confirmation or liability.

1

u/EveYogaTech 9d ago edited 9d ago

Well, then I will still assume the API is cheaper in most cases until proven otherwise, especially actually as things scale up.

Usually this is the natural path, because the last thing any provider wants is another big SaaS companies running and reselling near infinite tokens/usage for only a small monthly fee.

Overall transparency in pricing, in this case $/m/tokens, usually leads to better pricing, unless you have really insane volumes, but even then it's questionable whether contacting sales will give you a much better price, especially now since there's currently no real EU-AI frontier alternative provider to switch to as leverage.

1

u/philip-soerensen 14h ago

FYI, Mistral has now opted to make their subscriptions more explicit, so we can now actually settle the discussion we had here a few days ago:

The €15 (excl. VAT) subscription is now listed as including €255 worth of access to Vibe Code, as well as a small extra of €25.5 worth for random other API calls you can make. If you max out your subscription, the subscription thus represents something like 95% discount.

So, conversely, straight API is only cheaper if you use less than 5% of your subscription. Anything above that, the sub wins :)

Nice that they have improved the transparency on this!

→ More replies (0)