[ Documentation ]
REST API Billing and Limits

REST API Billing and Limits

The REST API uses the same account ledger, included allowance, prepaid balance, monthly spending cap, and daily safety limit as Contrast and rnx. API usage is recorded with surface: api so account reporting can separate it from UI and CI usage.

Current API rates

API rates are configured separately from UI and CI rates and currently launch at the same values as the customer rate card. The test-run upload charge is flat per artifact regardless of duration. Registration and read requests do not add usage charges.

Preview and build charges use a commit-based idempotency key when Git provenance is present. Uploading the same repository commit through UI, CI, and API creates one charge, attributed to whichever surface records it first. Test-run artifact charges are idempotent by preview share ID.

A free or otherwise ineligible account receives 402 subscription_required. Ledger limits return their specific 402 code, such as monthly_cap_exceeded, daily_velocity_exceeded, free_grant_exhausted, or balance_exhausted.

Request throttling is separate from spending protection. See Rate Limits.