1. Overview

BOOST uses usage-based limits to keep pricing predictable and to protect system performance. Limits apply consistently to:

• Web app usage (running tools from the dashboard or tool pages).
• API usage (calling tools via /v1 endpoints).
• MCP usage (AI agents using BOOST tools through MCP).

The examples on this page are illustrative. Actual limits, thresholds, and prices are defined by your plan and billing provider. Not legal advice. Not financial advice.

2. Types of limits

BOOST may apply several kinds of limits, depending on your plan configuration:

• Per-tool generation limits – maximum number of generations for a specific tool per billing period.
• Total account limits – maximum number of generations across all tools per billing period.
• Rate limits – maximum number of requests over short windows (for example, per minute) to prevent abuse or accidental overload.

These limits are intended to balance performance, fairness, and cost control, especially when multiple users or integrations share the same account.

3. Per-tool usage limits

Each BOOST tool can have its own generation allowance, depending on whether it is subscribed individually or as part of a bundle.

• Individual tool plans may specify a limit like “up to N generations per billing period for this specific tool.”
• Bundles may specify shared pools or per-tool caps for all tools inside that bundle (for example, higher limits for follow-up tools).
• Custom bundles may override or supplement these defaults to match your business volume.

When a per-tool limit is reached, that tool will either soft-fail with a clear warning or hard-fail with a usage error, depending on your plan configuration.

4. Account-level usage limits

In addition to per-tool caps, your account may have aggregate limits across all tools in a billing period.

• Example: a plan might allow a combined total of all generations (listings, follow-up messages, explainers, etc.) up to a specified number per month.
• This aggregate limit is intended to prevent unexpected overuse from multiple tools or integrations at once.
• Account-level limits are applied no matter which interface you use (dashboard, API, or MCP).

Consult your plan details in Billing & Subscription for the actual numbers when billing is fully live.

5. Short-term rate limiting

Rate limiting protects the platform from bursts of traffic and ensures fair access across users. It is separate from monthly usage quotas.

• Rate limits measure how many requests are made in a short time window (for example, per minute or per second).
• Limits may differ for web usage vs. API integrations, but the principle is the same: prevent spikes that could degrade performance.
• When rate limits are exceeded, requests are temporarily rejected with a clear error instructing you to slow down and retry later.

{
  "error": {
    "code": "rate_limited",
    "message": "Too many requests in a short period. Please retry after a brief delay."
  }
}

6. Behavior when limits are exceeded

When a limit is reached, BOOST returns structured, machine-readable errors instead of partial or ambiguous responses. The exact behavior depends on how your plan is configured:

• Soft cap – BOOST may warn you that you are at or near your limit while still allowing a small number of additional generations.
• Hard cap – BOOST blocks further generations for that tool or account until the billing period resets or you upgrade your plan.
• Rate limit exceeded – BOOST may reject only some requests in a short window, while allowing others after a delay.

{
  "error": {
    "code": "usage_limit_exceeded",
    "message": "Your current plan limit for this tool or account has been reached.",
    "scope": "tool-or-account",
    "plan": "example-plan-name"
  }
}

7. Monitoring your usage

BOOST is designed to show you clear, high-level usage information without requiring you to inspect raw logs.

• The Dashboard will surface total usage and highlight tools you are using most.
• The Billing & Subscription section will show how much of your current period’s allowance has been used.
• API integrations can infer usage trends from responses and error codes (for example, usage-limit responses).

If your usage patterns change significantly, you may need to adjust your plan or bundle configuration so limits better match your workload.

8. Best practices for agents and teams

To avoid unexpected interruptions due to limits:

• Use BOOST for high-value content, not endless low-impact test generations.
• Coordinate across team members if you share a single account or workspace.
• For API or MCP integrations, implement backoff and error-handling when you receive rate or usage-limit errors.
• Review usage regularly and adjust your plan if you consistently hit limits.

All limits are applied on top of BOOST’s core compliance filters. Fair Housing/CREA compliant; no protected-class criteria used. Not legal advice. Not financial advice.