Skip to main content

Rate limiting

The Tella public API and MCP server implement rate limiting to ensure fair usage and protect the service for all users.

Current limits

All API keys and external MCP connections used by the same user in a workspace share one 100-request-per-minute limit.

Rate limit headers

Every REST API response includes headers with rate limit information:

Example response headers

Handling rate limits

REST API requests

When a REST API request exceeds the limit, you’ll receive a 429 status code:

MCP tool calls

When an MCP tool call exceeds the limit, the server returns a tool error instead of an HTTP 429 response. The result includes the number of seconds to wait and marks the error as retryable:
Wait for the duration in the first text content block before retrying the tool call.

Best practices

Monitor the X-RateLimit-Remaining header and slow down before hitting the limit.
When you receive a REST API 429 or a retryable MCP error, wait before retrying with increasing delays:
The X-RateLimit-Reset header tells you exactly when your limit resets:
Instead of making many small requests, use pagination efficiently:

Rate limit scope

Rate limits are calculated per user within an organization:
  • All API keys and external MCP connections used by the same user share the same 100 requests per minute limit
  • Different users in the same organization have independent limits
  • REST API requests and MCP tool calls draw from the same limit

Need higher limits?

If your use case requires higher rate limits, please contact us to discuss your needs.