> For the complete documentation index, see [llms.txt](https://tazmania.gitbook.io/homepage/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://tazmania.gitbook.io/homepage/taz-inu-whitepaper.md).

# Taz INU Whitepaper

When looking at real-life Tasmania monsters, these creatures, which look cute as long as they don't open their mouths, were transformed into cartoon characters by Looney Tunes dating back to the 60s. This character, which gained its popularity in the 90s, will be a hit with us again in 2023. Taz, the eldest son of the house, who is very loved in his family, does not act with his feelings, but with the rumbling of his stomach and his instincts. The Tasmania devil is a constantly hungry, drooling character, and when he turns, nothing can stand in his way. Although he seems to be aggressive, this character, which is created quite cute, is pure and helpful.


---

# 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://tazmania.gitbook.io/homepage/taz-inu-whitepaper.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.