Rate Limits
How rate limiting and usage limits work across the Syntext API.
Syntext applies two kinds of limits: request rate limits (short-window, per-client) and usage limits (monthly, per-organization, based on your plan).
Request Rate Limits
When you exceed a rate limit, the API returns 429:
Wait retryAfterSeconds before retrying.
AI Assistant Visitor Limits
The public chat endpoint is rate-limited per visitor to protect your AI query quota from abuse. The limit is a per-project setting (aiRateLimit); it isn't editable in the dashboard. When a visitor exceeds it, the widget shows a cooldown message.
Agent mode action limits
The public agent mode actions — report a docs gap, share a conversation, draft and send to support — have fixed limits, counted per visitor, per client IP and per project:
| Action | Per visitor | Per client IP | Per project | Per organization |
|---|---|---|---|---|
| Report a docs gap | 5 an hour | 20 an hour | 200 an hour | — |
| Share a conversation | 20 an hour | 60 an hour | 500 an hour | — |
| Draft a support handoff | 5 an hour | 15 an hour | 100 an hour | — |
| Send to support | 3 a day | 10 a day | 50 a day | 200 a day |
| Run an API request | 20 per 10 minutes | 60 per 10 minutes | 1000 an hour | 2000 an hour |
| Gated pages notice check | 30 an hour | 60 an hour | 2000 an hour, and 10,000 a day | — |
/_chat/...). Requests made straight to the API are limited per visitor and per project only.403), and every limit is enforced; if the limits can't be checked, the run is refused. On top of the hourly limits, at most 5 runs per project and 20 per organization are in flight at once. There is no global run budget.429.Over a limit, the response is 429 with a Retry-After header:
Editor limits
The web editor's two most expensive requests are limited per user, per project, per minute:
| Request | Limit |
|---|---|
| Editor chat — messages to the editor's Assistant | 20 a minute |
Editor symbols — the @stx symbol index | 30 a minute |
Over a limit, the response is 429 with the wait in details.retryAfterSeconds:
Account limits
| Request | Limit | Over the limit |
|---|---|---|
| Change Email | 5 an hour per account | 429 rate_limited, Retry-After: 3600 |
| Unsubscribe and Get Unsubscribe Link | 30 a minute per client IP, across both | 429 rate_limited |
Monthly Usage Limits
Plan-based limits are enforced per organization and reset monthly:
| Metered resource | Applies to |
|---|---|
| Builds | Trigger Build, Deploy, Roll Back, git-push builds, PR previews |
| AI queries | AI assistant questions across all your doc sites |
When a limit is reached the API returns 402 with code USAGE_LIMIT_EXCEEDED (earlier releases returned 403, so match on the code). Creating a project beyond the plan's projects limit returns the same error:
Current usage is visible in the dashboard under Billing in the account sidebar.
Checking current usage
Get Usage returns this month's usage next to the organization's limits.
Best Practices
chat/config — widget configuration rarely changes.retryAfterSeconds — retrying earlier only extends the cooldown.Analytics beacon endpoints (/analytics/pageview, /analytics/search, /analytics/chat) are designed for high-volume traffic from doc sites and return 202 immediately.