Token Thrift
  1. Ask
  2. Cost and budgets
  3. Cost
  4. Your account
Started by Token Thrift

Cost / 3 public sources

How do agencies bill AI usage to clients?

Add your answer

Loading replies.

Add your answer

Don't paste anything your employer treats as confidential. Before anything is posted, we take out names of people, your company, its clients and internal projects, plus places and exact numbers, and show you the result to check. Your raw text is never stored. To redact it, we send it to Anthropic's API, which doesn't train on API data by default.

How Ask protects you

  • You post under a random handle. No name or employer is shown, and your email is never shown to anyone.
  • Before a reply is saved, a model removes names, employers, clients, places and exact figures, a fixed leak check reads it again, and you approve the result. Your raw text is never stored. It is sent to Anthropic's API for this step. Redaction lowers the risk; it is not a guarantee.
  • Follow-up questions are passed on by email, and neither person sees the other's address. You can answer privately.
  • A handle's first reply is reviewed before it is published.
  • Replies that are never published are deleted after 30 days. Deleting your handle removes your email; published replies stay up as anonymous text.

More in the privacy policy and the FAQ.

What you get for replying

  • A digest of everyone else's answers on that topic, at most one email a day, one click to stop.
  • A count of replies readers marked helpful, shown next to your handle.
  • Credit by handle in the monthly roundups when your answer is used.

Tips to stay hard to recognize

  • Describe your company by size and industry, not by name, product or city.
  • Leave out unusual tool combinations or internal project details only your team would know.
  • Round numbers and timelines yourself, even though redaction also does it.
  • Wait a while before writing about something that was just announced inside your company.
  • Redaction doesn't change your writing style, so a coworker with context could still recognize you.

Summary of public sourcesWritten by our research agent from 3 public sources. Not first-hand experience.

Agencies and consultancies that move to usage billed AI plans now get one invoice for work spread across many clients. A recent public thread describes a small agency whose bill rose after switching plans. It tagged coding sessions by repository with OpenTelemetry and got a cost figure per repo, but that figure did not match the invoice. Chat work by project managers was not captured, and sessions in folders with no git remote carried no repo tag. Claude Code's docs confirm the mechanics: it can export cost and token metrics, custom resource attributes can carry a team or cost center, and repository attributes are left out when there is no origin remote. Admins can push the telemetry settings to everyone through managed settings.

Replies split into two camps. One says not to pass usage through at all: build AI into the rate or a flat tooling line, use telemetry only as an internal margin check, and price agent heavy work per deliverable. The other wants exact attribution: a separate API key or project per client, a proxy that adds a client tag to every call, a session start hook that warns when no remote is set, or an export from the vendor's compliance and analytics APIs. Anthropic's Enterprise page says seats cover access only and all usage is billed at API rates, with spend limits at the organization and member level.

Still open: no one in the thread had a clean way to attribute chat work that is not tied to a repo, and it is unclear whether clients accept AI as a line item or prefer it hidden in the rate.

Sources

  • Reddit: How are agencies billing Claude Enterprise usage back to clients?
  • Vendor docs: Monitoring | Claude Code Docs
  • Vendor docs: What is the Enterprise plan? | Claude Help Center