Hot take: REST is cope. I'd take a well-documented RPC-based API over REST any day. It's only "useful" for things that are dead simple anyway and it's not even good at the U part of CRUD! And when you want to do anything other than basic CRUD actions on a resource you're either making weird sub-resources or straying away from REST anyway. It's annoyingly difficult to find where routes live, too many places use fancy language features to hide where an HTTP path is actually mounted and it just wastes so much time (or tokens).