Usage credits
Each request records provider, model, tokens, cost, and balance impact. Prices are configured through provider cost profiles.
Pricing
Use prepaid CREDITS during launch, then reconcile payment orders, checkout sessions, signed webhooks, usage debits, tax snapshots, and invoices from the same ledger.
Each request records provider, model, tokens, cost, and balance impact. Prices are configured through provider cost profiles.
Customers can open a provider-hosted payment page from the portal. Balance credit is applied only after the signed payment webhook.
Billing profiles, tax snapshots, numbered invoices, and PDF downloads are available for customer and admin workspaces.
Commercial packages
For testing OpenAI-compatible migration, model aliases, request logs, and customer billing workflows.
For production customers that need online recharge, invoice PDFs, routing policy, and cost-aware fallback.
For dedicated provider policy, compliance review, higher quota, manual settlement, and migration support.
What is included
| Provider setup | Bring your own provider keys, configure Base URLs, and keep customer-facing API keys separate from upstream credentials. |
|---|---|
| Margin control | Set per-model costs, aliases, routing priorities, and fallback policy so operators can review margin exposure before opening traffic. |
| Settlement | Support prepaid balances, manual payment orders, online checkout sessions, webhook verification, invoices, and CSV statement export. |
Launch assumptions
| Currency | Beta accounts use prepaid CREDITS. Real currency price lists should be configured per market before public self-service checkout. |
|---|---|
| Taxes | Japan consumption tax, qualified invoice requirements, VAT/GST wording, and cross-border tax treatment need accounting review for each target jurisdiction. |
| Refunds | Refund handling should follow the published refund policy and any final company terms shown before purchase. |