> For the complete documentation index, see [llms.txt](https://docs.sandshrew.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sandshrew.io/metashrew-open-source-repositories/metashrew-runes.md).

# metashrew-runes

METASHREW provides a WASM port of the runes metaprotocol, whose canonical representation is hosted as a sibling to the inscriptions metaprotocol within the ordinals codebase.

The METASHREW port of runes is available at:

{% embed url="<https://github.com/sandshrewmetaprotocols/metashrew-runes>" %}

With the above sources, it is possible for even a single developer to create a programmable variant of the runes asset class. Or, subject to the constraints of the runes protocol, metaprotocols can extend the indexer provided here to architect runes assets which may have additional utility other than their use for trivial transfers.


---

# 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://docs.sandshrew.io/metashrew-open-source-repositories/metashrew-runes.md?ask=<question>&goal=<endgoal>
```

`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.