Usage limits
Every Kameleo plan enforces the usage limits described on this page. Both limits are aggregated per team, not per device or user.
Concurrent browser limits
Your plan limits how many profiles can run at the same time. This is tracked as two independent quotas: one for all profiles regardless of device type, and one specifically for mobile profiles.
Plan limits
The exact CB and mobile CB limits depend on your active plan. See the pricing page for a comparison of limits across plans.
Checking current usage
Current CB usage is visible in the Kameleo app's bottom-left corner, hover over it to see mobile CB usage in a tooltip. Both sync in real time across all team members. It's also available via the GetUserInfo endpoint, see the API reference for the full response schema.
API request rate limits
Your plan limits how many API requests the team can send per minute. Only the following high-impact endpoints count toward the limit:
- SearchFingerprints
- CreateProfile
- StartProfile
All other operations (e.g., stop profile, list profiles) are lightweight and do not count.
Plan limits
The exact RPM limits depend on your active plan:
Checking current usage
There is currently no endpoint that reports current RPM usage. Exceeding the limit returns HTTP 429 with rate_limit_exceeded error code on further counted calls until usage falls back under the limit; see API error handling for the full reference.