> 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/http-api/rate-limits.md).

# Execution policy & safety limits

Unlimited Algenta execution, request safety bounds, licensed worker capacity, and configurable abuse controls.

Algenta is licensed per device at a flat price. **Decisions and executions are unlimited on every edition**: there is no monthly quota, per-decision charge, overage rate, or edition-specific request meter. The self-hosted engine does not send execution counts to Algenta or Stripe.

The runtime still records customer-owned audit events inside the deployment. Those local records are governance data, not vendor telemetry or a billing meter.

`GET /v1/limits` reports the effective execution policy. A value of `0` for monthly execution, plan request rate, or concurrent jobs means unlimited.

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

## Edition contract

All editions have unlimited decisions, no edition request meter, async execution, and no plan-level concurrent-job quota. The only tiered execution capacity is workers per licensed device:

| Edition    | Decisions | Workers/device |
| ---------- | --------- | -------------: |
| Community  | unlimited |              1 |
| Pro        | unlimited |              5 |
| Team       | unlimited |             20 |
| Enterprise | unlimited |     negotiated |

## Request-shape validation

The current API schema accepts up to 1,000,000 simulation runs in one request and up to 100 items in one batch. These uniform per-payload validation bounds prevent a single request from monopolizing memory; they do not cap total calls, decisions, or monthly execution. Split larger work across calls or async jobs.

Workers/device is licensed capacity, not a rate limit. The bundled runtime enforces the signed-license value locally. See [Licensing & editions](/deploy-and-operate/licensing.md).

## Security abuse controls

Authentication and key-management endpoints retain narrow security controls. These are not decision or execution quotas, and self-hosted operators can configure them:

| Operation                      | Scope             |   Default |
| ------------------------------ | ----------------- | --------: |
| Create an API key              | organization      | 10/minute |
| Login                          | email + client IP | 10/minute |
| Signup                         | client IP         |  3/minute |
| Create organizations by signup | email             |     2/day |

When one of these security controls is exceeded, the response is HTTP `429` with its operation-specific error code and a `Retry-After` header. This does not consume or reduce an edition execution allowance; no such allowance exists.

Provider APIs and customer infrastructure can still apply their own capacity or rate controls. Algenta surfaces those external errors explicitly rather than relabeling them as an Algenta plan quota.

## Related

{% content-ref url="/pages/LtqjHw8bwZ1rd0qQ3xgl" %}
[Usage & limits](/deploy-and-operate/billing.md)
{% endcontent-ref %}

{% content-ref url="/pages/wwdJd5GQCs0WvhNMBjj7" %}
[Error codes](/http-api/errors.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/http-api/rate-limits.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.