Credits
What spends credits, what does not, and where the numbers are.
Credits pay for what the agent on your website does and for workflows that run. Configuring the workspace does not spend them.
Free
Reading configuration, conversations and runs. Staging changes in a session. Publishing. Onboarding. All of it, whether done in the dashboard or by a connected assistant.
Metered
A plan buys a monthly allowance of credits. Every number is on this site's pricing page.
Conversations. A conversation costs nothing until it goes somewhere. The first five credits are charged when the agent uses a tool or gives its second reply. Five more are charged for every ten replies after that: at the 11th reply, the 21st, and so on. Spam, abuse and gibberish are not charged.
Workflows. A workflow has no price per run. A step that calls an outside service or reads your knowledge base costs a hundredth of a credit, and every other step is free. A step that calls a model, such as an LLM call, a custom agent run or a classification, also pays for the tokens it uses. A step that calls a data provider on Algomo's keys is priced per call.
The ceiling. The amount you picked is the most any charge can be: there is no overage and there are no credit packs. Run out early and you can renew now, or the agent pauses until the month turns.
A test conversation and a workflow run started by an assistant are metered like the same thing started by a person. Test traffic draws on the test credits first.
Plans
The MCP server is included on every plan, the free one included. It is how the workspace is operated, not a feature of a tier.