Rate limits & spend caps
The guardrails that keep Syncanix usage predictable: platform rate limits that protect stability, and spend caps you configure to stay within budget.
Two kinds of guardrail keep usage and cost under control: platform rate limits that protect the service for everyone, and spend caps you set yourself.
Rate limits
Syncanix applies fair-use rate limits so that no single source can overwhelm the service. They’re tuned to be invisible in normal use and only kick in against bursts well beyond real traffic.
- Requests are rate-limited per source; bursts beyond the limit get a “429 Too Many Requests” response and should be retried shortly after.
- Oversized request bodies are rejected with a “413” response, so an unusually large payload can’t degrade the service.
- MCP server traffic is additionally limited per workspace, so automated clients stay within a fair share.
Spend caps
Spend caps let you set a ceiling on model spend so a surprise can’t run away with your budget. You configure them in the dashboard.
- Set a maximum monthly spend for the workspace.
- Choose alert thresholds — for example at 50% and 90% — to be warned before you reach the ceiling.
- Caps can apply to the whole workspace, or to a narrower scope such as a single user or conversation.
Which limit is which
Three limits work together: your plan’s MAEU allowance decides your bill, spend caps protect your budget from surprises, and platform rate limits keep the service stable. Reaching one doesn’t imply the others.