One parameter, three contracts: the API field that changes meaning by endpoint

Here is an API design problem I ran into recently that I have not been able to stop thinking about, because every option for fixing it is worse than it looks. A media generation API has three creation