Understanding Usage & Billing.

Your billing cycle starts on the day you create your team and runs for one calendar month, then resets. If you create a team on January 15th, it renews on the 15th of every month. If you create a team on the 30th, it renews on the 30th. In February, or any other month with fewer than 30 days, it renews on the last day.

At the end of each cycle, ForecastAPI totals the API calls you made and charges your saved payment method for the usage-based amount. During the cycle, your team's Usage & Billing page shows the total. ForecastAPI calculates that total the same way as the final charge, so you have nothing separate to reconcile.

Pricing is tiered: the more you use in a billing cycle, the lower your rate for calls in the higher tiers. This applies automatically. You do not need to enable it.

Every billing cycle includes 200 free API calls. You do not need a credit card. After you exceed the free calls, a minimum charge of $1.00 applies even if your calculated usage is lower. ForecastAPI still bills $0.75 of calculated usage at $1.00. ForecastAPI also caps free tier requests at 100 datapoints each. Paid requests have no datapoint limit.

Example calculation

Suppose you make 55,000 calls in a month:

Team admins can open Usage & Billing from the team sidebar to see the current cycle's activity. It shows:

Usage figures can lag up to 15 minutes behind actual API activity. Treat the dashboard as a close estimate, not a live counter.

By default, usage is unlimited and ForecastAPI bills you for whatever you use. To cap it, set a monthly spending limit on the Usage & Billing page. After billable usage reaches the limit, ForecastAPI blocks further billable API requests until the next cycle or until you raise the limit.

1. No limit (default)

   Usage is unlimited and ForecastAPI bills you for actual usage each month. Use the Remove button on the spending limit form to return to this option.

2. Free tier only

   Enter 0 to cap usage at the free tier. ForecastAPI blocks any billable request. Use this setting for a development or testing team that must stay at $0.

3. Custom limit

   Enter any amount at or above $1.00 (e.g. 50.5). A warning appears after usage passes 80% of the limit. ForecastAPI blocks billable requests at 100%. A change to the limit takes effect immediately, in both directions.

A blocked billable request returns HTTP 402 with error: "spending_limit_exceeded". Free tier requests still work, even under a $0 limit.

Use batch endpoints whenever you process more than one entity at a time. The 50% discount applies with no other change to your integration. Set a $0 spending limit on development and staging teams so test traffic can never generate a charge. If your bill moves unexpectedly, the endpoint breakdown on the usage dashboard is usually the fastest way to spot a runaway integration.

Can I change my spending limit mid-cycle?

Yes, at any time, and it takes effect immediately. If you raise the limit, ForecastAPI unblocks requests that it rejected. If you lower it below current usage, ForecastAPI blocks new billable requests right away.

How accurate is the estimated cost on the dashboard?

ForecastAPI calculates it the same way as the final charge. Usage data can take up to 15 minutes to reach the dashboard, so the figure trails live traffic slightly and does not update instantly.