Billing
How LLM247's prepaid credit system works — deposits, deductions, and balance management.
Prepaid Credit Model
LLM247 operates on a pay-as-you-go basis. There are no recurring charges, no seat fees, and no usage minimums. You deposit credit into your account; that credit is drawn down as you make API calls.
The flow is straightforward:
- Deposit credit — Add funds to your account from llm247.net/billing
- Call the API — Before paid upstream work starts, the API reserves a conservative request budget from your available credit. After authoritative usage arrives, it settles the actual cost and releases unused funds.
- Track spend — The dashboard shows live balance, per-request cost breakdowns, and model-level usage aggregates
- Reload when needed — Your balance carries forward indefinitely; top up whenever it runs low
How Deductions Are Calculated
Token-priced models (chat / completion)
For text models — including OpenAI GPT-5.6, Anthropic Claude, Google Gemini, and every open-weight option in the catalog — token cost is calculated separately for input and output, then summed:
request_cost = (input_tokens / 1,000,000) × input_rate
+ (output_tokens / 1,000,000) × output_rateWorked example — calling gpt-5.6-terra with a 500-token prompt that generates a 200-token reply:
cost = (500 / 1,000,000) × $1.250
+ (200 / 1,000,000) × $7.500
= $0.0006250 + $0.0015000
= $0.0021250Providers may return a usage field containing token counts. Streaming clients should request usage reporting. Missing or incomplete provider usage is not treated as a free completed request: the reservation remains held until it can be reconciled against provider evidence.
{
"usage": {
"prompt_tokens": 500,
"completion_tokens": 200,
"total_tokens": 700
}
}A confirmed rejection before billable work releases its reservation. Timeouts and ambiguous failures may retain a hold because the provider may have performed work.
Payment Methods
We support two payment methods:
- Card — All major credit and debit cards, processed securely via Stripe.
- Crypto — Available currencies are shown at checkout and processed via Plisio. You'll be redirected to the payment partner to complete the transaction.
Top-Up Amounts
| Label | Amount | Suited For |
|---|---|---|
| Starter | $10 | Initial evaluation and exploration |
| Standard | $25 | Light to moderate development work |
| Developer | $50 | Active integration and testing |
| Team | $100 | Shared team access or small projects |
| Growth | $250 | Production workloads |
| Enterprise | $500 | High-volume or sustained usage |
Need an amount outside these tiers, or a custom arrangement? Submit a request via the contact form.
Checking Your Current Balance
From the portal: the balance page shows available credit. Funds reserved for in-flight or unresolved requests are not available for another request and are not counted as collected usage until settlement.
The authenticated portal balance endpoint is /api/user/balance; it uses a portal session token, not an inference API key. The legacy /v1/dashboard/billing/credit_grants endpoint is not supported.
Insufficient Funds and Financial Holds
A positive balance alone does not guarantee admission. If available credit cannot cover the request budget, the API rejects the request before paid upstream execution with HTTP 402 and an insufficient_quota error. A fully depleted wallet is rejected by authentication with HTTP 429 and the same error type.
Concurrent requests share the same available funds: they cannot reserve the same money twice. Reduce an explicit output-token limit or add funds if the request budget exceeds your available balance.
Requests containing features without a prepaid pricing policy (such as provider-hosted search or remote media) return HTTP 400 with invalid_request_error, not insufficient_quota. Declared client-side function tools and bounded Kimi reasoning use the model's token rates; they do not spend separate hosted-tool credits.
Account-level API suspensions return HTTP 403 with account_suspended; replacing or re-enabling API keys does not remove the suspension. Adding credit does not automatically clear a financial hold. Contact support with the request or payment reference for reconciliation.
Refund and Adjustment Policy
Credit purchases are non-refundable. We recommend starting with a smaller deposit to validate your integration before committing to a larger amount.
If a technical fault on our end caused an incorrect deduction, use the contact form with the affected request IDs and timing. We review each case individually.