> For the complete documentation index, see [llms.txt](https://guide.strikepack.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guide.strikepack.com/horizon-es/trademark-notice.md).

# Aviso de marca registrada

Collective Minds, STRIKEPACK y STRIKEPACK HORIZON son marcas comerciales de Collective Minds Gaming Co. LTD. PS5, PlayStation y DualSense son marcas comerciales registradas de Sony Interactive Entertainment Inc. Microsoft, Xbox, Xbox One y Xbox Series X|S son marcas comerciales del grupo de empresas Microsoft. Android, Google Play y el logotipo de Google Play son marcas comerciales de Google LLC. Apple, el logotipo de Apple, App Store e iPhone son marcas comerciales de Apple Inc., registradas en EE. UU. y otros países y regiones. iOS es una marca comercial o marca comercial registrada de Cisco en EE. UU. y otros países y se utiliza bajo licencia. Bluetooth es una marca comercial registrada de Bluetooth SIG, Inc. Este producto de Collective Minds no está avalado, fabricado ni distribuido por Sony Interactive Entertainment Inc., el grupo de empresas Microsoft, Apple Inc., Cisco Systems, Inc., Google LLC o Bluetooth SIG, Inc. Copyright © 2026 Collective Minds Gaming Co. LTD. Todos los derechos reservados.


---

# 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://guide.strikepack.com/horizon-es/trademark-notice.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.
