Credit usage
Every operation on the Weeki platform consumes credits. This page details exactly how many credits each operation type uses, so you can estimate and control your costs.
A credit is the unit of AI and compute: an agent turn costs at least 3, a minute of compute 1 to 45 depending on the cluster. No commitment.
The agent and the AI assistants
Credits consumed when a model works for you: a conversation turn, a background task, an assistant reply.
| Operation | Credits | Unit | Notes |
|---|---|---|---|
| Agent conversation turn | 3+ | per turn | 3 credits at least; a long turn (many steps, tools) is billed in proportion to its real model cost |
| Background agent task | 3+ | per turn | Same rule as a conversation turn; daily budgets per agent |
| AI assistant reply (LaTeX, code, data, Doc, Plan, Academy) | 10 | per reply | Billed only when the reply succeeds |
| AI call in a workflow (DAG node) | 10 | per call | Same rate as an assistant reply |
Compute, by the second
Notebooks, workflows, code repositories and SQL run on a cluster you choose; the time is billed by the second, with a minimum per run — even when the run fails.
| Operation | Credits | Unit | Notes |
|---|---|---|---|
| Cluster XS — 1 vCPU, 1 GB | 1 / min | by the second, min. 1 | Notebooks, workflows, code repositories, SQL on a dataset |
| Cluster S — 2 vCPU, 4 GB | 3 / min | by the second, min. 1 | Notebooks, workflows, code repositories, SQL on a dataset |
| Cluster M — 4 vCPU, 8 GB | 8 / min | by the second, min. 2 | Notebooks, workflows, code repositories, SQL on a dataset |
| Cluster L — 8 vCPU, 16 GB | 20 / min | by the second, min. 5 | Notebooks, workflows, code repositories, SQL on a dataset |
| Cluster XL — 16 vCPU, 32 GB | 45 / min | by the second, min. 10 | Notebooks, workflows, code repositories, SQL on a dataset |
Free of credits
Everything else does not consume credits.
| Operation | Credits | Unit | Notes |
|---|---|---|---|
| Boards, maps, documents, plans | 0 | — | Editing and collaboration |
| Templates placed on a board | 0 | — | Deterministic placement, no model call |
| Connected accounts and imports | 0 | — | M365, Google Drive, Confluence and the other connectors |
| Store items (courses, templates) | 0 | — | Paid in euros when they are not free, never in credits |
Credit Pricing
The Pro plan includes 500 credits per user per month. Beyond that, you top up credits at €0.05 excl. VAT each; large volumes are negotiated.
| Monthly Volume | Price / Credit |
|---|---|
| First 500/user each month (included in Pro, not carried over) | Included |
| Beyond: top-up | €0.05 excl. VAT |
| 500,001+ or annual commit | Custom |
Estimate your monthly cost
Select a use case and adjust the parameters to estimate your monthly credit consumption and cost.
Organization using RAG, search, and AI assistant for internal knowledge management.
How credits work
- Billing. Credits are consumed as you use them — by the second for compute. Nothing is charged when idle, and nothing after the fact: included credits arrive each month, top-ups are paid in advance.
- Included credits. The Pro plan includes 500 credits/user/month. Unused credits do not roll over.
- Overage. Beyond the included quota, an action starts if your topped-up balance covers it. The subscription owner pays for the team and can set a monthly limit for each person.
- Enterprise. Annual credit commits with custom pricing are available. Contact us for volume discounts.