FYI, when a user enters an incorrect date/origin/destination the search engine still counts the invalid search towards the number of credits used.
For example, I accidentally put 2022-XX-XX instead of 2023-XX-XX and it ate up 10 credits (since I had a date range of 10 days)
Okay this has been fixed (it was actually pretty crucial for alerts, so the timing worked out).
It will now just error out if you put in any dates that are before the current date in UTC-12.