AdminCP & Account Usage

The AdminCP Artificial Intelligence (AI) section (/admin/core/ai) is where admins decide how much the site may spend on AI, which models run which features, and who may use them. Members see their own allowance at Settings → AI usage (/settings/ai).

Models and their prices are not edited in the AdminCP. They live in vitnode.api.config.ts, next to the provider keys they need. See Model pricing.

First-time setupCopy Anchor Link

AI Setup covers the models and prices you set in code. Everything after that happens in the AdminCP.

Staff permissionsCopy Anchor Link

The AI screens use two staff permissions in the ai module of @vitnode/core. Grant them in Staff → Administrators like any other staff permission.

Without can_manage, the pages are read-only: forms are disabled, write buttons are hidden and the role form has no Artificial intelligence (AI) tab.

SettingsCopy Anchor Link

The Settings button on Artificial Intelligence (AI) → Overview opens a sheet with the rules every run follows. Changes apply from the next run, after you press Save settings. The sheet has its own link, /admin/core/ai?settings=open, so you can send it to another admin.

Switch AI features off and the rest of the sheet hides, because none of it applies while AI is off.

Budgets and allowances are calendar months in the site's time zone (the default language's). The settings sheet shows which one.

Budgets are in USD, because that is what providers bill. Members are charged in AI points. Costs, Points & Budgets explains the conversion and what happens on failure.

ActionsCopy Anchor Link

Artificial Intelligence (AI) → Actions lists every AI action installed plugins register, grouped by the plugin it comes from. Each row shows the action's icon, title and description in your language. Badges appear only when something differs from the default: a chosen model, a daily limit, or a warning that no configured model can run the action. Search by title, description or key, or filter by plugin.

The switch on each row turns the action on or off straight away. A disabled action refuses to run for anyone, and its row fades.

The Configure button (the gear) opens a sheet with the rest:

• Enabled: the same switch as on the row.
• Model and Fallback model: only models with every capability the action needs are listed. Site default is the first compatible model.
• Editorial instructions: up to 2,000 characters appended to the prompt, e.g. house style.
• Limits: runs per member per day, max input characters, max output tokens, retries, steps and timeout. Each one can fall back to the plugin's default.

Press Save action to apply the changes from the next run. An action marked No compatible model, so it can't run needs a model with the right capabilities in vitnode.api.config.ts first.

AI accessCopy Anchor Link

A member's run must pass four separate controls. They answer different questions, so check the right one when somebody is refused:

The permission does not replace content access. An excerpt action still checks that the admin may edit the article.

RolesCopy Anchor Link

Creating or editing a role in Users → Roles shows an Artificial intelligence (AI) tab to admins with ai:can_manage. It sets:

• Allowance: monthly points, Unlimited points, or the site default.
• Features: one row per AI permission, showing the icon, title and description of every action that uses it. Pick Default, Allow or Deny; Allow opens an optional daily limit in the same row. Icons turn grey when the role can't use the feature.

The AI access is saved together with the role, right after it.

A member with several roles gets the largest allowance (never the sum), the broadest permissions and the largest daily limit. Root roles always have access and no point cap, but the site budget still applies to them.

User exceptionsCopy Anchor Link

The AI access card on a member's AdminCP page (Users → a member) gives them their own rule, ahead of their roles: Block AI features, Unlimited points, or a personal monthly allowance. It replaces what their roles give until you remove it.

HistoryCopy Anchor Link

Artificial Intelligence (AI) → History lists every run with its action, status, origin (Members or Background jobs), model, cost and points. Filter by status, origin, action or model. Details shows:

• tokens in and out, cost, cost source and what was charged or reserved;
• every provider call, with retries and fallbacks listed as separate calls;
• cost corrections made by reconciliation;
• whether an editor accepted the suggestion (tracking only, never billing).

Run statuses: reserved, running, succeeded, failed, canceled and uncertain (the process died mid-call; the maintenance cron settles it). The ai-maintenance cron prunes history older than Keep history for.

OverviewCopy Anchor Link

Artificial Intelligence (AI) → Overview answers two questions: will we stay inside the budget? and where does the money go?

• Date range (top right): This month (the default), Last month, the last 7, 30 or 90 days, or any range picked on the calendar. Every number below follows it, and each is compared with the range before it: this month so far with the same days of last month, a whole month with the month before, anything else with the same number of days just before it.
• Budget: what the month has charged to the budget and the share of the limit used, with a mark where an even pace would be today. The bar turns amber at 80% of the limit (or when the forecast goes over it) and red at 90%. The arrows next to the month's name step through earlier months.
  • For this month you get a forecast: what is already charged, plus the selected range's daily average for every day left. Pick Last 7 days to forecast from recent days, or Last 90 days for a steadier average. Going over turns the note amber.
  • For an earlier month you get how it closed, and what a month would cost at the selected range's pace.
• Six numbers: spend, cost per run, runs, failure rate, tokens and the share of runs with a known cost, each with its change. Click one to chart it.
• Chart: for spend, the month's running total against the budget line, with last month dashed and the forecast to the month's end. For the other numbers, a running total (or a running average for rates) across the range, against the range before it.
• Where it goes: the picked number by action or by model, ranked, with a mark for the range before. A run whose model has no price shows Unknown, never $0, and the page tells you how many runs that is.

The range and the budget month live in the URL (?range=7d, ?from=2026-09-12&to=2026-09-25, ?month=2026-09), so a view can be shared with another admin. Days follow the site's time zone, shown in the Settings sheet.

Member page: /settings/aiCopy Anchor Link

Members who can use at least one AI feature get Settings → AI usage. Members without any feature, or on a site with AI switched off, don't see it in the settings menu, and opening the URL shows a not-found page. The page reads only the member's own data:

• Monthly points: points left, the share used and the renewal date. The bar turns amber at 80% used and red at 90%. Unused points do not roll over.
• Your AI features: one row per feature they may use, with today's runs against its daily limit and the points it cost this month. Opening a row loads that feature's latest runs with their status and points. Prompts and generated text are never stored.

The same points bar sits in its own AI points group at the bottom of Settings → Overview, with a link to the full page.

A notice under the points bar explains why AI may not be working, checked in this order:

API routesCopy Anchor Link

Every screen is backed by an API route under @vitnode/core. Use them with fetcher, e.g. fetcher({ plugin: '@vitnode/core', method: 'get', module: 'admin/ai', path: '/overview' }).

Learn moreCopy Anchor Link