Overages & Limits

Plan limits are enforced with no hidden margin or tolerance:

• No safety buffer. The enforced limit is identical to the published limit. A plan with 10,000 adds allows exactly 10,000 adds — not 9,800, not 10,200.
• No overage billing. MemorySync does not bill for usage beyond the plan limit. Once you reach the limit, requests are silently degraded until the cycle resets or you upgrade. There is no surprise bill at month-end.
• Atomic enforcement. The limit check and counter increment happen together as one indivisible step. Concurrent requests at the limit boundary are serialized — exactly one succeeds.

These are the exact limits enforced for each plan. Both metrics are independently tracked:

The two limits are independent. You can exhaust your add request quota while still having retrieval quota remaining, and vice versa. Hitting one limit does not affect the other.

When a request would exceed your plan limit, MemorySync uses silent degradation:

The usage counter is not incremented for degraded requests. The counter stays at the limit value — it never exceeds it.

Organizations can optionally set a monthly spending budget on top of plan limits. This is separate from the plan’s request quotas and operates on dollar amounts:

• Optional monthly budget. Configure a budget amount and an alert threshold from the billing dashboard. Budgets are off by default.
• Progressive throttling, not a hard cliff. As spend approaches your budget, expensive intelligence work runs in progressively more conservative modes. Above the alert threshold, only the most important work continues.
• Forecast and current spend. The dashboard surfaces both current spend for the cycle and a linear projection to end of month so you can react before utilization climbs into restrictive territory.

Budget and plan limits are separate: you can hit your plan’s add request limit without reaching your budget, and your budget can constrain intelligence features while you still have request quota remaining.

When a request is silently degraded by the quota gate, cost tracking behaves predictably:

• No charge for skipped requests. Silent skips do not advance the usage counter and do not contribute to spend.
• Predictable cycle totals. Because skipped requests are free, your spend for the cycle reflects only requests that actually ran.
• Detection on the dashboard. Metrics sitting at exactly 100% of their plan limit are the signal that silent degradation is in effect — configure dashboard alerts to be notified before you reach that point.

There are exactly two ways to restore access after hitting your plan limit:

There is no manual counter reset, no admin override, and no support ticket path to get extra quota mid-cycle. The system is designed to be fully self-service through plan management.