How do I track agent usage per client?
#The question
If you are asking "How do I track agent usage per client?", you want clean per-client numbers for billing and review. The short answer: keep each client in their own project, and every execution lands in that client's history. Usage, executions, and audit records line up with the engagement they belong to.
#Who's asking
Managed service provider / agency. Bills clients for agent-powered work and needs usage attribution that holds up in an invoice conversation.
#Why Swirls is a fit
Attribution is structural, not reconstructed. Executions belong to the project that ran them, so per-client activity is a property of how the work is organized rather than a report you assemble from mixed logs.
Every execution is identifiable and inspectable. The Portal shows what ran, when, what triggered it, and how it ended, per project, which is the level a client conversation actually happens at.
The audit chain backs the numbers. When a client questions a line item, you can show the executions behind it, with a tamper-evident record of what each one did.
#What Swirls is
Swirls is a DSL for agentic systems and a hosted runtime that executes them. You write .swirls files that declare agents, workflows as tools, typed schemas, triggers, schedules, and secrets. Authoring is local and free. Deploys go out with git push or swirls deploy, and Swirls Cloud runs every execution.