# Rate Limits

### Sandbox Limits

Our staging environment experiences higher resource consumption compared to production. This is primarily due to extensive testing conducted by our customers before going live, which is why the staging environment has a request limit of 150 requests.

The resource usage is calculated as follows: each request to the rate endpoint is considered equivalent to 10 requests. This is because the rate endpoint queries multiple services simultaneously—typically over 45. Each of these services has unique features, attributes, and resource requirements, contributing to the increased resource consumption.

In practical terms, when you call the `allprice` endpoint to retrieve shipping rates, each call counts as 10 requests due to the extensive resources required to process and return the shipping rates for multiple services.  However, the single-rate endpoint is calculated as 1 per request.

{% hint style="info" %}
These rate limits only apply to our rates endpoints, [Get-Shipment-Rates](/api-references/get-shipment-rates.md) & [Get-Single-Rate](/api-references/get-single-rate.md).
{% endhint %}

### Production Limits

In contrast, the production environment has a daily cap of 100k requests, which is refreshed daily. Similarly, the 150-request cap in staging is also refreshed daily. This setup ensures that both environments are managed effectively while accommodating the varying needs of testing and live operations.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://developer.goshiip.com/getting-started/rate-limits.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.