> 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/engine-runtime/bundled-runtime.md).

# Verify the bundled engine

Verify the bundled Algenta compute runtime without installing, starting, or managing a separate engine process.

Algenta owns the complete compute runtime lifecycle. Hosted Algenta already runs it, the self-hosted image contains it, and the standard installer starts it with the API. SDK and MCP users connect to Algenta; they do not install Mojo, a worker package, or a separate engine service.

{% hint style="success" %}
There is no second setup step. If the deployment is healthy, the bundled runtime is already available. If it is unhealthy, repair or redeploy the Algenta installation instead of starting another process.
{% endhint %}

## Installation contract

| Deployment                                       | Runtime responsibility                                                    |
| ------------------------------------------------ | ------------------------------------------------------------------------- |
| Algenta cloud                                    | Algenta operates the runtime. Configure only your API key and base URL.   |
| Self-hosted                                      | The signed Algenta image includes the runtime and starts it with the API. |
| Python, TypeScript, Cursor, Codex, or MCP client | The client calls Algenta. No local compute service is required.           |

For a new self-hosted deployment, use the normal installer:

```bash
curl -sSL https://algenta.ai/install.sh | bash
```

The installer brings up the complete stack. It does not hand the runtime lifecycle back to the user.

## Verify the deployment

Check liveness first:

```bash
curl -sS "$ALGENTA_API_URL/v1/health"
```

Then ask the authenticated infrastructure endpoint to run its compute probe:

```bash
curl -sS "$ALGENTA_API_URL/v1/infrastructure" \
  -H "Authorization: Bearer $ALGENTA_API_KEY"
```

A healthy response has a primary node with `status: "live"` and `engine_mode: "binary"`. The endpoint executes a known payload; it does not report healthy merely because a file exists.

| Signal                                    | Meaning                                                        | Action                                                             |
| ----------------------------------------- | -------------------------------------------------------------- | ------------------------------------------------------------------ |
| `status: "live"`, `engine_mode: "binary"` | The bundled compiled runtime executed the probe.               | None.                                                              |
| `status: "error"`                         | The runtime was present but the compute probe failed.          | Inspect deployment logs and redeploy a verified Algenta image.     |
| `engine_mode: "missing"`                  | The deployment artifact does not contain the required runtime. | Replace the image or package; do not install a separate component. |

## Verify real compute

Run one deterministic simulation through the same public API your application uses:

```bash
curl -sS -X POST "$ALGENTA_API_URL/v1/simulate" \
  -H "Authorization: Bearer $ALGENTA_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"mode":"auto","scenario":{"variables":{"x":{"low":50,"high":150}},"objective":"maximize_net_value"},"runs":100,"seed":42}'
```

The response must contain computed statistics and no fallback or unavailable error. Measure warm latency only after at least one successful request; installation and process startup are cold-path work.

## Related

{% content-ref url="/pages/l0L6fUVZOMtx6UivtoX2" %}
[Engine health & verification](/engine-runtime/health.md)
{% endcontent-ref %}

{% content-ref url="/pages/tWtESdNlxR5ZqT7F3czC" %}
[Self-hosting](/deploy-and-operate/self-hosting.md)
{% endcontent-ref %}


---

# 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/engine-runtime/bundled-runtime.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.