Skip to main content
Fireworks uses different controls for serverless and on-demand deployments. This page is the canonical reference for spending tiers, monthly spend limits, on-demand GPU quotas, and account-wide request limits. For serverless TPM and adaptive limits, see Serverless rate limits.

Check your current limits

View your account’s current quotas and limits:
This shows your rate limits, GPU quotas, spend limits, and usage across serverless and on-demand deployments.

Spending tiers

Your spend tier controls available quotas and capacity. For legacy self-serve postpaid accounts, it also determines the maximum monthly spend limit. Prepaid accounts can set a monthly spend limit independently of tier.
Add prepaid credits to unlock a higher tier. For example, adding $100 moves you from Tier 1 to Tier 2. Your new tier activates within minutes.
These spending tiers control the maximum serverless TPM upper bounds your account can reach. The spend-limit maximum shown above applies only to legacy self-serve postpaid accounts.Fireworks operates on a pre-paid credits billing system. Contracted customers may have the option to move to post-paid billing — contact our sales team to discuss your options.

Training GPU quota

Fine-tuning jobs use training GPU quota (separate from on-demand deployment quota), granted automatically by spending tier: Counts are GPUs of that type available to training jobs. Blackwell (B200/B300) is 0 until Tier 2, and current managed fine-tuning shapes run on Blackwell, so most fine-tuning needs Tier 2. If a job is rejected with HTTP 429 quota_exceeded, raise your tier and resubmit.
Need more training quota than your tier allows? Reach out for enterprise support and we’ll help size the right allocation for your workload.

Enterprise accounts

Enterprise accounts do not have the same spend limits. If you have an Enterprise account, the spending tiers and spend-limit controls described on this page do not apply to you. For information about Enterprise quotas and resource allocation, see Enterprise quotas or contact your enterprise account representative.

Manage your quotas

Account-wide request limits

All API usage on your account shares a single request-throughput envelope: The 6,000 RPM cap applies account-wide—it is not a separate serverless-only limit—and it is a fixed ceiling, not adaptive. Per-minute request volume above this cap is rejected (for example HTTP 429), regardless of your spending tier.

Monthly spend limit

Set a monthly spend limit that fits your needs and adjust it anytime. For prepaid accounts, the limit tracks the dollar value of your usage regardless of whether credits pay for that usage. Adding credits increases your available balance, but does not raise or reset your monthly spend limit. Auto Reload is separate from the spend limit. Auto Reload purchases credits when your balance is low; it does not change how much usage your account can accrue during the month. Contracted postpaid accounts may have different billing terms. Contact your account representative if you have questions about how a postpaid limit is calculated.

View and adjust your spend limit

Check your current spend limit:
Set a custom monthly spend limit:
For example, to set a $200 monthly spend limit:

Warnings and suspension

By default, Fireworks sends a warning email when usage reaches 80% of your monthly spend limit. You can add other notification amounts from the Billing page. When usage reaches 100% of the limit, all API requests pause automatically across serverless inference, deployments, and fine-tuning. Raise the monthly spend limit to resume usage. If your credit balance is also depleted, you must add credits as well.
The self-serve spend-limit behavior described here does not apply to Enterprise accounts. Refer to your contract or contact your account representative for your account’s billing and suspension terms.

On-demand deployment quotas

On-demand deployments have GPU quotas instead of rate limits:
Need more GPUs? Contact us to request a quota increase.
On-demand and dedicated deployments are not limited by adaptive serverless TPM upper bounds. If you receive HTTP 429 on those endpoints, it typically means deployment saturation (GPUs busy) rather than hitting a TPM tier cap. Requests still count toward account-wide request limits. See understanding 429 errors for details and resolution steps.

Account recovery

If your account is suspended due to payment issues:
  1. Go to Billing
  2. Resolve failed payment methods and add credits (or pay outstanding invoices for postpaid accounts)
  3. Your account reactivates automatically within an hour
Still suspended after resolving payment issues? Contact support via Discord or email inquiries@fireworks.ai.