I don’t think that was a great example since there’s only so many refunds a customer is going to ask for. And it’s saving time that otherwise maybe would have to go through a human. The rate is low enough that a more expensive model makes more sense.

Though for tasks where you are trying to search through billions of documents, social media posts, etc. and extract certain information, where each individual post is of low value and only the data in aggregate is valuable, then that’s where you’d want something cheaper and faster.

Such as if you want to look at all posts on X in the last few months and find how many have a negative or positive sentiment about the economy (or are unrelated).

Of course you could use a special-purpose model for this, but the whole point of something like Jev is to ask whatever questions you want without having to train something new.

    > so why invest into a more complex solutions

Not sure what's more complex about one REST API call versus another REST API call...