is there any reason you wouldn't call it?
Is calling it a business decision? or is it an impl detail of how the API works?
I'd say if it's a business decision / something with that decision needs to be tested, kick it back up to the use case / domain, if it's just, thats how the API works, and from a business / decision perspective, it either all works, or it all doesn't, then do it in the repo and keep it out of the way