Billing and credits

Hosted API runs use prepaid credits. Available credit packs and their configured prices appear in the developer console.

Reservation and settlement

Before a run is queued, the service validates the request and reserves enough credits for the selected compute profile. At termination it settles the measured charge through the existing credit ledger and returns unused reserved credits under the normal refund rules.

The run response exposes:

{
  "credits_reserved": 10,
  "credits_settled": 3
}

Balances are never adjusted directly outside the ledger service.

Buying credits

Selecting a pack opens Stripe Checkout. A completed payment grants the configured number of credits only after a signed Stripe event is processed. Provider event IDs are stored, so replaying the same event cannot grant credits twice.

An insufficient balance returns 402 and maps to InsufficientCreditsError in Python.