> For the complete documentation index, see [llms.txt](https://docs.bitcoincomics.art/niftysats/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bitcoincomics.art/niftysats/inscriptions/character-collections/volumes-3-12.md).
# Volumes 3 - 12
Above, you'll see the original hand sketched concepts for the rest of the NiftyFam. [Review the chart here](/niftysats/inscriptions/character-collections.md#all-12-characters-and-supplies) to see the full release order and supplies of all 12 volumes.
The SilkToads are up next, with 1111 ordinals with traits and designs that will tell the story of the infamous SilkRoad website created by Ross Ulbricht, which allowed all sorts of illicit merchandise to be bought and sold using Bitcoin.
After them, will be 999 Axomotos, that have a personality similar to The Flintsones' Dino. A happy-go-lucky axolotl that will have his own story to tell.
We'll update these pages for each collection as we draw closer to their individual releases, and provide more details about each collection and corresponding mint details.
Now get to know the history of the [BITCOIN•COMICS runes](/niftysats/inscriptions/runes-intro.md)!
---
# 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.bitcoincomics.art/niftysats/inscriptions/character-collections/volumes-3-12.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.