Skip to main content
API credits are consumed based on results returned, not requests made. You’re charged for what you actually receive — failed calls and empty responses cost 0 credits.

What costs credits

Examples

Plans and overages

Each plan includes a monthly credit allowance that resets at the start of every billing cycle — credits don’t roll over. Once the included credits are used, additional usage is billed at the plan’s overage rate. See Plans, Billing & API Credits and Understanding API credit overages.

Overage protection

Overage protection lets you cap API spend at your plan’s included credits. It applies to all paid plans (Premium and Enterprise) and is off by default — additional usage beyond your monthly allowance is billed at the plan’s overage rate (see pricing). Toggle it from the API settings in your dashboard:
  • Off (default): Requests continue to succeed after you exhaust your included credits. Any additional credits are billed as overages.
  • On: Requests to endpoints that consume credits are paused as soon as your team reaches its monthly credit limit. No overage charges will occur. Access resumes automatically at the start of the next billing cycle.
When overage protection is on and the limit is reached, credit-consuming endpoints return a 402 Payment Required response:
To restore access before the next cycle, either turn overage protection off or upgrade your plan.

Check your usage

Retrieve your team’s credit usage for the current billing period.
Authenticate with your API key in the x-api-key header.

Response

Example request