> For the complete documentation index, see [llms.txt](https://docs.sia.tech/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sia.tech/miscellaneous/sia-brand-guidelines.md).
# Brand Guidelines
Third-party projects are an important part of the Sia ecosystem. They broaden the range of applications on Sia and add solutions that are not developed by our team.
We aim for users to discern between core and non-core projects for several reasons:
* Non-core projects often involve some level of centralization, which is entirely acceptable. Users benefit from having choices, and centralization allows for the implementation of features that are more accessible to achieve compared to those on Sia's core infrastructure.
* There's the potential for confusion where users might mistake your project for something created by the core team. We want to ensure that users know where to go for help.
* We want your project to get credit for your work and to stand on its own.
These guidelines help developers keep their projects clear and distinct from core Sia projects.
## Logo and Branding Usage
The Sia Foundation exclusively owns the Sia trademark in the United States and prohibits the direct use of the Sia logo or wordmark in any third-party project. Do not copy, modify, or style the Sia logo or wordmark in a way that could cause confusion or misrepresentation.
Sia Wordmark Logo
Sia Shorthand Logo
### Referencing Sia in Content
You may use the name **“Sia”** in plain text when accurately referring to the project in articles, reviews, presentations, or other informational materials.
* Do not alter, recreate, or style the official Sia logo.
* Do not imply any official endorsement or partnership unless you have prior written permission from the Sia Foundation.
### Branding Your Own Project
You may **not** use the name **“Sia”** or the official logo in your project’s name, branding, or marketing in a way that could cause confusion or suggest affiliation.
* Develop your own distinct name, logo, and branding.
* Avoid names that are similar to “Sia” or that incorporate it as part of the name.
* Sia's trademark name is pronounced *"sigh-uh,"* not *"see-ya."*
* Do not use the name **"Sia"** in your project without explicit written approval from the Sia Foundation.
#### Built on Sia Assets
If you would like to showcase your project's integration with Sia, you can add any one of the following `Built on Sia` assets to your project.
| Color | Primary Version | Text Only | Type |
| :-------: | :---------------------------------------: | :-----------------------------------: | :--: |
| Dark |  |  | .jpg |
| Dark |  |  | .png |
| Dark |  |  | .svg |
| Dark 50% |  | N/A | .jpg |
| Dark 50% |  | N/A | .png |
| Dark 50% |  | N/A | .svg |
| Light |  |  | .png |
| Light |  |  | .svg |
| Light 50% |  | N/A | .png |
| Light 50% |  | N/A | .svg |
{% hint style="info" %}
If you have any questions about these branding guidelines, reach out via [email](mailto:hello@sia.tech) or [Discord](https://sia.tech/discord).
{% endhint %}
---
# 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.sia.tech/miscellaneous/sia-brand-guidelines.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.