Rate Limits
Truedy API uses configurable per-minute rate limits to ensure fair usage and prevent abuse. Limits are applied per organization (per API key).Current behavior
- Per minute: The API allows a fixed number of requests per minute per organization. The default is 100 requests per minute and can be configured per deployment (
RATE_LIMIT_PER_MINUTE). There are no per-hour or per-day tiers in the current implementation. - No rate limit headers: Responses do not currently include
X-RateLimit-*orRetry-Afterheaders. Use the 429 response body to know the limit and when the window resets. - Rate limiting can be disabled by the deployment (e.g.
RATE_LIMIT_ENABLED=false). When disabled, no 429s are returned for over-limit requests.
Rate limit exceeded (429)
When the per-minute limit is exceeded, you receive a 429 Too Many Requests response with the same envelope as other API errors:- details.limit: The per-minute limit that was applied.
- details.reset_at: ISO 8601 timestamp when the current window resets (approximately the start of the next minute).
- meta.request_id: Use when contacting support.
- meta.ts: Server time when the response was generated.
reset_at to wait before retrying. Implement exponential backoff when you receive 429s to avoid tight retry loops.
Best practices
Use reset_at
Wait until after
error.details.reset_at before retrying when you get 429Implement backoff
Use exponential backoff when rate limited
Request higher limits
Contact support@truedy.ai for higher limits if needed
Use multiple keys
Distribute load across multiple API keys (each has its own limit)
Handling rate limits
Exponential backoff
Usage tracking
API requests are logged and tracked. Usage can be viewed in the dashboard where available. For higher limits or custom needs, contact support@truedy.ai.Increasing limits
- Contact support: Email support@truedy.ai
- Specify requirements: Provide your use case and expected volume
- Upgrade plan: Higher-tier plans may include higher limits

