Credits
Monitoring credits are a team’s balance for work you start yourself. The plan pays for everything HostRepute checks on its schedule; credits pay for manual scans, the checks you start in the portal, the API or MCP, campaign preflights and AI assistant requests. Credits belong to the team, never expire, and are bought in one-time packages that don’t change the plan.
How credits are used
Section titled “How credits are used”- A member with the Developer role or higher starts the work. Viewers can’t start anything that uses credits. The portal shows the cost before you start.
- HostRepute checks the balance. Without enough credits the work doesn’t start: the portal says how many credits it
needs, and the API answers
402withrequired_creditsandavailable_credits. - Scans, checks and campaign preflights take their credits when they start. AI requests take theirs when the answer, summary or playbook is ready.
- When the work fails, its credits are refunded (see Refunds).
- Every charge, refund and purchase is recorded in the team’s credit history.
When the team has a plan, the team menu at the top of the sidebar shows the balance. Only the Owner can buy credits and change the low-balance settings.
What uses credits
Section titled “What uses credits”| Action | Credits |
|---|---|
| Blocklist scan you start (Manual scan, the API or MCP) | 1 |
| Certificate check you start (portal, API or MCP) | 1 |
| One-off email authentication check | 1 |
| Campaign preflight | 1 |
| AI assistant chat message | 2 |
| AI summary | 5 |
| AI playbook | 10 |
Scheduled monitoring uses no credits: the blocklist scans, certificate checks, uptime checks, domain expiry checks and email authentication checks HostRepute runs on its own schedule are part of the plan, and so is the first scan of a domain or IP you add. Plans and limits lists what each plan includes.
Refunds
Section titled “Refunds”A refund puts the credits back as soon as HostRepute knows the work failed. Whether work counts as failed depends on what it is:
- Manual blocklist scan (portal, API or MCP). Refunded when no blocklist answered, the scan couldn’t finish, or it couldn’t be started. A second manual scan of the same domain or IP while the first is running uses no credit, but every blocklist check started through the API uses one. Read run a manual scan and run checks and wait for results.
- Certificate check started in the portal (Check now, or a bulk check). A check that ends with Couldn’t connect is still a check, so it keeps its credit. It’s refunded only when HostRepute can’t run the check at all. Read monitor TLS certificates.
- Certificate check through the API or MCP. Refunded when the check fails after its retries, which includes a host that can’t be reached on any of its addresses.
- One-off email authentication check. Refunded when the check can’t run. A check that runs and finds problems keeps its credit.
- Campaign preflight. Refunded only when the email couldn’t be checked at all. A preflight that was partly checked keeps its credit. Read check an email before you send it.
- AI assistant. Nothing is charged until the answer, summary or playbook is ready, so a request that fails costs nothing.
Buy credits
Section titled “Buy credits”The team’s Owner buys credit packages. Bigger packages cost less per credit; prices are on hostrepute.com/pricing.
| Package | Credits |
|---|---|
| Starter | 500 |
| Basic | 2,500 |
| Standard | 10,000 |
| Pro | 25,000 |
| Business | 50,000 |
| Enterprise | 100,000 |
| Ultimate | 200,000 |
-
Open Settings, then Plans & billing, then Credits and choose Buy credits.
-
Under Buy credits, choose Buy next to the package you want. The button carries the package’s name.
-
Check the summary, then choose Continue to checkout and pay in Paddle’s checkout.
The credits are added once the payment goes through, and the page says “Credits added to your wallet.” If Paddle’s confirmation takes longer, the page says “Payment received.” and the balance updates when it arrives. Credits stay on the balance when the trial ends or the plan is cancelled.
Low-balance payment links
Section titled “Low-balance payment links”Low-balance payment links email the team’s Owner a link to buy a package when the balance runs low. Nothing is charged automatically: credits are added only after someone pays through the link. The setting is off until the Owner turns it on.
- When a link is sent. HostRepute checks the balance each time work uses credits. Under Send a link when the balance falls below, choose A share of what you bought, a percentage of all the credits the team has bought, or A number of credits. With the percentage, a team that has never bought credits never gets a link.
- Which package. Package to offer picks the package the link pays for.
- How often. While the balance stays low, another link goes out at most every 6 hours. When as many links as Top-ups per month, at most allows have been paid in a calendar month, no more are sent until the next month.
To change it, open the Credits tab, choose Low-balance payment links, switch Email a payment link when credits run low on or off, fill in the fields and choose Save. The portal’s percentage field accepts 1 to 100, but HostRepute saves only 5% to 50%.
| Setting | Default | How to change |
|---|---|---|
| Low-balance threshold, as a percentage | 5% to 50% | Set in billing |
| Low-balance threshold, as a number of credits | At least 1 credit | Set in billing |
| Recharges per month | 1 to 20 | Set in billing |
| Low-balance threshold, default | 20% of the credits bought | Set in billing |
| Package in the payment link, default | Standard | Set in billing |
| Recharges per month, default | 5 | Set in billing |
| Another payment link while the balance stays low | At most one every 6 hours | Fixed |
| Low-credit warning email | When a use leaves 10 credits or fewer, at most once every 24 hours | Fixed |
Credit history
Section titled “Credit history”The History tab shows Credit history: the team’s 12 most recent credit purchases and uses, newest first, each with what happened, the date and the number of credits. The entries are:
- Purchases, from the package grid or a low-balance payment link, naming the package.
- Uses, one per scan, check, preflight or AI request, saying what it was for.
- Refunds, starting with “Refund”, for work that failed.
- Referral credits, from Refer a friend.
- Changes by HostRepute, such as bonus credits or a correction to the balance.
- Chargebacks. When Paddle refunds a credit purchase, or the payment is charged back, those credits are taken off the balance. The balance can then fall below zero, and work that uses credits can’t start until the balance covers its cost again.
These kinds have no labels in the portal. The MCP server’s credit history names them with internal type values, listed under Statuses and what they mean.
When to change the settings
Section titled “When to change the settings”- Turn on low-balance payment links when scripts or CI jobs start checks through the API, so a check never fails for lack of credits while nobody is watching the balance.
- Choose a fixed number of credits as the threshold when your use is steady, and a percentage when it grows with the packages you buy.
- Lower Top-ups per month, at most to cap how many top-ups a month the team can pay for through the links.
Related
Section titled “Related”- Credit costs lists what uses credits and the packages.
- Plans, trial and billing covers what the plan pays for.
- Run a manual scan is the most common use of credits.
- Connect AI clients with MCP lists the MCP tools that use credits.
- Glossary defines a credit.