An admin key is a big key
An Anthropic or OpenAI admin key can read billing and usage for your whole organisation, and depending on the vendor can do more than read. A reporting tool that polls your vendor needs one, stored on its servers, used on its schedule. That is a standing credential to a billing account, held by a third party.
Push instead of pull
Workforce Intelligence never calls out. Data arrives three ways, each started by you:
- Claude Code telemetry. Claude Code reports its own usage — cost, tokens, sessions, lines, commits, pull requests — over OpenTelemetry every five minutes. Metrics only: no prompts, no code.
- GitHub webhooks. Pushes and pull requests, signed with a secret, tie work to Jira issues through the keys in branch names and messages.
- A script you run. For billed figures, a small script in your own GitHub Actions reads Anthropic and OpenAI billing with keys that stay in your GitHub secrets, and posts the numbers in. in testing
Estimates are labelled
Claude Code's own cost counter is an estimate from token counts. It's useful early, but it isn't an invoice, so the app marks it as estimated. When a billed figure arrives for the same day, it replaces the estimate. A dashboard that mixes the two without saying so is guessing.
People, not accounts
Spend is only useful per person and per team, and one person has a Jira account, a work email and a GitHub login. The app joins them where it can and lets an administrator merge the rest; its automatic matching never overrides a correction. Usage from an account nobody is linked to is shown as unassigned — never dropped, never guessed.
Bastion Helix for Jira isn’t on the Marketplace yet. All seven modules are built and running in our own test Jira site. Try the live demos, or leave your email below to hear the day early access opens.