# Daily limits for members, agents and keys

> Page: https://docs.plotwork.dev/daily-limits. Index of every page: https://docs.plotwork.dev/llms.txt

An Enterprise organisation can hold each member, each agent connection and each organisation key to fewer calls a day than the allowance every account in it has, so one busy agent or a runaway CI job cannot use up the day.

## TL;DR

| Question | Answer |
|---|---|
| Where is it? | **Daily limits inside the organisation's allowance** on the organisation's Settings tab. The owner and the admins change it. |
| Which plan? | Enterprise. On another plan the section names the plan that has it; limits set before can still be turned off. |
| What can be limited? | **Per member** (every agent one member connected, together), **per agent connection** and **per organisation key**, each off or a number of calls a day. |
| Can one be different? | Yes. An override gives one member or one key its own number, higher or lower, and wins over the default. |
| What does a refused call get? | `429 orgs.member_cap`, the plan limit's shape, with `details.scope`, `limit`, `used` and `resetsAt`. An agent gets it as data in the tool's answer. |
| Does the account's own allowance still apply? | Yes. A limit sits inside it; a call past the allowance gets `usage.daily_limit` as before. |
| When does the count start again? | At 00:00 UTC, with the daily limit. |
| Who is told? | Each owner and admin gets one email at 80 percent of a limit and one when it is reached, at most once a day each. The Usage page shows an alert row. |
| Is it audited? | `orgs.settings.caps` when the limits change, and `orgs.cap.reached` once a day for each limit reached. Both go to your SIEM on Enterprise. |

## 1. Set the limits

Open the organisation, then **Settings**, and find **Daily limits inside the organisation's allowance**. Each limit is a number field; empty is off. Beside each is the allowance, such as "of 250,000 a day", which every number is held to.

| Limit | What it counts |
|---|---|
| Per member | The calls of every agent a member connected to the organisation, through MCP and the REST API. The member's personal calls are not counted. |
| Per agent connection | The calls of one agent a member connected with a browser sign-in. The member limit still holds all their agents together. |
| Per organisation key | The calls of one key from the Keys tab, such as a CI key. |

Under **Overrides**, **Add override** picks a member, an agent connection or a key and gives it its own number. A CI key that needs more than the others is the usual case. A member's override goes when they leave the organisation; a key's when it is revoked.

Save sends the whole setting. A number over the allowance, or an override for someone who is not a member, is refused before anything changes, with what to fix.

## 2. What a refused call looks like

A call whose member, connection or key has made its limit today is refused with the plan limit's 429 and its own code:

```json
{
  "error": true,
  "errorCode": "orgs.member_cap",
  "message": "This member has made all 1000 calls a day its organisation allows. The count resets at 00:00 UTC.",
  "details": {
    "scope": "member",
    "limit": 1000,
    "used": 1000,
    "resetsAt": 1792540800000,
    "retryAfterSeconds": 3600
  }
}
```

The `Retry-After` and `RateLimit` headers say when to come back. Over MCP the same refusal is the JSON-RPC error `-32029` with `data.errorCode` set to `orgs.member_cap`, so an agent reads it as an answer and can say so. Only that member, connection or key is refused: everyone else in the organisation carries on.

## 3. Alerts and the Usage page

When a call takes a limit to 80 percent, each owner and admin gets an email naming who, how many of how many, and when the count starts again. A second email goes when the limit is reached. Each is sent once a day at most.

The organisation's **Usage** page has a **Daily limits today** card:

| Part | What it shows |
|---|---|
| Alert rows | One line for each limit at 80 percent or more, such as "lin@acme.example reached 900 of 1,000 today". |
| Rows | Each member, agent connection and key with a limit or calls today, "used / limit" with a thin bar. |
| The breakdown | The **By member** and **By agent or key** tables gain a **Today** column with the same figure and bar. |

The owner, the admins and the people who may read the call history see everyone. Any other member sees their own limit and how much of it is used.

## 4. What it costs

Nothing more is written for a call with a limit than without one. The count a limit reads is the one the daily limit already keeps, one row per account, day and key, and the limit is checked in the same statement that adds the call. An alert is sent only by the call that crosses 80 percent or the limit, from the count that statement returned.

## See also

| Page | Why |
|---|---|
| [Organisations](https://docs.plotwork.dev/organisations.md) | Members, keys, connected agents and the Usage page. |
| [Plans and billing](https://docs.plotwork.dev/plans-and-billing.md) | The daily allowance each plan has. |
| [Audit log](https://docs.plotwork.dev/audit-log.md) | `orgs.settings.caps` and `orgs.cap.reached`. |
| [Send audit events and drift to your tools](https://docs.plotwork.dev/siem-delivery.md) | Where the audit events go on Enterprise. |
| [Connecting an agent](https://docs.plotwork.dev/mcp/connect.md) | How an agent connects to an organisation. |