---
title: "act: capacity"
description: "Sets how many new leads one user can take in a period to The answer gives the new capacity, with how many the user holds and when it refills"
section: reference
address: /reference/act/capacity
contract: 0476e35e6e275db5
---

# act: capacity

Sets how many new leads one user can take in a period to The answer gives the new capacity, with how many the user holds and when it refills

[figure: The caller sends CapacityInput to /v1/act/capacity. The platform returns a card whose body is Capacity.]

<span class="op-method">POST</span><span class="op-path">/v1/act/capacity</span>

Set capacity. The call needs the brand rung under a token with the act grant, and it is served by the platform.

The route takes [CapacityInput](/concepts/capacityinput) and returns a card whose body is [Capacity](/concepts/capacity).



## Request body
The request body is [CapacityInput](/concepts/capacityinput).



| field | type | required | note |
|---|---|---|---|
| `user` | `id` | yes |  |
| `per_period` | `count` | yes |  |
| `period` | `duration` | yes |  |



## Response
The route returns a card whose body is [Capacity](/concepts/capacity). Every card ends with a foot that states the basis of each number, the scope of the call, and the time when the facts were true.

## Headers


| header | required | meaning |
|---|---|---|
| `Scale-Scope` | yes | the scope the call runs in: tenant/<id>, then /brand/<id>, then /strategy/<id> |
| `Scale-As-True-On` | no | the date the facts must have been true on; defaults to now |
| `Scale-As-Known-On` | no | the date the facts must have been known on; defaults to now |
| `Scale-Key` | no | for a change, the key made from the input; a repeat under the same key returns the unit held and writes nothing |



A caller needs the brand rung and a token with the act grant. The platform serves this route.

## Example
The example sends the smallest body that CapacityInput allows. The build validates it against the schema of CapacityInput.

<details class="wire"><summary>Example</summary>





```sh
curl -X POST https://api.scaleintelligence.co/v1/act/capacity \
  -H "Scale-Key: $SCALE_KEY" -H "Scale-Scope: tenant/<id>" \
  -H "content-type: application/json" \
  -d '{ "user": "…", "per_period": 0, "period": "…" }'
```




```typescript
import { client } from "@scale/sdk";
const answer = await client.act.capacity({
    "user": "…",
    "per_period": 0,
    "period": "…"
  });
// answer.body is a Capacity. answer.foot holds the basis, the scope and the time.
```




```python
import requests
answer = requests.post("https://api.scaleintelligence.co/v1/act/capacity",
    headers={"Scale-Key": KEY, "Scale-Scope": "tenant/<id>"},
    json={
      "user": "…",
      "per_period": 0,
      "period": "…"
    }).json()
```




```rust
let answer: Card = client.post("https://api.scaleintelligence.co/v1/act/capacity")
    .header("Scale-Key", key).header("Scale-Scope", "tenant/<id>")
    .json(&CapacityInput { /* the fields of the page */ }).send().await?.json().await?;
```




</details>

## MCP tool
The MCP tool `si.act.capacity` takes the same input and returns the same card. The tool changes data and needs a grant. An MCP host that renders cards draws this card from `ui://scale-intelligence/cards/Capacity`. The [tool's page](/reference/tools/si-act-capacity) describes it.
