Usage, pricing & limits

Rate limiting

By default the number of requests is limited to 300 requests per minute per organization. Contact us if you need a higher limit.

Credits

API usage is measured in credits. Each successful request consumes a number of credits determined by a multiplier defined per endpoint.

• Failed requests (HTTP 4xx / 5xx) are not billed.

• Multipliers can change over time. The credit cost applied is always the one active at the time of the request — your billing history is never retroactively modified.

• When a pricing change is scheduled, a badge on the relevant endpoint page shows the future multiplier and its effective date.

Tracking your consumption

Call GET /v1/credits-usage to retrieve the total credit consumption over a period (the current month by default), along with the effective start/end dates and organization/headquarter scope used for the calculation. This endpoint lets you filter by any date range or a different organization/headquarter you administer.

• Values can be fractional (e.g. 12.5), matching the decimal multipliers applied per endpoint.

• Only successful requests (HTTP < 400) are billed, so the reported usage reflects billed usage only.

Reading the pricing badges

Each endpoint page displays one or two badges next to the page title:

Badge Meaning
x1.0 Current multiplier active for this endpoint
↗ DD/MM/YYYY x2.0 A price change is scheduled on that date

A ? badge means the endpoint is not yet tracked in the pricing system.

Billing period

Contact us for details on your current consumption or to request a usage report.