Auto Top-Up
Auto top-up charges a fixed amount to your saved card the moment your balance falls below a threshold you choose. That way an overnight PDF batch or a busy monitoring period is never cut short by a 402 INSUFFICIENT_CREDITS error. The feature is optional and off by default; teams starting on the welcome credit are never asked for a card.
Add a payment method
Add a card under Settings → Billing → Payment methods. Only the team owner and admins with billing permission can add cards and change auto top-up.
Set the threshold and amount
Open the Auto top-up section on the same page and enter three values:
| Setting | Example | Description |
|---|---|---|
| Threshold | $5 | A top-up fires when the available balance drops below this amount. |
| Top-up amount | $25 | The amount charged to the card on each trigger. At least $10. |
| Monthly cap | $200 | The highest total that can be topped up automatically in one calendar month. |
Pick a threshold that is a few times your busiest hour's spend. For an integration spending $2 an hour, a $5 threshold leaves enough buffer until the top-up completes.
Confirm the top-up
Every successful top-up sends an email to your team and a credits.topped_up webhook event. You can hook your own accounting or monitoring system onto this event:
{
"event_type": "credits.topped_up",
"payload": {
"amount_usd": 25.00,
"trigger": "auto",
"balance_after_usd": 29.62,
"invoice_id": "inv_3k9d72"
}
}The invoice appears immediately under Settings → Billing → Invoices.
If a buggy loop starts hundreds of jobs a second, auto top-up keeps funding it. When the cap is reached, top-ups stop, you get an email and new jobs start receiving 402 again; it is your last safety belt against runaway spend.
If the card is declined
If a payment is declined, auto top-up retries twice more within 24 hours, then pauses and notifies the team owner. Once you update the card, the feature switches back on by itself. To make sure the balance never runs out unexpectedly, use auto top-up together with Balance Alerts.