> For the complete documentation index, see [llms.txt](https://book.restfulnode.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://book.restfulnode.com/part-2/chapter-2/summary.md). # Summary In this chapter, we looked at the history of the web and how REST was introduced. We clarified certain confusions around the topic of knowing the differences between HTTP and REST. We have taken a look at Roy Fielding's dissertation and have broken down its components and how each of them are related to HTTP. We then looked at real world examples and examined what and why certain APIs were RESTful and others not. We then delve into the topic of the Richardson Maturity Model and explored why being RESTful is not a black or white topic, but rather a complex subject in which many levels exist. That being said, knowing what is truly RESTful is useless if put into practice the wrong way, that is why we must be willing to follow pragmatism over dogmatism in our everyday jobs as developers. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://book.restfulnode.com/part-2/chapter-2/summary.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.