This specification defines the QUERY method for HTTP. A QUERY requests that the request target process the enclosed content in a safe and idempotent manner and then respond with the result of that processing. This is similar to POST requests, but QUERY requests can be automatically repeated or restarted without concern for partial state changes.
This is pretty good, though I expect even if it’s accepted it’s going to be a long journey before you can reliably use it
If we’re adding stuff to http, it would be nice for some additional status codes, things have moved on a bit since the early days
There should be a 400 that just says “fuck you and your AI”
I believe you can use 422: Unprocessable Content for this.
“I know what you said, but I’m not answering you.”
That’s what 418 is for imo