For the complete documentation index, see llms.txt. This page is also available as Markdown.

Rate limits

KrosAI applies rate limits to ensure fair usage and platform stability.

Limits by Plan

Plan
Requests/Second
Requests/Day
Concurrent Calls

Free

10

1,000

1

Pro

50

50,000

10

Business

200

500,000

50

Enterprise

Custom

Custom

Unlimited

Rate Limit Headers

Every API response includes rate limit information:

X-RateLimit-Limit: 50
X-RateLimit-Remaining: 45
X-RateLimit-Reset: 1704891600
Header
Description

X-RateLimit-Limit

Maximum requests per second

X-RateLimit-Remaining

Requests remaining in current window

X-RateLimit-Reset

Unix timestamp when limit resets

Rate Limit Response

When you exceed the rate limit, you'll receive a 429 Too Many Requests response:

The Retry-After header indicates seconds to wait:

Endpoint-Specific Limits

Some endpoints have additional limits:

Endpoint
Limit
Notes

POST /outbound-calls

10/sec

Per organization

POST /phone-numbers

5/sec

KYC required

GET /calls

100/sec

Pagination recommended

POST /webhooks

10/sec

Per organization

Concurrent Call Limits

Outbound calls have concurrency limits:

Plan
Concurrent Outbound

Free

1

Pro

10

Business

50

Enterprise

Unlimited

Exceeding the concurrent call limit returns:

Best Practices

Implement Exponential Backoff

Use Batch Operations

Cache Responses

Monitor Usage

Queue Outbound Calls

Requesting Higher Limits

Need higher limits? Contact us:

  • Pro/Business: Upgrade to a higher plan

  • Enterprise: Custom limits available

Email support@krosai.com with:

1

Organization ID

Provide your organization ID.

2

Current usage patterns

Describe your current usage patterns (traffic, peak times, typical requests).

3

Required limits

Specify the limits you need (requests/sec, requests/day, concurrency).

4

Use case description

Explain the use case and why higher limits are required.

Next Steps

  • Error Codes - Handle errors properly

  • SDKs - Use official SDKs with built-in retry logic