Credits and usage

Spiich meters the work its agents do in credits. Every workspace has one credit balance, and each thing the assistant does on your behalf draws from it. Credits are what stop an agent quietly running up unbounded work, and they are the number to check first when something says it cannot continue.

This guide covers what spends credits, where each role sees the balance, and how to read the usage history. For what a plan costs, or what a credit is worth, talk to us at contact. Pricing is not published here.

What spends credits

• Contact enrichment: finding an email address, a phone number or a LinkedIn profile.
• Meeting briefings, and the post-meeting CRM update plus follow-up email draft.
• Background agent runs, including leads an agent finds and saves and the scoring it does on them.
• AI and prompt columns in tables, charged per generated cell. See AI and prompt columns.
• Research the assistant does for you on the open web.

Reading records, browsing tables, opening a thread and changing settings do not spend credits. Neither does an attempt that was refused: a background agent run rejected for hitting its daily limit is logged for the audit trail but costs nothing.

At the bottom of Settings > Billing there is a Credit Costs table listing what common actions consume. The exact rows differ between workspaces, so read your own rather than someone else's.

Where you see your balance

The month boundary follows your own timezone, so two people in different offices can see the month turn over at different moments.

Read the usage history

Open the Background Agents page and scroll past the agent table to the usage section. It appears once the workspace has adopted at least one agent.

Usage History is an itemized table with Type, Agent, Record, Charged to, Cost and Date. Expand a row for the breakdown behind a single run. Failed attempts are listed too, labelled Daily limit exceeded or Out of credits, so a gap in your results always has a visible reason. For a run started by hand, the row names both the person who pressed Run and, where they differ, the member the agent acted as.

Analytics adds Used, Remaining and Runs tiles, a daily spend bar chart and a spend-by-agent breakdown over a 7, 30 or 90 day window. Anything past the top eight agents is folded into a single Other row.

Get warned before you run out

Below the usage section, admins can turn on Low credit warning. Switch it on and drag the Warn below slider to a percentage of the monthly credit allowance; the line underneath tells you the exact number of credits that percentage works out to. It saves itself. When the balance drops below that point, Spiich emails the workspace admins.

Non-admins see the current setting as read-only text. The warning needs a monthly credit allowance to measure against, and says so plainly when the workspace does not have one yet.

Bring your own enrichment provider

Enrichment does not have to spend Spiich credits. Under Settings > Integrations there is an Enrichment providers section where an admin can add an API key for Lusha, Wiza, Apollo, FullEnrich or Lemlist. While a key is connected, enrichments run on that provider's credits instead.

Each provider card opens a two-step dialog: Find Key, with the exact steps for that provider's own dashboard, then Connect, where you paste the key. Spiich validates the key against the provider before saving, so a wrong key is rejected there rather than at your next enrichment.

A key on its own is not enough. The team also has to select that provider in Teams, otherwise enrichment keeps running the default way. Members without admin rights see a note asking them to contact their admin.

Limits

• Credits belong to the workspace, not to a person. Team budgets and personal caps are how you divide them up.
• Team budgets and personal caps both apply to every action and the stricter one wins. Budgets reset on the 1st of the month, UTC.
• The daily chat allowance is separate from credits. It covers the Balanced and Expert thinking tiers only; Fast has no daily limit, which is why requests continue on Fast when a share runs out.
• The Credit Costs table differs between workspaces, so a figure quoted from another workspace may not apply to yours.

If something goes wrong

• "You don't have enough credits to process notes." Either the workspace balance is exhausted or the acting person's team budget or personal cap is reached. An admin checks Settings > Billing, then raises the cap in Settings > Team Management.
• Usage History shows "Out of credits" and agents stopped. The workspace ran out. Background agents are paused and admins are emailed. Top up, then re-activate the paused agents and turn on the low credit warning.
• A prompt column cell reads `Paused` instead of a value. The workspace hit its credit limit, so generation stopped. A blank cell would have read as "no answer", so Spiich says Paused instead. Reload once credits are available.
• The Billing entry is missing from Settings. It is admin-only, and hidden entirely on a custom contract. Ask an admin, or contact Spiich for a contract workspace.