> 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/deploy-and-operate/billing.md).

# Usage & limits

Inspect unlimited execution policy and local governance records. Algenta is licensed per device, never per decision.

Algenta is **licensed per device** — a flat license with unlimited decisions and **no usage-based billing**. There is no per-simulation metering, no compute overage, and no surprise invoice. For the editions (Community, Pro, Team, Enterprise), what a license grants, and how to install and verify one offline, see [Licensing & editions](/deploy-and-operate/licensing.md).

This page covers the runtime's **governance and observability** endpoints: how to inspect the unlimited execution policy and query customer-owned activity records for audit. These records stay inside a self-hosted deployment; Algenta execution counts are not sent to Algenta or Stripe. Every command and endpoint below is real and runs against a hosted or self-hosted deployment.

{% hint style="info" %}
Looking for pricing, editions, or how to license a commercial deployment? That lives in [Licensing & editions](/deploy-and-operate/licensing.md). This page is purely operational — inspecting limits and usage.
{% endhint %}

## Inspect the effective policy

`GET /v1/limits` returns execution policy and request-shape safety bounds. `0` means unlimited for monthly execution, plan request rate, and concurrent async jobs.

{% tabs %}
{% tab title="cURL" %}

```bash
curl -s https://api.algenta.ai/v1/limits \
  -H "Authorization: Bearer $ALGENTA_API_KEY"
```

{% endtab %}

{% tab title="CLI" %}

```bash
de account limits
```

{% endtab %}

{% tab title="Response" %}

```json
{
  "plan": "algenta_team",
  "max_simulations_per_month": 0,
  "max_runs_per_simulation": 1000000,
  "max_batch_items": 100,
  "rate_limit_per_minute": 0,
  "async_jobs_enabled": true,
  "webhooks_enabled": true,
  "concurrent_jobs": 0,
  "storage_gb": 0,
  "llm_spend_cap_usd_month": 0
}
```

{% endtab %}
{% endtabs %}

## Observe your usage

`GET /v1/usage` reports local activity for audit and capacity planning. On a self-hosted deployment these records remain in your database. They are not an Algenta usage bill or vendor telemetry: decisions are unlimited and nothing here is invoiced per call.

{% tabs %}
{% tab title="cURL" %}

```bash
curl -s https://api.algenta.ai/v1/usage \
  -H "Authorization: Bearer $ALGENTA_API_KEY"
```

{% endtab %}

{% tab title="CLI" %}

```bash
de account usage
```

{% endtab %}

{% tab title="Response" %}

```json
{
  "billing_period": "2026-07",
  "simulations_run": 4210,
  "api_calls": 4210,
  "storage_bytes_used": 0,
  "storage_gb_limit": 10
}
```

{% endtab %}
{% endtabs %}

{% hint style="success" %}
Add `--format json` to any `de account` command for raw output suitable for scripting.
{% endhint %}

## Governance, not billing

Keys, local activity records, and audit are **runtime primitives** — the same controls apply to humans, SDKs, and AI agents because every call crosses one governed boundary. They are decoupled from how you pay: one flat license per device, with unlimited decisions.

* **Per-tenant provider keys (BYOK)** — bring your own model keys, encrypted at rest. See [Bring your own key](/guides/byok.md).
* **Teams, roles & audit** — scope who can do what and keep an append-only trail. See [Teams, roles & audit logs](/deploy-and-operate/teams-rbac.md).
* **Egress & privacy** — inspect and tighten what a self-hosted engine sends outbound. See [Egress policy & privacy reports](/deploy-and-operate/privacy-egress.md).

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Licensing &#x26; editions</strong></td><td>How Algenta is licensed per device, the editions, and offline verification.</td><td><a href="/deploy-and-operate/licensing.md">Licensing &amp; editions</a></td></tr><tr><td><strong>Self-host the engine</strong></td><td>Run Algenta on your own infrastructure.</td><td><a href="/deploy-and-operate/self-hosting.md">Self-hosting</a></td></tr><tr><td><strong>Teams, roles &#x26; audit</strong></td><td>Govern access with roles and an audit trail.</td><td><a href="/deploy-and-operate/teams-rbac.md">Teams &amp; roles (RBAC)</a></td></tr></tbody></table>


---

# 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/deploy-and-operate/billing.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.