Credits and usage

# Credits and usage ## Credits Usage is measured in **credits**, an abstract unit. How many you have depends on your plan: * **Free**: a one-time grant that never renews. * **Starter**: a monthly allotment that resets each billing cycle. * **Enterprise**: custom grants. See [Plans](/docs/self-enterprise/billing/plans/). ## Per-verification cost Each verification costs a fixed number of credits, decided by the product. The cost is locked in when the session is created (so an in-flight session keeps the price it started with), but the credit is **charged when the verification completes**, not at creation: | Product | Credit cost | | --- | --- | | Pre-KYC | 25 | | Age Verification | 10 | | Proof of Human | 10 | | Sovereign | 10 | The dashboard shows the cost when you configure a product. To estimate spend, multiply your expected verifications by the product's cost. ## What you're invoiced for Your invoice (the metered usage Self bills) counts verifications that produced a result, not sessions the user abandons: | Session result | On your invoice? | | --- | --- | | `valid` | Yes | | `invalid` (a rule failed) | Yes | | `error` (technical failure) | No | | `expired` (never started/completed) | No | ## Insufficient credits If your balance can't cover a session's cost, `sessions.create(...)` is rejected with HTTP `402` (the SDK throws `SelfApiError` with `statusCode: 402`, and `details` carries `balance`, `required`, and `planTier`). The session is not created. To add capacity, upgrade your plan from **Manage plan** (or talk to sales about Enterprise). Watch the credits meter on the **Settings → Usage & Billing** tab so this doesn't surprise you. ## Test environment Test verifications (sessions created with an `sk_test_` key) never consume credits. Use test freely. ## Related * [Plans](/docs/self-enterprise/billing/plans/): what each tier includes. * [Dashboard: Billing](/docs/self-enterprise/dashboard/billing/): the Usage & Billing tab.