When credits are consumed
A request becomes billable after it passes API-key authentication, product access checks, burst-rate limits, and plan/quota enforcement, and Prontiq accepts it for endpoint processing. Requests rejected before admission do not consume credits. This includes missing or invalid API keys, products not included in your plan, burst-rate-limit rejections, and hard-cap quota rejections. Once admitted, a request may consume credits even if endpoint processing later returns a validation error, no match, or an API error. If you believe credits were consumed incorrectly during an incident, contact support.Endpoint credit costs
For plan, invoice, and payment state, see the Billing guide.
For traffic protection behaviour, see Rate Limits & Quotas.
Usage and billing totals
Usage appears in Prontiq first. Billing totals and invoices can take a few minutes to catch up while billing events settle. Do not build customer billing records from API response headers. Use the console for billing records and invoices.Response headers
Data API responses can include usage and quota headers.Header presence depends on the active account state and endpoint. Use
X-Request-Id or
error.request_id when contacting support about a specific request.Where to manage billing
Account billing
Signed-in users can see account-specific billing and usage in the console.
Billing support
Raise a support ticket for billing, invoice, or account questions.