# 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="https://3071851461-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M4Nnmtk9_gFGWOddsf6%2Fuploads%2Fo0pBqY29LbeMOkiXG6Nd%2Fdb.webp?alt=media&#x26;token=6c370665-064a-4974-9497-b6b3a182c74b" alt=""><figcaption></figcaption></figure>

You can see the stats on each endpoint/scenario

<figure><img src="https://3071851461-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M4Nnmtk9_gFGWOddsf6%2Fuploads%2FNPUYlytrQAdBQieiK9z9%2Fdb2.webp?alt=media&#x26;token=948c3ec1-a778-4819-91d8-87ffa5c70dc7" 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](https://readme.directual.com/web-pages/components/multistep-form#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](https://readme.directual.com/scenarios/editing-scenarios/integration-steps/http-request-step) 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="https://3071851461-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M4Nnmtk9_gFGWOddsf6%2Fuploads%2FUgN3Se7GbI63qdgTgzMv%2Fscen%20logs.webp?alt=media&#x26;token=60ccde92-d2e7-4a7a-9b8e-22686174fc41" 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="https://3071851461-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M4Nnmtk9_gFGWOddsf6%2Fuploads%2Fmyyop522dmEf2AhFj7Q5%2Fscen%20logs%202.webp?alt=media&#x26;token=f091eb1a-b1f2-4ce3-b725-ec16f5a99178" alt=""><figcaption></figcaption></figure>

* [JavaScript SDK](https://readme.directual.com/scenarios/editing-scenarios/action-steps/js-sdk-step) operations taking longer than 0.5 seconds. **Coeff** = `time / 0.5`;
* [HTTP requests](https://readme.directual.com/scenarios/editing-scenarios/integration-steps/http-request-step) running longer than 3 seconds. **Coeff** = `time / 3`;
* Operations involving heavy [context](https://readme.directual.com/scenarios/using-variables/context-variables) 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](https://readme.directual.com/scenarios/synchronic-scenarios-1) 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 %}