Sync Claude.ai Team spend with Cowork

---
name: antenna-team-spend-sync
description: "Uploads Claude.ai Team spend to Antenna. Exports the spend report from the claude.ai analytics page one day at a time for each day Antenna is missing in the last 90 days, uploads each day with the Antenna connector, then uploads the current member list. Use for 'sync Claude Team spend to Antenna'."
---

# Sync Claude Team spend to Antenna

Claude.ai Team plans have no usage or cost API. The billed numbers are in the spend report on the analytics page, and seat tiers are in the Members page export. This skill exports both with the pages' own Export buttons and uploads them to Antenna through the Antenna connector. Antenna validates each file, keeps the history, and reports which days are still missing.

## Prerequisites (check first; stop and tell the user if any fail)

- The user is a Team **Owner** or **Primary Owner**. Admins cannot see or export the spend report.
- The **Antenna** connector is connected and its tools `claude_team_cost_status`, `claude_team_cost_upload` and `claude_team_members_upload` are available. If they are missing, the user must disconnect and re-add the connector in Antenna to approve the new access (an Antenna admin is required).
- The browser Claude drives is signed in to claude.ai, on the Team organization being synced.
- Claude can read the browser's download folder (usually `~/Downloads`). If it can't, ask the user to connect that folder.
- Only use the real Export buttons on visible pages. Never call claude.ai private endpoints directly and never handle session cookies.

## Steps

1. **Ask Antenna what is missing.** Call `claude_team_cost_status`. If it lists several Claude sources instead, use the source ID the user gave in the prompt ("for source 8941"). Otherwise show each source's ID and last uploaded day, tell the user the ID is the number at the end of the source's page URL in Antenna (**Settings** > **Sources** > **Configure** on the Claude.ai Team source, e.g. `/claude_apps/8941`), and ask which to use; in a scheduled run, stop and report this instead. Call it again with that ID as `claude_data_source_id`. Note `window.start_date` and `window.end_date` (yesterday, UTC), each organization's `missing_dates`, `uploaded_days`, and `member_lists`.
2. **Find this organization.** The organization is the `<org>` in the spend report file name, `spend-report-<org>-YYYY-MM-DD-to-YYYY-MM-DD.csv`. If the status lists exactly one organization, use it. Otherwise, export one day (step 4) and read `<org>` from the downloaded file name. An organization that isn't listed is missing every day in the window.
3. **Choose the days.** Take this organization's missing days. Also re-export its newest uploaded day if it was uploaded less than two days after that day ended, because the report refreshes with a one-day delay and that day may have been incomplete. Process at most 14 days per run, oldest first, so days that are about to leave the 90-day window are saved first. Say how many days are left for the next run.
4. **Export one day.** Open https://claude.ai/analytics/overview, scroll to "How much is Claude costing?", click **Export spend report**, choose **Custom**, and set the start and end to the same day (click the month part of each date field and type the digits as MMDDYYYY). Check that both fields show that day, then click **Download**. Wait for the download to finish (the button shows "Downloading…" and the dialog closes) before starting the next day, or the browser may block later downloads. The report has no date column, so each file must cover exactly one day.
5. **Upload the day.** Read the downloaded file and call `claude_team_cost_upload` with:
   - `csv`: the file contents exactly as downloaded, header row included. Do not retype, reorder or round values.
   - `date`: the day, `YYYY-MM-DD`.
   - `claude_organization`: the `<org>` from the file name.
   - `file_name`: the downloaded file name.
   A file with only the header row is valid: that day had no usage beyond the seats. If Antenna refuses the file, record the day and the reason, and continue with the next day. Uploading a day again replaces that day's report.
6. **Upload the member list.** Once per run, after the spend days: open https://claude.ai/admin-settings/members and click **Export CSV**. Call `claude_team_members_upload` with the file contents as `csv` and the downloaded file name (`members-<organization ID>-YYYY-MM-DD.csv`) as `file_name`.
   - Leave out `tier_prices`: each seat tier keeps the price Antenna already has.
   - Only on a run the user is watching, and only when `member_lists` had no list for this organization, ask the user each seat tier's monthly price and pass them as `tier_prices`. A scheduled run never asks.
7. **Report.** Finish with a short summary: days uploaded with their user counts and net spend, days refused with the reason, days still missing, and the member list uploaded (member and Active counts). Do not paste emails or file contents into the chat.

## Rules

- Antenna uses net spend. Never edit the CSV.
- The spend report covers only usage beyond the seats. Seat fees come from the member list and the seat prices in Antenna.
- The CSVs contain member emails and account IDs. Send them only to the Antenna connector; do not copy them anywhere else. Leave the downloaded files where they are; do not delete them.
- If the spend report is missing from the page (no extra usage enabled, or the user is not an Owner), stop and explain. Do not try workarounds.
- If the browser can't open a page, set the date range or download a file, or a Save As dialog or a prompt to allow claude.ai to download multiple files appears during a scheduled run, stop and report exactly which step failed. In the report, tell the user to turn off **Ask where to save each file before downloading** in `chrome://settings/downloads` and add `claude.ai` under **Allowed to automatically download multiple files** in `chrome://settings/content/automaticDownloads`.

## Running it on a schedule

A skill can't create a schedule. After a successful first run, the Owner says "do this every week" (or uses **Scheduled** > **New task**) and Claude creates the scheduled task. Weekly is enough: the report keeps 90 days, and each run fills every missing day. The browser step needs the Claude Desktop app open and online on the Owner's computer, and the browser signed in to claude.ai.