Billing and pricing

One TokenLab balance works across models. There is no subscription or minimum spend; charges are based on the model and usage recorded for each request.

One result, one chargeCopy Anchor Link

Each completed request is charged once for the delivery option that produced the result:

• TokenLab Verified uses TokenLab public prices.
• Official uses the Official price layer based on the model maker's public price.
• Auto uses TokenLab Verified when available, then Official if needed. You pay for the option that completes the request.

For paid generation, Console shows the maximum estimate before confirmation. After completion, Runs and Usage show the final charge. Any unused reserved amount is released.

Pricing ModelsCopy Anchor Link

Model prices can change. Check Console, the Models page, GET /v1/models/:model/pricing, or the Pricing API for the current price.

On the Models page, a dash in the TokenLab price or discount column means no TokenLab Verified offer is currently available; it does not mean free. Models with Official supply remain available through Official or Auto. Delivery labels describe supported options, while availability is checked when each request runs. Series prices summarize models with supply in the relevant delivery option and keep different billing units separate.

Token-Based PricingCopy Anchor Link

Most chat, reasoning, embedding, rerank, and some image models are priced by input, output, cache, or image-output tokens.

Request and Task PricingCopy Anchor Link

Image, video, music, 3D, audio, and world models may be priced per request, image, second, minute, or task. The model page shows the billing unit.

Async task billingCopy Anchor Link

Video, music, 3D, and task-based image generation return a task ID and poll_url. The final amount is recorded after the task becomes completed or failed. A completed task includes billing_transaction_id after billing; a failed task is not charged.

If Usage still does not show the final charge or released amount after the task finishes, contact support@tokenlab.sh with the Request ID and task ID.

Billing transaction IDsCopy Anchor Link

Non-streaming OpenAI-compatible responses include billing_transaction_id when billing finishes before the response is sent. The same value may appear in X-Billing-Transaction-ID; Gemini and other native formats may expose it only in this header.

Async tasks include billing_transaction_id after completion. Streaming may finish before billing does, so use Usage when the header is absent.

Token countsCopy Anchor Link

Text models usually report input, output, and total tokens in usage. Tokenization differs by model, language, and media input, so character-count formulas are not reliable billing estimates. Use the model's current price and the final Usage record.

Find your usageCopy Anchor Link

Open Usage to find:

• Real-time balance
• Usage history by model
• Cost breakdown
• API key usage

API responseCopy Anchor Link

Token-based responses usually include usage information:

{
  "usage": {
    "prompt_tokens": 50,
    "completion_tokens": 100,
    "total_tokens": 150
  }
}

Spend lessCopy Anchor Link

Low-balance alertsCopy Anchor Link

Set a threshold in Console → Settings. TokenLab emails you when the balance falls below it.

Add balanceCopy Anchor Link

Open Console → Billing, choose an amount, and use one of the payment methods shown at checkout. The balance updates after the payment provider confirms the payment.

API Key LimitsCopy Anchor Link

You can set a spending limit when you create or edit an API key in Console → API Keys.

When the limit is reached, requests with that key will return 402 Payment Required.

Billing helpCopy Anchor Link

Contact support@tokenlab.sh for billing inquiries.