Call units and limits
Your API usage is measured in call units. Think of call units like a centralized token balance. Depending on your needs, we can set call uinits by minute, hour, day, week, or month.
Your account is allocated a specific budget (See Account settings).
As your application makes API calls, units are automatically deducted from your balance based on the weight of the operation. The exact amount of consumed call units depends on the function and limit parameter and can be seen in the API Explorer.
Maximum results per response
For the Autosuggest API and Documents API, a limit is applied to the maximum results per response. The results limit determines the maximum number of items that a single API response can contain.
There is a default limit set to 10 for the Autosuggest function and 30 for the Documents function.
The number of call units consumed by your request is determined directly by the limit parameter you set (for example, 2 units for a 30-document limit versus 4 units for a 60-document limit), regardless of how many actual results are found.
We currently do not offer paging. However, if you want to retrieve a larger data set for your query without exceeding the result limit, you may either use thedate_fromanddate_toparameters in the Documents function to filter results within a specific timeframe or continuously monitor the response of a given query over time.
Monitor remaining units
You can monitor your usage and remaining call units directly in the API Explorer, and in the response header. After running test queries, you’ll see:
- Your assigned call units (based on your contract).
- The remaining call units are available for the given period.
If your limit is exceeded, the server will respond with status code 429 (too many requests).
Requests in the MCP Server
MCP-based interactions operate just like direct API calls, with one exception: the scout-panel function returns a URL instead of HTML. Call units are only deducted when this URL is actually opened.
