Transactions and API key settings
Manage your transactions, API key access and spending limits.
Transactions
Billing shows top-ups, charges, refunds and adjustments in rupiah. Top up from Billing with QRIS, a credit card, a bank virtual account or a retail payment code; the full amount is credited. Requests using keys supplied by Ark draw from your balance at the model’s listed rate. Usage on your own provider keys is billed directly by that provider. Corrections appear as separate transactions.
- Transactions: filter by date and type.
- API keys: filter by name and enabled state.
- Both lists use Previous/Next navigation with 15, 30, 50 or 100 rows per page.
- Transaction links open the associated inference request.
Coupon credit
Redeem a coupon code from Billing, or with POST /api/billing/coupons/redeem and {"code": "…"}. Codes are not case-sensitive and each one can be used once per account. Organization owners and admins can redeem for the organization by adding organization_id. Coupon credit is not a payment, so it has no invoice.
- Models: coupon credit pays only for the models listed with the code. Other models use your paid balance.
- Order: a paid request uses eligible coupon credit first, soonest expiry first, then your paid balance.
- Expiry: unused credit is removed when it expires and appears as a separate transaction. A request already in progress keeps the credit it was admitted with.
- Limits: spending paid with coupon credit counts toward spending limits.
GET /api/billing/credits shows your paid balance and each credit with its remaining amount, expiry and models. Logs show the part of each charge paid with coupon credit in coupon_credit_micro.
Top-up bonus codes
Enter a bonus code in the top-up dialog. When the payment is confirmed, a share of the topped-up amount is added as coupon credit and follows the coupon rules above: the code’s models, expiry and spending order. A code can cap the bonus, require a minimum top-up and limit how many top-ups per account earn it. POST /api/billing/topups/preview with {"code": "…"} returns the rule before you pay. The bonus is not charged or taxed, and the invoice notes it.
On a model shown with a discount, bonus and coupon credit pay the list price unless the code says it is usable at discounted prices. Your paid balance is spent first there, at the discounted price, and the credit is kept for other models.
API key settings
Open an API key to manage:
- Name and expiration to identify the key and control its lifetime.
- Request limits. Blank limits allow unlimited requests.
- Model, provider and connection access. Empty access lists allow all resources within the other restrictions.
Disabling a key is reversible. Deleting it stops clients using that secret. Activity and Logs shortcuts filter usage to the selected key.
Spending limits
Account and API key spending limits apply to paid Ark inference. BYOK requests and response-cache hits are free.
- Unlimited: the default. Set a limit to cap spending.
- Zero: blocks new paid requests.
- Daily: resets at midnight UTC.
- Weekly: resets on Monday.
- Monthly: resets on the 1st.
- Lifetime: never resets.
Resetting a limit does not refill your balance. Changing a limit does not erase spending history.
Estimates and final charges
- Admission checks actual spending plus pending estimates against all applicable limits.
- A rejected estimate returns
402 budget_exceededbefore dispatch. - Final charges use actual usage and can exceed the estimate or limit. Overages are shown and block later paid requests.
Pending estimates carry across reset boundaries.
Manage limits through the API
- Account:
GET /api/billing/budgetorPUT /api/billing/budget. - Owned key:
GET /api/api-keys/:id/budgetorPUT /api/api-keys/:id/budget.
To set a Rp100.000 monthly limit, send this PUT body:
{
"limit_micro": 100000000000,
"reset": "monthly"
}Use limit_micro: null for unlimited spending. Responses include settled spend, reservations, remaining allowance, overage and the next reset.
A signed-in session is required. Inference Bearer tokens do not grant account-management access.
Export usage
GET /v1/usage/export exports matching requests as CSV, up to 10,000 records.
- Filters:
from,to,model,provider,status,api_key_id,kindandrequest_id. - Date ranges: include the start and exclude the end.
- Timeseries: accepts an IANA
timezone. - Excluded: request bodies and credentials.