From sign-up to your first audit in about 5 minutes.
Nothing to install. Paste one admin key in your browser and TraxAgent does the rest, every night.
How your key is protected
TraxAgent needs one thing from you: a read-only view of your bill. Here is everything that happens to the key.
- You paste an admin keySent over HTTPS only (TLS with HSTS). Nothing to install.
- Encrypted before it's storedAES-256-GCM, tied to your account. The encryption key lives apart from the database.
- Used only to read reportsUsage and cost reports: token counts and dollars. Shown back to you as the last 4 characters only.
- Gone when you say soDisconnect to delete it at once, or revoke it in your provider's console any time.
Never: reads prompts or outputs, creates keys, changes provider settings, or sits in front of your traffic. Security team can't share an admin key? Use the self-hosted collector (Integrations). Everything we do to keep it safe →
What TraxAgent measures
AI you pay for by usage: API keys used by your apps, agents and CI jobs. Plus Claude Code, Codex and Cursor per developer, and who uses their Claude or ChatGPT Team, Business or Enterprise seat (activity counts, idle seats and what they cost).
What it can't see
Conversation content, anywhere. Personal Claude Pro and Max chat and personal ChatGPT plans, because Anthropic and OpenAI don't report those anywhere TraxAgent can read.
Create your TraxAgent account
About 1 minuteGo to Get a free audit, enter your email, and click the confirmation link we email you.
Create an admin key at your provider
About 2 minutesClaude (Anthropic): in the Claude Console open Organization → Admin API keys and click Create Admin API Key, named “TraxAgent”. It starts with
sk-ant-admin01-. Only organization admins can create one. On Claude Enterprise, the primary owner creates an Analytics API key in claude.ai under Organization settings → API instead.OpenAI: in the OpenAI platform open Settings → Organization → Admin keys and create a key named “TraxAgent”. If it offers permissions, read-only is enough. It starts with
sk-admin-.Free connects one provider. Every paid plan connects both.
Paste it into TraxAgent
30 secondsOpen Connections, paste the key and click Connect. TraxAgent checks the key, reads your last 30 days of usage and costs, and opens your dashboard, usually in a minute or two.
That’s the whole setup. TraxAgent refreshes every night on its own, so new leaks show up the next morning and savings are measured automatically.
Read your audit
As long as you likeCost explorer shows where the money goes. Recommendations lists every fix in dollars per month with the steps to ship it. Set a fix to In progress or Done as your team works through them.
Prove the savings
After fixes shipYour first read is the baseline. Verified savings compares every nightly read against it, cost per million tokens on every key, so growth in traffic never counts as savings.
Optional: teams, reports and agents
When you need them- Teams: give each Anthropic workspace or OpenAI project to a team to split spend and fixes (paid plans).
- Reports: print, save as PDF, download CSV or send finance a read-only link.
- API and MCP: create a read-only token and connect TraxAgent to Claude Code or your own tools.
- Pull request check: add the token as a repository secret and copy the GitHub Actions workflow; each pull request gets a cost comment.
- Cost by tag: send token counts and tags from your code to see cost per feature, pipeline or customer, and cost per task with a task_id.
Problems people hit, and the fix for each
Kept up to date from real support cases. The Connect expert on your Connections page knows all of these and can read your own connection's error.
Claude
"This key can't read usage reports" with "Missing permissions", or the Admin keys and Members pages show "Page not found".
Why: The Console account is an Individual account. Anthropic doesn't give Individual accounts the Admin API, so there are no admin keys, no members, and no usage reports. The organization is named "…'s Individual Org".
Fix: In the Console open Settings → Organization. At the bottom, click Convert to team. This keeps the same organization ID, keys, usage history and credits. Afterwards the Admin keys and Members pages appear and you're the Admin.
"didn't accept this key" with "The Admin API requires an Admin API key or an organization-scoped API key".
Why: The key was created with a workspace scope (Default or a named workspace). Usage reports are organization-level, so a workspace key can't read them.
Fix: Create an Admin API key instead: Settings → Admin keys → Create admin key. It starts with sk-ant-admin01-. If you use a personal key (sk-ant-usr…), choose scope Organization when creating it, not a workspace.
"Missing permissions" on a key from a team organization.
Why: The account that created the key isn't an Admin of the organization. A personal key has exactly the permissions of its account.
Fix: Ask an Admin to change your role on Settings → Members, or to create an Admin API key for TraxAgent.
"That's a workspace API key" when pasting an sk-ant-api03-… key.
Why: Regular API keys call models; they can't read organization reports.
Fix: Use an Admin API key (sk-ant-admin01-…) from Settings → Admin keys.
Connected, but "There's no usage in the last 30 days yet".
Why: The organization has no API usage. Claude Pro, Max and chat usage is not API usage and never appears in these reports.
Fix: Nothing is wrong. Use the Claude Code connector for Claude Code on subscription seats, and the dashboard fills in once apps, agents or developers use API keys.
OpenAI
"That's a project API key" when pasting an sk-proj-… key.
Why: Project keys call models; organization usage needs an Admin key.
Fix: platform.openai.com → Settings → Organization → Admin keys → Create admin key. Paste the secret key, which starts with sk-admin- (shown once, at creation), not the key ID that starts with key_.
OpenAI says the key can't read usage, or the Admin keys page is missing.
Why: Only organization Owners see Admin keys.
Fix: Ask an Owner on Settings → Organization → Members to create the admin key, or to make you an Owner.
Claude Code
Claude Code token created, settings in place, but nothing shows under Developers.
Why: Telemetry isn't reaching TraxAgent: the settings file isn't being read, the token doesn't match, or Claude Code wasn't restarted.
Fix: Restart Claude Code fully. Check the status line shows a cost figure (that proves the script runs). Run `claude --debug` briefly and look for otlp lines with 401 (token mismatch: paste the settings again) or 400. Check CLAUDE_CODE_ENABLE_TELEMETRY is "1" inside "env".
Usage arrives but the 5-hour and weekly limit bars stay empty.
Why: The limit bars exist only for Pro and Max sign-ins, or the status line script isn't installed, or jq is missing.
Fix: Check the status line in Claude Code shows "5h NN%". If not, confirm ~/.claude/traxagent-statusline.sh exists and is executable, and that `which jq` finds jq. API-billed accounts have no limit bars.
A developer appears as user@hostname or account:… instead of their email.
Why: The status line uses git's user.email; telemetry uses the Claude sign-in email when available.
Fix: Run `git config --global user.email you@company.com` on that machine.
All
A yellow bar says the key was rejected or expired.
Why: The key was deleted, rotated or reached its expiry date.
Fix: Create a new key the same way as before and paste it on Connections. Set the expiry date there to get reminders 14, 7 and 1 days ahead.
Cursor
"This doesn't look like a Cursor usage export" after dropping a file.
Why: The file isn't Cursor's usage CSV (for example the invoice, the members list, or a spreadsheet that was re-saved with different column names).
Fix: Open cursor.com/dashboard → Usage, pick the date range, press Export CSV and drop that file without opening it in Excel first. Its columns start with Date, Kind, Model and token counts.
Some Cursor models show tokens but $0, or the total looks low.
Why: Models without a public price (Auto, Cursor's own models) can't be valued at list price. Cursor also moved self-serve plans to token-based usage in 2026, so included usage has no dollar figure in its export.
Fix: Nothing is wrong. TraxAgent counts those tokens and values the rest at list price per model, the same way as Claude Code. On-demand charges Cursor billed show in the Charged by Cursor column.
"Cursor didn't accept that key" when connecting the team.
Why: The key isn't a team Admin API key, it was revoked, or the team's plan doesn't include the Admin API (Cursor lists it for Enterprise teams in its docs).
Fix: A Cursor team admin creates an Admin API key on the API Keys page of cursor.com/dashboard. If the team's plan has no Admin API, use the CSV upload instead: each developer exports their own usage, no admin needed.
The developer isn't a Cursor team admin and can't make a key.
Why: Only Cursor team admins can create Admin API keys.
Fix: Either upload your own usage CSV (option A, no admin), or press Ask your Cursor admin: it makes a ready-to-send message with a one-time link where the admin pastes the key without a TraxAgent account. The link works once and expires in 7 days.
Claude seats
"Anthropic didn't accept that key" on the Claude seats card.
Why: It's a Console Admin API key (sk-ant-admin01-…) or an ordinary API key. Seat data needs a Claude Enterprise Analytics API key, a different key type made in claude.ai.
Fix: The Claude organization's primary owner opens claude.ai → Organization settings → API, turns on API access, and creates an Analytics API key (scope read:analytics). Paste that one.
Organization settings → API is missing or the create button is greyed out.
Why: Only the primary owner of a Claude Enterprise organization can turn on API access and create Analytics API keys.
Fix: Press Ask your primary owner on the Claude seats card. It makes a message with a one-time link; the owner pastes the key there without a TraxAgent account.
A Claude Team admin can't find an API page in claude.ai.
Why: Claude Team has no analytics API; it's an Enterprise feature.
Fix: Use option B: in claude.ai → Admin settings → Members (or Analytics), export the CSV and drop it on the Claude seats card. A file with a last-active column lets TraxAgent spot idle seats. Upload again monthly.
Connected, but yesterday's seat activity is missing.
Why: Anthropic publishes a day's analytics around 13:00 UTC the next day, and data starts January 1, 2026.
Fix: Nothing to do. TraxAgent rereads the last few days every night, so the gap fills itself.
ChatGPT seats
Can't find where to export ChatGPT seat usage.
Why: The export lives in the ChatGPT admin area, visible to workspace admins and owners only.
Fix: In ChatGPT open Workspace settings → Analytics → User analytics, choose the last 30 days and export the CSV. Not an admin? Press Ask your ChatGPT admin on the ChatGPT seats card: it makes a one-time upload link, no account or key needed.
"Why doesn't ChatGPT use an API key like Claude Enterprise?"
Why: OpenAI's only API for workspace data is the Compliance API, which returns conversation content and files. TraxAgent never reads conversations.
Fix: Use the user analytics CSV. Upload it monthly to keep idle seats current; add your price per seat to see idle seats in dollars.
Uploaded, but idle seats show as unknown.
Why: The file has no last-active column (for example a plain member list).
Fix: Export User analytics rather than the members list; it includes last activity per person.
TraxAgent
"We couldn't send the email" on sign-up or sign-in.
Why: TraxAgent's email service is unavailable for a moment.
Fix: Wait a minute and try again. If it continues, write to support@traxagent.io.