> For the complete documentation index, see [llms.txt](https://urchin.gitbook.io/overview/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://urchin.gitbook.io/overview/what-is-urchin.md). # What is Urchin? Content management plays a large role in many application and website strategies. For teams building decentralized appliations, there few frameworks that offer content management via blockchain that provide transparency and immutability. In leveraging [Urchin, the blockchain based CMS](https://www.npmjs.com/package/urchin-web3-cms), teams can ensure that content stored within the blockchain is tamper-proof and resistant to unauthorized modifications, and offers a trackable history that is publicly available. This not only enhances security, but follows the ethos of building in Web3 while enabling seamless integrations with smart contracts. Urchin is: * *headless* - detached from primary appliations and available via API calls for builds or dynamic content filling. * *a fully capable CMS* - designed to manage markdown content, images and other media, and meta information for organization and taxonomy. * *an open-source, public protocol* - as opposed to most cloud-based CMS solutions, Urchin is a network of programs deployed on the blockchain with an open-source MIT license. --- # 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://urchin.gitbook.io/overview/what-is-urchin.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.