Skip to main content

​
Usage and limits

API keys and account MCP connections share one allowance per effective billing account. A team member uses the billing account resolved for that membership. Creating another key or connection does not increase the allowance.

​
How calls are counted

  • Each successful data action counts once through REST or MCP, including downloads. action_request_get, usage_get, projects_status, and GET /v1/translate/{projectId}/status are exempt from the monthly allowance and still enforce authentication and rate limits.
  • Failed actions, action discovery, and MCP protocol initialization do not consume the monthly allowance.
  • Monthly allowances reset at the start of each UTC calendar month. In-progress calls may appear as pending usage.
  • No monthly ceiling still includes the plan rate limit, media credits, duration and file limits, and generation concurrency limits.
  • Additional network protections can limit excessive bursts across credentials.

​
Handle limits

Read your current usage in Integrations or through the usage action. On a rate-limit response, wait and retry with backoff. When the monthly allowance is exhausted, wait for the reset or change plan. Use job status and webhook notifications to avoid unnecessary polling.