Right, but why stop there: going to different URLs for different resources is also nuts. REST is fundamentally broken from this conflation of concerns across different layers.
GraphQL — where you are sending and receiving data (and application errors) to a specific endpoint is much much saner.
No, REST is good, but you should either use it or not. If you're not going to use it, then you really ought to be sending and receiving data to a specific endpoint. And once you're doing that, it actually starts to be questionable whether you need or want HTTP at all (ignoring the hellworld of middleboxes we live in).
GraphQL — where you are sending and receiving data (and application errors) to a specific endpoint is much much saner.