Scalekit · Rate Limits

Scalekit Rate Limits

Scalekit enforces per-environment API rate limits on its management and auth REST endpoints, returning HTTP 429 when a client exceeds its allowance. Usage allowances (M2M tokens, tool calls, MAU/MAO, connections) also act as plan-level quotas. Specific per-endpoint request-per-second / per-minute values are not published in detail and are not reconciled in this artifact.

Scalekit Rate Limits is the machine-readable rate-limit profile for Scalekit on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 6 rate-limit definitions, measuring requests, tokens, users, and organizations.

The profile also includes 3 backoff/retry policies defined and response codes documented for throttled.

Tagged areas include Authentication, SSO, SCIM, Identity, and B2B SaaS.

6 Limits Throttle: 429
AuthenticationSSOSCIMIdentityB2B SaaSAgent AuthRate LimitingQuotasThrottling

Limits

Management API Requests environment
requests
see provider documentation
Per-environment request rate on organization/connection/directory/membership endpoints.
Token Endpoint (client credentials) client
requests
see provider documentation
OAuth 2.0 token issuance at /oauth/token; cache and reuse access tokens until expiry.
M2M Tokens environment
tokens
10000 free per month (then $5 per 1,000)
Plan-level quota for machine-to-machine token issuance.
Agent Tool Calls account
requests
5,000/month (Free, hard stop); 200,000/month (Growth)
Tool execution via /api/v1/execute_tool counts against the tool-call allowance.
Monthly Active Users (MAU) environment
users
1,000,000 free per month
Plan-level quota; usage beyond is billed per MAU.
Monthly Active Organizations (MAO) environment
organizations
100 free per month
Plan-level quota; usage beyond is billed per MAO.

Policies

Tiered Limits
Allowances raise as accounts move from Free to Growth and via Enterprise agreements.
Token Reuse
Obtain a client-credentials access token and reuse it until expiry rather than minting one per request.
Backoff Strategy
Clients should implement exponential backoff with jitter and honor Retry-After on 429 responses.

Sources