Auto-reload is the automatic credit top-up of RichAPI. When the organization balance drops below a threshold that you set, RichAPI buys one credit pack for the organization. RichAPI charges the default card of the organization off-session, so the top-up happens with no user at the keyboard. An organization owner turns auto-reload on in the Auto-Reload card on the Plans & Billing page of the dashboard.
This article covers the automatic top-up only. For the credit pack prices, the rate tiers, and the manual purchase flow, read Buying Credits and Upgrading Plans.
What does RichAPI auto-reload do?
Auto-reload watches the organization balance. When the balance falls below the threshold, auto-reload buys one credit pack. RichAPI stores four values for each organization: the on-off switch, the threshold in credits, the reload pack, and the date of the last reload.
Setting | Dashboard label | Allowed value | Default |
Switch | Auto-Reload | On or off | Off |
Threshold | Reload when credits drop below | 1 to 1,000,000 credits | 100 credits |
Reload pack | Reload amount | One of the six credit packs | 1,000 credits — $20 |
Last reload | Last triggered | A date, or Never triggered | Never triggered |
Cooldown | Not shown | 24 hours between reloads | 24 hours |
The cooldown is fixed. An organization gets one automatic reload in any 24-hour period.
CAUTION: Auto-reload charges the saved card without any action from a user. A workspace with steady traffic can trigger one charge every 24 hours. A 50,000-credit reload pack charges $800 each time.
When does auto-reload trigger?
Auto-reload runs after RichAPI settles the credits for an API call. RichAPI reads the new balance. Every condition in the table below must be true before RichAPI starts a reload.
# | Condition | Detail |
1 | The Auto-Reload switch is on. | A workspace that never selected Save has auto-reload off. |
2 | The call returned a | A |
3 | The call charged credits. | A free call and an async job status poll charge nothing, so neither starts a reload. |
4 | The new balance is below the threshold. | A balance equal to the threshold starts no reload. The test is strict. |
5 | 24 hours passed since the last reload attempt, paid or declined. | Inside the cooldown, RichAPI skips the reload. |
CAUTION: A call that returns 402 never triggers auto-reload. Set the threshold above the cost of your most expensive single call. A successful call then fires the reload while credits remain.
Condition 3 matters for a workspace that polls async jobs. A status poll costs 0 credits, so a client that polls for hours triggers no reload in that time.
How do I turn on auto-reload?
Open the dashboard and select the workspace.
In the sidebar, open Usage & Billing.
Select Plans & Billing.
Find the Auto-Reload card.
Turn on the switch beside Auto-Reload. The card shows two fields.
In Reload when credits drop below, enter the threshold in credits.
In Reload amount, select a credit pack.
Select Save. The dashboard shows the message Auto-reload settings saved.
Auto-reload takes effect on the next successful billable API call. RichAPI runs no reload for a workspace that sends no calls.
Which credit pack does auto-reload buy?
Auto-reload buys exactly one pack for each reload. The Reload amount list holds the same six packs that the Buy Credits section sells. RichAPI stores the position that you select, so the pack never changes until you save a new one.
Position in the list | Credits | Price | Price per credit | Discount against $0.02 |
1st (default) | 1,000 | $20 | $0.020 | None |
2nd | 5,000 | $100 | $0.020 | None |
3rd | 10,000 | $190 | $0.019 | 5% |
4th | 25,000 | $450 | $0.018 | 10% |
5th | 50,000 | $800 | $0.016 | 20% |
6th | 100,000 | $1,500 | $0.015 | 25% |
The list rate is 1 credit = $0.02. At the list rate, 50,000 credits cost $1,000. The pack costs $800, which is a saving of $200, or 20%.
The Reload amount list opens on the first pack. If you do not change that choice, auto-reload buys 1,000 credits for $20 on every reload.
RichAPI adds the credits to the balance after Stripe confirms the payment. The Transaction History table on the Plans & Billing page then records the reload with the type Purchase and the amount that the card paid.
How do I choose a threshold?
The threshold is the balance at which RichAPI buys the next pack. Pick a threshold that covers the traffic of the workspace while the reload lands. The threshold must also cover the 24-hour cooldown that blocks a second reload.
Two rules keep production traffic alive.
Set the threshold to at least one full day of credit spend.
Set the reload pack to at least several days of credit spend.
Rule 2 exists because of the cooldown. After a reload, the balance is about the threshold plus the pack. That total must last until the next reload is allowed. If the pack covers less than 24 hours of traffic, the workspace burns the pack, waits out the cooldown, and then eats into the threshold.
A worked example. A workspace spends 500 credits a day, which is 21 credits an hour. The default threshold of 100 credits covers under 5 hours. That default gives no room for a weekend or for a traffic spike. A threshold of 1,000 credits covers 2 days, and a 10,000-credit pack covers 20 days of that traffic.
CAUTION: Do not leave the threshold at 100 credits for production traffic. At 500 credits a day, 100 credits is under 5 hours of cover, and a single large bulk call can clear it in one request.
Which threshold and pack suit my call volume?
Find the row that matches the daily credit spend of the workspace. The arithmetic in the last column shows how much cover each number buys.
Volume | Daily spend | Threshold | Reload pack | The arithmetic |
Low | 100 credits ($2.00) | 500 credits | 5,000 credits — $100 | 500 ÷ 100 = 5 days of cover. 5,000 ÷ 100 = 50 days of traffic for each reload. |
Medium | 500 credits ($10.00) | 1,000 credits | 10,000 credits — $190 | 1,000 ÷ 500 = 2 days of cover. 10,000 ÷ 500 = 20 days of traffic for each reload. |
High | 5,000 credits ($100.00) | 10,000 credits | 50,000 credits — $800 | 10,000 ÷ 5,000 = 2 days of cover. 50,000 ÷ 5,000 = 10 days of traffic for each reload. |
Every row keeps the reload pack well above one day of spend, so the 24-hour cooldown never blocks a needed reload. The dollar figures use the list rate of 1 credit = $0.02.
What payment method does auto-reload need?
Auto-reload charges the default card of the Stripe customer for the organization. RichAPI sets that default card after a credit pack purchase in Stripe Checkout.
Open Usage & Billing > Plans & Billing.
Find the Manage Payment Method card.
Select Open Billing Portal. The dashboard redirects the browser to Stripe.
Add a card, or set an existing card as the default.
Return to the dashboard from the Stripe portal.
If the organization has no default card, RichAPI treats the reload as declined. After a decline, RichAPI adds no credits and starts no new reload for 24 hours. The next try comes with the first successful billable call after those 24 hours.
CAUTION: RichAPI sends no email for a failed reload. RichAPI also sends no 90% or 100% credit depletion email while auto-reload is on. Treat a 402 in your own logs as the alert.
Handle the 402 in the client so that a failed reload pages a human.
import requests
response = requests.post(
"https://api.richapi.ai/api/v1/enrich_profile",
headers={"x-api-key": "YOUR_API_KEY"},
json={"url": "https://www.linkedin.com/in/satyanadella"},
timeout=60,
)
if response.status_code == 402:
raise RuntimeError(f"RichAPI credits exhausted: {response.json()}")
response.raise_for_status()
print(response.json())
How do I see the last time auto-reload triggered?
Open Usage & Billing > Plans & Billing.
Find the Auto-Reload card.
Read the text at the bottom left of the card.
The card shows Last triggered: with a date, or it shows Never triggered. The Auto-Reload card hides that text while the switch is off. The date also changes when a reload attempt fails.
To confirm that the credits landed, scroll to the Transaction History table on the same page. The table lists the last 50 credit allocations of the organization. A reload appears as a row with the type Purchase, a positive credit count, and the amount that the card paid.
How do I turn auto-reload off?
The Auto-Reload card hides the threshold field, the reload amount field, and the Save button while the switch is off. So the dashboard cannot save the off state today. To turn auto-reload off, select the chat button in the bottom-right corner of the dashboard, or write to [email protected]. Name the workspace, and RichAPI turns auto-reload off for the organization.
While auto-reload is off, RichAPI sends one organization owner an email alert at 90% credit depletion and a second email at 100% depletion. Each alert goes out once until the next top-up.
What happens when auto-reload is off and the balance runs out?
If the organization balance cannot cover a call, the API returns 402 and runs no request. RichAPI charges no credit for the rejected call.
{
"error": "Insufficient credits",
"reserved": "<credits that the call needs>",
"balance": "<credits left in the organization balance>"
}
Field | Type | Description |
| string | Always |
| string | The credits that the call needs. |
| string | The credits left in the organization balance. |
A 402 is a dead end for auto-reload. RichAPI checks auto-reload only after a successful billable call, so a workspace at zero credits cannot recover on its own. To clear the 402, buy a credit pack on the Plans & Billing page, then raise the auto-reload threshold.
Why does auto-reload not fire?
What you see | Cause | Correction |
The balance is below the threshold and no reload happens. | The Auto-Reload switch is off, or the workspace never selected Save. | Turn on the switch, set the two fields, and select Save. |
The balance is below the threshold and no reload happens. | A reload ran, or a reload failed, inside the last 24 hours. | Buy a credit pack on the Plans & Billing page. Select a larger pack in Reload amount. |
The balance is below the threshold and no reload happens. | The recent calls returned | Buy a credit pack on the Plans & Billing page. Raise the threshold above one day of spend. |
The balance reached zero and no reload happens. | The workspace has no default card in Stripe. | Open Manage Payment Method > Open Billing Portal. Add a card and set it as the default. |
The card was declined. | Stripe refused the off-session charge. | Update the card in the Stripe billing portal. RichAPI tries again on the first successful billable call after 24 hours. |
Last triggered shows today, and the balance looks unchanged. | The credits arrive through a Stripe payment event, not through the browser. | Reload the Plans & Billing page after a few seconds. |
The reload is late every time. | The threshold is too low for the traffic of the workspace. | Raise the threshold to at least one day of credit spend. |
If a reload still fails after these corrections, write to [email protected]. Name the workspace and the date of the failure.
Frequently asked questions
What triggers a RichAPI auto-reload?
A RichAPI auto-reload triggers after a successful API call that charged credits and left the balance below the threshold. RichAPI also requires that 24 hours passed since the last reload.
What is the default RichAPI auto-reload threshold?
The default RichAPI auto-reload threshold is 100 credits, and the default reload pack is 1,000 credits for $20. For production traffic, raise the threshold to at least one day of credit spend.
How often can RichAPI auto-reload charge my card?
RichAPI auto-reload charges the card one time in any 24-hour period. The cooldown is fixed and no dashboard setting changes it.
Does auto-reload rescue a workspace that already hit 402?
Auto-reload does not rescue a workspace that already hit 402. RichAPI checks auto-reload only after a successful billable call, so a workspace at zero credits must buy a credit pack in the dashboard.
Does RichAPI email me about a failed auto-reload?
RichAPI sends no email for a failed auto-reload charge. RichAPI also stops the 90% and 100% credit depletion emails while auto-reload is on. Treat a 402 in your own logs as the alert.
Which credit pack does auto-reload buy?
Auto-reload buys the single pack that you choose in Reload amount on the Auto-Reload card. The six choices are 1,000 credits for $20, 5,000 for $100, 10,000 for $190, 25,000 for $450, 50,000 for $800, and 100,000 for $1,500.
Do the credits from an auto-reload expire?
Credits from an auto-reload never expire. The credits join the organization balance and carry over into every later billing cycle.
Does an auto-reload change my rate tier?
An auto-reload counts as a credit purchase, so RichAPI recomputes the rate tier of the organization after the payment. A large reload pack can raise the requests-per-second limit for the rest of the billing cycle.
Related articles