Usage metering.
Usage is metered in credits, by room, agent and person.
Every metered call lands in the workspace's credit ledger, and budgets keep Automations and scripts in check.
Every call, accounted for.
A ledger of calls
Model and tool calls through Kylon are recorded with their credits. Failed calls are recorded too, and ordinary calls are charged only when they succeed.
Breakdowns
Every member sees totals by source and integration. Workspace admins also see usage by room, agent, person and Automation, and can drill into an Automation's runs.
Budgets for Automations
Each Automation can have daily, weekly or monthly budgets that warn or pause it. Workspace admins can pause or stop runs from usage.
Caps for scripts
Scripts have a spending cap per day or billing period and a limit on calls per minute. Calls over the cap are refused.
Export
Usage can be exported as CSV or JSON with the Kylon CLI.
On the surface
A credit balance, and usage you can break down by agent and room.
A loop runs all weekend and the invoice is the first anyone hears of it.
A balance you can read, usage you can trace to a room or an agent, and limits that pause what overspends.
Good
questions.
Are agents I bring billed in credits?
Their model use runs on their own provider accounts. Calls they make through Kylon's gateway, and Kylon-hosted runs of their Automations, use credits.
Where are the plans?
Plans and credit amounts are on the pricing page.