Pricing and billing
Credits and billing
Credits, holds, card verification, auto-recharge and promo codes.
One credit is one cent of platform usage. Platform-funded calls draw down your credits at catalog price with no markup; calls on your own provider key are billed by your provider and never touch your credits. Balance, top-ups and auto-recharge live on the Credits page in the app.
Credits
| Fact | |
|---|---|
| Value | 1 credit = $0.01 |
| Fractions | Supported |
| Balance | Credits granted minus platform-funded spend |
| Sources | Plan allotment, top-ups, auto-recharge, bonuses, promotions |
| Order used | Soonest expiry first; then free grants and bonuses before purchased credits |
Top-ups need no subscription. API fields carry money in nano-USD: a call's usage.cost and the usage APIs' cost_nano_usd.
{
"usage": {
"prompt_tokens": 1200,
"completion_tokens": 300,
"cost": 0.0084,
"is_byok": false
}
}usage.cost is dollars (0.0084 = 0.84 credits). On your own key it is 0 with is_byok: true.
Pending holds
When a platform-funded request starts, the gateway holds its worst-case cost until the provider reports usage, usually within seconds. A hold is not a charge: it settles to the actual cost. Your balance counts settled charges; what new requests can use is the balance minus open holds.
GET/api/orgs/{org_id}/pending-holds| Moment | Balance | Available |
|---|---|---|
| Before | 1,000 | 1,000 |
| Request starts, holds 40 | 1,000 | 960 |
| Settles at 12 | 988 | 988 |
Verification
Free and promotional models need a verified card. Verification places a temporary $1 hold that is released, not charged (where holds are off, the $1 is charged and credited to your balance). Any settled purchase also verifies the organization. Your own provider keys work without verification.
| Response | Meaning |
|---|---|
402 card_required | Complete the $1 card verification |
402 free_tier_requires_payment | This free tier needs a card on file or a verified card |
429 model_requires_payment: | This model's lanes open after verification or any top-up |
429 model_requires_purchase: | This model's lanes open after a real purchase (top-up or plan); verification is not enough |
These clear by acting, not by retrying. The message names the exact step and links the page.
Auto-recharge and limits
Auto-recharge tops up your balance off-session when it falls below a threshold you set on the Credits page. To cap spend, use per-key spend caps, budgets and spend alerts.
| Control | Scope |
|---|---|
| Auto-recharge | Organization balance |
| Key spend cap | One key, per day, week, month or year (UTC) |
| Budget | Team, key, model or identity, monthly or recurring |
| Spend alert | Email when org spend or a budget crosses a threshold |
When credits or a cap run out, calls fail with 429 insufficient_quota; the message says which (insufficient_credits, key_daily_cap, a budget). It does not clear on retry.
/api/orgs/{org_id}/budgetsGET/api/gateway/usage/dailycurl "https://api.experientiallabs.ai/api/gateway/usage/daily" \
-H "Authorization: Bearer YOUR_API_KEY"Promo codes
The checkout has one Promo code field, shared by top-ups and plans. A code either lowers the charge, or matches a share of your purchase in bonus credits on top. If a purchase qualifies for more than one bonus (a code and a plan's first-cycle bonus, say), you get the single best one, never a stack, so a code can only improve on the no-code outcome.
| Code kind | Effect |
|---|---|
| Discount | Lowers what you pay |
| Match | Bonus credits on top of a full-price purchase |
| Two bonuses apply | You get the larger |