Skip to main content
Adaline enforces rate limits to ensure fair usage and platform stability. Limits apply per workspace.

Default Limits

These are default limits. If you need higher limits for your use case, contact support@adaline.ai.

Handling Rate Limits

When you exceed the rate limit, the API returns a 429 Too Many Requests response:

Payload Limits

Requests exceeding payload limits receive a 413 Payload Too Large response.

SDK Retry Behavior

TypeScript SDK (@adaline/client)
  • The Monitor class buffers logs and flushes in batches
  • Failed flushes are automatically retried with exponential backoff
  • Configure flushInterval and maxBufferSize to control batching
Gateway SDK (@adaline/gateway)
  • Built-in configurable queue with automatic retry
  • Exponential backoff on transient failures (429, 5xx)
  • Pluggable queue backend for custom retry logic

Best Practices

Use the SDK’s built-in batching (Monitor class) rather than sending individual API calls for each trace or span. This significantly reduces the number of requests.
Use initLatestDeployment() with a refreshInterval to cache prompt deployments locally and reduce deployment fetch requests.
If making direct API calls, implement exponential backoff when you receive 429 responses. Start with a 1-second delay and double it on each retry, up to a maximum of 60 seconds.
Review plan limits in your workspace settings and contact support if your application needs higher limits.