Timekeeper connects AI request accounting to a firm, case, product and model tier. Case teams can review usage; administrators can manage case and firm-wide spend policies.
Set spend policies and review firm-wide usage without reading source records.
Review usage for cases they can access, with partial pricing identified.
Distinguish reference-rate estimates, reserved amounts and completed request accounting.
The receipt beside each step is an illustrative example of what a reviewer sees, not data from a real case.
Open Timekeeper from a case and choose a UTC accounting month. Review request counts and estimated usage grouped by product and model tier.
case · accounting month · product · tierAdministrators can switch to firm-wide accounting. Other members see only the case view permitted by their case access.
case access · administrator-only firm viewAdministrators can create, edit and archive case or firm-wide limits, optionally narrowed to a product and model tier. Policy changes require recent authentication and are audited.
scope · limit · revision · auditEnabled policies reserve a bounded estimate before a gateway request. Retries have their own accounting. A reached limit or a cost that cannot be bounded blocks the request rather than bypassing the policy.
reservation · request attempt · limit decisionRequest accounting settles against reported token usage where pricing is known. Missing pricing remains visibly partial instead of appearing as zero-cost usage. Prompts and record content are not copied into the usage ledger.
reported usage · reference rates · pricing gapsSee how Timekeeper fits your case review. Sign in to your firm's workspace or request a walkthrough.