Investigating Validation Error with source: noImages in API Requests and Recent Image Handling Changes

Ezequiel B. Dennis L. - I've been digging into this with engineering and I'm not able to reproduce the validation error you're hitting. When I test "source": "noImages" in production, the request goes through fine. An engineer I talked to mentioned there was a recent change around how we handle images from inputText, which might be the culprit here. Could you share your complete request bodies? I want to see the full JSON you're sending to the POST endpoint, including all the parameters. Dennis, you said this was working in production until a customer hit it this morning - any sense of when it stopped working? That'll help us correlate with deployments. One theory: if your inputText has any image URLs in it, the recent changes might be trying to process those and triggering the model requirement. Worth checking if that's the case. I want to see what's actually different about your requests before saying anything about workarounds. The API should definitely accept "source": "noImages" without needing a model parameter. Once I have the full picture I'll escalate with the specifics and get you either a fix or clarity on what changed.