Sandbox quota

Sandbox API keys include a fixed number of calls you can make while testing. Each successful request uses one call from that allowance. Development and production keys do not use this quota—they rely on credits and spending limits instead.

How it works

When you send a request with a sandbox key, the API checks that you still have calls remaining before it runs your endpoint. If you do, one call is counted against your key's allowance for that request.

If the API returns a successful response (status 2xx or 3xx), that call stays used. If the request fails with a client or server error (4xx or 5xx), the call is returned to your allowance so you are not charged for requests that did not complete successfully.

This applies to all SDK routes when you use a sandbox key—not only run-models.

When you run out of calls

Once your allowance reaches zero, further requests are rejected with 402 Payment Required and a body like:

JSON
{
  "error": "SANDBOX_LIMIT_EXCEEDED",
  "message": "Sandbox API call quota exhausted for this key.",
  "sandboxLimit": 0,
  "environment": "sandbox"
}
402
SANDBOX_LIMIT_EXCEEDED — this sandbox key has no calls left. Create another sandbox key in the developer portal, or switch to a development or production key when you are ready to move beyond trial usage.