Tracking third-party tool usage on Claude Max is two fields, not one, since April 4, 2026

At noon Pacific on April 4, 2026, Anthropic stopped covering third-party tool usage under the flat Max subscription. Cline, Roo Code, aider, OpenCode, OpenClaw, Cursor, and anything else that authenticates with a Claude OAuth token (or relays your session) now bills at per-token API rates against your extra_usage balance. Claude Code and claude.ai are still inside the plan. Anthropic gave Max users a one-time $200 credit with an April 17 deadline; after that, third-party tool calls draw real dollars from the pay-as-you-go pool. Source: support.claude.com/en/articles/12429409-manage-extra-usage-for-paid-claude-plans, and Anthropic's pricing page.

Because the field exists on every Max account's /api/organizations/{org}/usage response regardless of how the billing routes. seven_day_oauth_apps tracks utilization attributed to OAuth-connected app traffic against an internal weekly cap that the server still maintains for accounting and rate-shaping. The field stays at zero on accounts with no OAuth integrations and ticks up when integrations are connected. The dollars-out side of third-party tools sits in the extra_usage block in the same payload, with used_credits and monthly_limit. Watching either one alone gives a partial answer.

Two places on the same private endpoint: /api/organizations/{org}/usage carries the extra_usage block ({ is_enabled, monthly_limit, used_credits, utilization, currency }) and /api/organizations/{org}/overage_spend_limit carries the canonical month-to-date used_credits and the monthly_credit_limit you set. claude.ai/settings/usage renders both. ClaudeMeter parses both into Rust structs (ExtraUsage and OverageResponse in src/models.rs) and shows them next to the seven Window buckets, so you can see plan-quota exhaustion and dollars-spent at the same moment.

No. ccusage and Claude-Code-Usage-Monitor walk ~/.claude/projects/*.jsonl on disk; that ledger only exists for Claude Code itself, which writes those JSONL transcripts locally. Cursor, Cline, Roo Code, aider, and OpenCode do not write to ~/.claude/projects, so a local-log reader literally never sees them. The only place those calls show up is on the server: as movement on seven_day_oauth_apps (when the integration uses OAuth) and as used_credits ticking on the extra_usage block. ClaudeMeter and ccusage measure different things; they coexist rather than compete.

Because $200/month Max users were running thousands of dollars of agentic work through third-party tools under the flat fee before April 4. The change repriced that work, and the same users who built workflows around it now need a live read on two numbers they did not need to watch before: how much OAuth-app utilization they have left this week, and how many dollars they have spilled into metered billing this month. The official UI shows both but you have to keep refreshing the page; the third-party tracking category exists to put them in a sticky surface.

Yes, on the Max-via-OAuth path. Cursor's 'Bring your own subscription' flow authenticates against your Claude account; after April 4 the calls it makes bill against extra_usage at per-token rates rather than coming out of your flat Max allowance. You'll see them show up as dollar movement on extra_usage.used_credits. The seven_day_oauth_apps bucket may also tick depending on how Cursor's integration is structured. If you point Cursor at a separate Anthropic API key instead, those calls don't touch your Max account at all and don't appear on /api/organizations/{org}/usage.

Yes. Sign in to claude.ai, open DevTools at claude.ai/settings/usage, copy the full Cookie header on the /usage request, grab your org UUID from /api/account memberships[0].organization.uuid, and run: curl -s claude.ai/api/organizations/$ORG/usage with the Cookie header you copied and a Referer header pointing at claude.ai/settings/usage. The Referer is load-bearing; drop it and you get 403. The JSON you get back has seven Window objects (five_hour, seven_day, seven_day_sonnet, seven_day_opus, seven_day_oauth_apps, seven_day_omelette, seven_day_cowork) and the extra_usage block. That single curl is a faithful snapshot; the reason a poller is worth installing is that the rolling denominators slide as old traffic ages out, so the numbers drift between snapshots.

Yes. MIT-licensed Rust core for the macOS menu bar app, Manifest V3 JavaScript for the browser extension, source at github.com/m13v/claude-meter. There's no telemetry: a single HTTPS request per minute to claude.ai with your own session cookie. The extension reads the same private endpoint claude.ai/settings/usage renders from, so the numbers match the official page exactly.

Today the menu bar surface is macOS 12+ only. The browser extension targets Chrome, Arc, Brave, and Edge (Manifest V3). Safari and Linux/Windows menu bar are not on the roadmap. If you're outside the macOS+Chromium combo, the practical fallback for tracking the same two fields is to keep claude.ai/settings/usage open in a tab, or run the curl above on a cron. ClaudeMeter just removes the manual refresh; it doesn't change the underlying data source.