> For the complete documentation index, see [llms.txt](https://whitepaper.memetheftauto.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://whitepaper.memetheftauto.com/the-art/legalities.md).
# Legalities
We’ve also done our due diligence to ensure the artwork is legally protected and not in violation of Rockstars IP patents, copyrights, or trademarks. According to Section 107 of the Copy Rights Act, the “fair use” doctrine protects parody works from copyright infringement claims, provided the work meets certain criteria.
A parody is specifically recognized in the statute’s examples as a form of fair use when it:
\- Uses elements of the original work to comment on, criticize, or mock it.
\- Transforms the original work rather than simply copying it.
\- Takes only what is necessary from the original to make its point.
The U.S. Supreme Court case **Campbell v. Acuff-Rose Music, Inc. (1994) affirmed that parody can be of commercial use and still qualify as fair use, meaning monetization is allowed if the parody meets the legal tests.**
Each character has been reviewed and cleared as a valid parody, which fully protects MTA and its artwork.
{% hint style="info" %}
\*\*Disclaimer: *Meme Theft Auto is an original parody developed by Web4 Innovations LLC and is not affiliated with or endorsed by Rockstar Games or Grand Theft Auto.*
{% endhint %}
## **Reference Links:**
#### - Copyright.gov: - Govinfo.gov: - Corporate.findlaw\.com:
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://whitepaper.memetheftauto.com/the-art/legalities.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.