Skip to main content
The Mobbin API and MCP server use rate limiting to ensure fair usage and maintain service stability.

​
Limits

​
Exceeding the Limit

When you exceed the rate limit, the server returns:
  • HTTP status 429 Too Many Requests
  • A Retry-After header indicating how many seconds to wait before retrying

​
Best Practices

  • Respect Retry-After: When you receive a 429, wait the indicated time before retrying.
  • Use exponential backoff: If retries continue to fail, increase wait time exponentially with jitter.