> For the complete documentation index, see [llms.txt](https://developer.emporix.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.emporix.io/user-guides/getting-started.md).

# Getting Started

- [General Concepts of Emporix](https://developer.emporix.io/user-guides/getting-started/generalconcepts.md): Get an overview of Emporix's main characteristics and features.
- [Creating your first tenant](https://developer.emporix.io/user-guides/getting-started/creating-a-tenant.md): Create your first tenant.
- [Developer Portal](https://developer.emporix.io/user-guides/getting-started/developer-portal.md): Developer Portal is a starting place for setting up and configuring your tenant.
- [Manage Users](https://developer.emporix.io/user-guides/getting-started/developer-portal/manage-users.md): Grant relevant access rights to your team.
- [Manage API Keys](https://developer.emporix.io/user-guides/getting-started/developer-portal/manage-apikeys.md): API keys enable you to work with Emporix API with different scopes and perspectives.
- [Tenant List](https://developer.emporix.io/user-guides/getting-started/developer-portal/tenant-list.md): View and manage your tenants.
- [My Account](https://developer.emporix.io/user-guides/getting-started/developer-portal/myaccount.md)
- [Manage Showcase and Sample Data](https://developer.emporix.io/user-guides/getting-started/developer-portal/demo-data.md): Use sample data and showcase storefront to test your setup.


---

# 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://developer.emporix.io/user-guides/getting-started.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.