> For the complete documentation index, see [llms.txt](https://readme.directual.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://readme.directual.com/pricing-and-billing/how-we-count-requests-and-operations.md).

# How we count requests and operations

### App Dashboard

You can see the detailed statistics on the consumption on the app's dashboard:

<figure><img src="/files/7oikCT8bbNyBYm9eKrsL" alt=""><figcaption></figcaption></figure>

You can see the stats on each endpoint/scenario

<figure><img src="/files/S4hWDvQ8Uni9reP8Hid1" alt=""><figcaption></figcaption></figure>

### GET-requests

Each time when your API-endpoint is requested for reading, the counter adds 1 request.

{% hint style="warning" %}
If you specify parameter `pageSize = N` (by default N = 30), the counter adds  N/30 requests. For example, if you request 300 objects via a GET-request, you'll spend 10 requests from the limit.
{% endhint %}

Note that each field [render for link/arrayLink](/web-pages/components/multistep-form.md#setting-up-dynamic-inputs) consumes GET-requests.

### POST-requests

Each time when your API-endpoint or Webhook is requested for writing, the counter adds 1 request.

### HTTP-requests

Each time when you call third party API from scenarios using [HTTP-request step](/scenarios/editing-scenarios/integration-steps/http-request-step.md) or plugin, the counter adds 1 request.

### Regular processing operations

Each object processed (each scenario logs line) in a scenario step adds 1 to the counter.&#x20;

<figure><img src="/files/XK15SiJyHd2wmgBpAu4s" alt=""><figcaption></figcaption></figure>

There are also **coefficients** for processing steps based on their complexity and resource consumption. Every processing-intense step is marked with the 🔥emoji and the coefficient numbers.&#x20;

<figure><img src="/files/K4UlRhpJ0EMgbszukGOI" alt=""><figcaption></figcaption></figure>

* [JavaScript SDK](/scenarios/editing-scenarios/action-steps/js-sdk-step.md) operations taking longer than 0.5 seconds. **Coeff** = `time / 0.5`;
* [HTTP requests](/scenarios/editing-scenarios/integration-steps/http-request-step.md) running longer than 3 seconds. **Coeff** = `time / 3`;
* Operations involving heavy [context](/scenarios/using-variables/context-variables.md) greater than 1kb. **Coeff** = `Context size / 1kb;`
* Operations involving heavy object size greater than 64kb. **Coeff** = `Object size / 64kb.`

### Sync processing operations

Each object processed in a [sync scenario](/scenarios/synchronic-scenarios-1.md) step adds 1 to the counter.

The sync scenario processing is a resource-heavy operation. Thus the following multiplier was introduced:

* Synchronous scripts (the whole scenario peocessing time) that run over 5 seconds. Coeff = `time / 5`.

{% hint style="info" %}
**Example**: The scenario runs synchronically 12 seconds. The number of steps passed by the object is 10. The final operations from the limit = 24
{% endhint %}