Top up credits
Buy Billing credit packages from the in-chat card or the Billing page.
Alumia credits are org-scoped managed-usage credits. Subscription packages grant monthly credits, promo credits can be granted after phone verification, and paid top-up buckets keep managed work moving when included credits run low. You buy top-up credits in one of two places: in the chat panel when a managed request needs more credits, or directly from the Billing page.
Path A: top up from the chat panel
When an agent tries to run a managed model or metered platform operation without enough credits, the chat panel surfaces a card explaining that credits are required. It includes two actions:
- Buy credits — opens the top-up dialog inline.
- Manage billing — link to
/<orgSlug>/billing.
Click Buy credits. You stay in the lab; no tab switch needed.
Path B: top up from the Billing page
Navigate to /<orgSlug>/billing. The same Buy credits action lives near the credit summary. Click it to open the same dialog.
The Buy credits dialog
The dialog title is Buy credits, with the description explaining that top-up credits are added to your org credit account after payment confirmation.
Pick a top-up package. Billing validates the selected package against the active catalog and your package policy before creating payment.
Click Continue to payment. The dialog creates a Stripe PaymentIntent via /api/v1/billing/top-ups/payment-intent and renders the payment form in the modal, so you stay on the Billing page or in the lab overlay.
Card confirmation
Enter your card in the embedded form. Stripe handles 3-D Secure and wallet methods where enabled. On success, the webhook grants a paid top-up credit bucket and the UI refreshes the credit summary without a full redirect.
What happens to the funds
- The top-up lands as paid Billing credits in your org account.
- The first 1,000 eligible users on the platform can also receive 1,000 Early Bird promo credits after phone verification.
- Credit budgets can be configured from
/<orgSlug>/billingso threshold alerts warn before hard caps pause managed spend.
Verify
Send a message in the lab on any managed model. Credits tick down as the request finishes, and the request shows up in /<orgSlug>/billing under usage. If you instead see a payment-required error, the top-up did not land or the package/budget still blocks the request — see Troubleshooting.