The article mentions that the only "contract" you have with the client is a GET request to a top-level URI, and from there, everything should be described via some sort of hypertext, and the application can go from there.<p>I just don't understand how that's supposed to work in the context of, say, a server application. In a browser, you have a human to make sense of the hypertext and decide what looks worth clicking on, which forms look like you want to fill out.<p>In an API, I already know, by the fact that I'm writing an application, what I want to do. I want to delete this customer, run a garbage compaction on a repository, search for new records. What's the point of "discovering" these URIs via hypermedia?