> For the complete documentation index, see [llms.txt](https://docs.legitimate.tech/public-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.legitimate.tech/public-docs/project-docs/required-activation-assets.md).

# Required Activation Assets

What materials do I need for a project with Legitimate?

For creators and brands using Legitimate's services, we require a set of assets to be provided to activate your tags. All assets must be sent to the Legitimate Team at least two weeks before the project launch. If a client fails to do so, there’s a risk that the tags will not be activated in time.

Further information about each asset type and instructions on specific specs are hyperlinked

* Item Image
  * Image - We recommend this be a rendering or image of the physical item. Please see our image spec requirements [here](/public-docs/project-docs/required-activation-assets/image-specs.md)
* Item Animation (Optional)
  * Please see our animation spec requirements [here](/public-docs/project-docs/required-activation-assets/animation-specs.md)
* Item Title (name)&#x20;
  * 50 character count limit&#x20;
* Item Description
  * Description of your item, we recommend keeping this at 2 - 3 sentences tops. You can always add additional information in the rest of the digital experience if need be.
* Header Logo (Optional)&#x20;
  * If you'd like to replace the Legitimate logo at the top of the digital experience. Please see our spec requirements [here](/public-docs/project-docs/required-activation-assets/header-logo-spec.md)
* Builder.io Exclusive Content
  * By leveraging Legitimate’s builder.io integration your team can easily add custom content to your Legitimate Digital Experience. Content can include images, videos, text, QR codes, etc.
    * using the [Figma to Builder.io plug in](https://www.builder.io/c/docs/import-from-figma) you'll also we able to seamlessly integrate your figma designs into your Legitimate Digital Experience
  * Custom content will need to be added by the client team by following our [best practices and guidelines](/public-docs/project-docs/managing-your-skus-on-legitimate-dashboard-with-a-third-party-cms-integration/how-to-use-the-legitimate-builder.io-integration.md). If you would like the Legitimate Team to help further customize your Legitimate Digital Experience please inquire about our App Integration & Custom Legitimate Digital Experiences

#### What does the digital experience look like?

The top part of the digital experience, labeled in red below, is where the item image, title, and description will go. Everything below the "Item Details" section is what you'll be able to customize using our Builder.io integration.

<br>


---

# 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://docs.legitimate.tech/public-docs/project-docs/required-activation-assets.md?ask=<question>&goal=<user_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.
