# Recursion An important exception to sandboxing is recursion: access to `ord`'s `/content` endpoint is permitted, allowing inscriptions to access the content of other inscriptions by requesting `/content/`. This has a number of interesting use-cases: * Remixing the content of existing inscriptions. * Publishing snippets of code, images, audio, or stylesheets as shared public resources. * Generative art collections where an algorithm is inscribed as JavaScript, and instantiated from multiple inscriptions with unique seeds. * Generative profile picture collections where accessories and attributes are inscribed as individual images, or in a shared texture atlas, and then combined, collage-style, in unique combinations in multiple inscriptions. A few other endpoints that inscriptions may access are the following: * `/blockheight`: latest block height. * `/blockhash`: latest block hash. * `/blockhash/`: block hash at given block height. * `/blocktime`: UNIX time stamp of latest block. --- # Agent Instructions: 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: ``` GET https://satsmax.gitbook.io/white-paper/inscriptions/recursion.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.