LotsBlogYou log into the dashboard, the agent ran a few drafts, and the credit counter is lower than expected. New operators notice this within the first week. The counter moves, there is no obvious receipt for each action, and it is not clear whether the balance resets, refills, or just runs until empty.
Here is exactly what LotsTech Credits are, what each action costs, how the three plan pools compare, and how to set a monthly cap so the system never surprises you.
What LotsTech Credits actually are
LotsTech Credits are the shared ecosystem balance that powers AI actions across the LotsTech stack. Every time the agent drafts a post, refreshes content, runs an analytics check, or suggests an interlink, the system spends credits from your monthly pool.
They are not a subscription upsell or a hidden fee. They are the resource budget for the agent's work inside your blog. The plan you pick determines how big that monthly pool is.
Credit cost per action
The exact credit cost per action depends on the complexity of the operation. Here is how the system categorizes them:
- Drafting a full article — the highest-cost action. The agent researches the brief, writes the full structure (opening, H2 sections, FAQ, CTA), applies the blog voice and tone rules, and saves it as a draft. The operator's playbook for writing a compounding article shows exactly what this workflow produces.
- Drafting a list post — lower than a full article because the structure is lighter and the agent fills items instead of writing prose sections.
- Refreshing an existing post — comparable to drafting a shorter piece. The agent reads the existing content, updates stats, tightens the answer-first paragraph, and saves the revision.
- Creating a brief — low cost. The agent reads strategy context and produces a structured writing direction.
- Analytics fetch and review — minimal cost. Reading the archive state and returning metrics.
- Interlinking pass — low to medium depending on how many posts the agent scans to find the best contextual link targets.
The system is designed so that a typical weekly cadence of 3 posts on the Pro plan uses roughly 30–50% of the monthly pool, leaving room for refreshes, experiments, and rewrites.
Monthly allowance by plan
Each plan includes a monthly credit pool that resets every billing cycle:
- Starter — $9/month — 1,000 credits per month. Enough for a single-blog operator running 1–2 posts per week with occasional refreshes. Includes a 7-day free trial.
- Pro — $24/month — 2,500 credits per month. The sweet spot for most operators. Supports 3 posts per week consistently plus monthly content refreshes. Still includes the 7-day free trial.
- Business — $69/month — 7,000 credits per month. Designed for multi-blog workspaces, agency operators, and teams running multiple agents. 7-day free trial applies.
All paid plans come with a 7-day free trial, so you can test the system before committing. There is no perpetual free tier.
How to budget: what 3 posts/week looks like on Pro
If you are running the standard operator cadence — 3 posts per week on the Pro plan at $24/month:
- Roughly 40–50 credits per article draft
- Roughly 20–30 credits per list post draft
- Roughly 10–15 credits per content refresh
- Roughly 5–10 credits per brief creation
At 3 articles per week (12 per month), you use approximately 500–600 credits on drafting. Add monthly refreshes on 2–3 existing posts (roughly 50 credits) and a handful of briefs and interlinking passes (roughly 50 credits total). That lands at roughly 700–750 credits from a 2,500 pool — well within budget.
The remaining pool covers experiments, rewrites, analytics checks, and the occasional longer piece.
What happens when you run out
If you hit your monthly credit cap before the billing cycle resets:
- Drafts still queue in the system. The agent can still plan and brief.
- Publishing from existing drafts is not blocked — credits are spent on agent actions, not on storage or delivery.
- New agent actions (drafting, refreshing, interlinking) pause until the pool resets or you upgrade to a higher plan.
This design means the blog never goes offline, but the agent stops doing new work until credits refresh.
Setting a monthly cap
Every operator should set a monthly credit cap in the dashboard settings. The cap tells the agent to stop spending when the pool reaches a threshold you define — so you never burn through credits before month end.
Recommended caps by plan:
- Starter: 800 credits (leave 200 for mid-month margin)
- Pro: 2,000 credits (leave 500 for unexpected work)
- Business: 5,500 credits (leave 1,500 for multi-blog variance)
The cap is adjustable any time, so you can raise it during a content push and lower it during a light month. The operator's pre-flight checklist covers what else to check before a publishing push.
FAQ
Can I buy more credits mid-month?
Yes. Additional credits can be purchased from the dashboard at any time. They are typically available in smaller packs so you do not need to upgrade the entire plan.
Do unused credits roll over to next month?
No. The credit pool resets at the start of each billing cycle. Unused credits from the previous month do not carry over. The monthly cap helps you pace consumption so the entire pool is available throughout the month.
Does reviewing a draft cost credits?
No. Reviewing a draft in the dashboard — reading it, leaving comments, approving or rejecting it — does not spend credits. Credits are only spent on agent-generated actions: drafting, refreshing, interlinking suggestions, brief creation, and analytics.
Credits are the resource that keeps the agent working. Understand the budget, set the cap, and the system runs predictably. The 7-day free trial on any paid plan lets you see exactly how your cadence maps to the pool before committing.