> For the complete documentation index, see [llms.txt](https://mysmax.gitbook.io/mysmax/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://mysmax.gitbook.io/mysmax/how-do-super-services-work.md).

# How Do Super Services Work?

#### ① Defining a Super Service

Upper-level JOI hubs combine multiple individual device-level services into one advanced service—called a Super Service. For example, a single Super Service could manage lighting, security, and climate across an entire building, orchestrating these services seamlessly.

#### ② Controlled Access (Public vs. Private)

Super Services have strict access controls. Only services explicitly defined as public are accessible by lower-level hubs. This protects privacy and ensures sensitive data remains secure. Private Super Services remain hidden and are only accessible by the hub that created them.

#### ③ Requesting and Executing Super Services

Lower-level hubs can request available public Super Services whenever needed. JOI manages these requests intelligently, triggering the correct IoT devices or robots automatically—no manual intervention required. Users simply define the task; JOI takes care of the complexity.


---

# 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://mysmax.gitbook.io/mysmax/how-do-super-services-work.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.