For AI service providers · Guide
How to monitor AI agent costs by client
Track client cost by tying each accepted deliverable to its workspace, run and external charges. Review Agentic Workers workspace billing, then add costs paid directly to other providers and the effort needed to review the result. Do not assume a single consolidated client margin report.
By Agentic Workers Team · Published · Updated
Responsibilities and evidence
Agree on the owner and retain a safe evidence reference for each responsibility.
- Service scope
- Provider drafts; client accepts. Evidence: agreed output and stop conditions.
- Account ownership
- Client and provider confirm owners. Evidence: account inventory without secret values.
- Configuration
- Provider sets up the intended workspace and agent. Evidence: reviewed settings.
- Action review
- Named reviewer checks supported actions. Evidence: request and decision.
- Acceptance
- Client or delegated reviewer checks the result. Evidence: accepted artifact.
- Exit
- Account owner and provider remove access. Evidence: handoff and denied-access check.
1. Choose the accounting boundary
Record the client workspace, billing owner and source provider accounts. Decide how shared costs will be allocated and label that rule as an assumption. Keep the same rule during a pilot so comparisons remain meaningful.
2. Reconcile the work
For each expected run, record whether it produced an accepted result, a retry or a failure. Compare available run and usage evidence with workspace billing and external invoices. Do not count a failed attempt as a delivered client outcome.
3. Act on the difference
Investigate unexpected volume, large inputs and repeated retries. Pause or change the process through its normal controls when needed. Recheck the next run and update the client’s service scope if the workload changed.
Example provider workflow. Adapt it to the client’s agreed scope.
- 01
Step 1: Choose the accounting boundary
- 02
Step 2: Reconcile the work
- 03
Step 3: Act on the difference
Fit and limitations
- Good fit
- Providers applying this process to an agreed client service.
- Poor fit
- Treating this checklist as an automatic product feature or a substitute for a client agreement.
- Known limits
- These are operating recommendations. Test each supported product path in the target workspace and plan. Examples are not performance, pricing or security benchmarks.
Sources and evidence
Documentation establishes the scope of a claim. It does not replace an acceptance test in your client’s environment.
| Source | What it supports | Checked |
|---|---|---|
| Current plans and billingProduct documentation | Confirm current plan eligibility and separate third-party usage. No numeric pricing comparison is made here. | |
| Read an agent run recordProduct documentation | Inspect available tool calls and execution details within the relevant workspace. A completed run is not proof of an accepted result. | |
| Schedule a recurring jobProduct documentation | Configure and test the schedule, time zone, agent and supported result destination. |
Questions providers ask
Who is responsible for the result?
The provider names an operator; the client names the person who can accept the deliverable. The platform does not replace those responsibilities.
What evidence should we retain?
Keep the source date, workspace and agent, expected output, review decision and artifact reference. Exclude credentials and unnecessary personal data.
When should we stop and review?
Stop when the account, recipient, output or permissions differ from the agreed scope, then resolve the exception before continuing.
Set up one client service
Set up the client workspace, connect its tools and review the first deliverable. Use a tested delivery path, such as Telegram, so the client can receive work in chat. Track operating costs and review effort before pricing a recurring service.
Sign up now