> For the complete documentation index, see [llms.txt](https://help.aikido.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.aikido.dev/miscellaneous-info/wallet-and-credits/automatic-top-ups.md).

# Automatic Top-Ups

Buy credits automatically when your wallet drops below a threshold, so credit-backed scans keep running.

Automatic top-ups let Aikido buy more credits when your wallet runs low. You set the balance that triggers a purchase, how many credits to add, and an optional monthly cap.

Automatic top-ups are not available by credit card. Aikido sends an invoice, and the credits are added after it is paid.

## What you need

* Workspace admin access.
* At least one successful payment on the workspace, by card or by invoice. A [manual credit purchase](/miscellaneous-info/wallet-and-credits.md#how-to-purchase-credits) counts. That payment unlocks automatic top-ups. Later top-ups are still invoiced.

## Turn it on

Open [Wallet settings](https://app.aikido.dev/settings/wallet/settings), click **Manage** next to **Automatic Top-Ups**, turn it on, and click **Save**.

| Setting         | Required | What it does                                                                                     |
| --------------- | -------- | ------------------------------------------------------------------------------------------------ |
| Top-Up Trigger  | Yes      | Aikido creates an invoice when the wallet balance drops below this many credits.                 |
| Top-Up Amount   | Yes      | Credits added each time. Minimum 100. One credit is $1 USD.                                      |
| Monthly Maximum | No       | The most credits Aikido invoices automatically in one calendar month. Leave it empty for no cap. |

The top-up amount cannot be higher than the monthly maximum.

## What happens when the wallet runs low

1. Aikido checks workspaces that have automatic top-ups turned on.
2. If the balance is below the trigger, Aikido creates an invoice for the top-up amount and emails it to workspace admins.
3. The purchase shows in [wallet history](https://app.aikido.dev/settings/wallet/history) as **Automatic Top-Up** with status **Awaiting Payment**.
4. After the invoice is paid, Aikido adds the credits and the transaction becomes **Completed**.

Aikido does not create another automatic top-up while an invoice is still unpaid. Pay or settle that invoice before the next one can be issued.

If the balance is still below the trigger after a top-up is paid, Aikido can invoice again, up to the monthly maximum. The monthly maximum resets at the start of each calendar month. It only counts automatic top-ups, not credits you buy yourself and not [monthly complimentary credits](/miscellaneous-info/wallet-and-credits.md#monthly-complimentary-credits).

## Spending limits

The monthly maximum caps how many credits Aikido buys for you. [Spending limits](/miscellaneous-info/wallet-and-credits.md#spending-limits) cap how many credits a feature can use. Set both if you want a ceiling on purchases and a ceiling on usage.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.aikido.dev/miscellaneous-info/wallet-and-credits/automatic-top-ups.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.