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

# Getting Started

- [Install](https://docs.algenta.ai/getting-started/install.md): Install the published Algenta clients or run the self-hosted engine. Pick your path, install in one command where a public package exists, and verify it.
- [Quickstart](https://docs.algenta.ai/getting-started/quickstart.md): Run Algenta end to end in minutes — install the integrated service, mint an API key, and make your first decision call.
- [Try it without a key](https://docs.algenta.ai/getting-started/playground.md): Try the Algenta engine with a single POST /v1/playground call — no sign-up and no API key. Run a decision, optimization, simulation, or forecast in one request.
- [Core concepts](https://docs.algenta.ai/getting-started/concepts.md): The core Algenta model — one integrated engine, governed data, deterministic decisions, capability routing, and explicit deployment boundaries.
- [Authentication & API keys](https://docs.algenta.ai/getting-started/authentication.md): Create and use Algenta API keys. Mint a key, send it as a Bearer token, and confirm an authenticated request succeeds.


---

# 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.algenta.ai/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.