Claude Code statusline that reads Anthropic Claude Code Analytics Admin API data and shows daily estimated cost, hourly pace, sessions, and budget pressure.
Open the source and read safety notes before installing.
Source-backed facts for citing this resource, derived directly from the registry — also available as plain text for AI assistants.
Decision playbook
Signals are present but mixed. Use the checklist below to confirm the source and operational safety for your environment.
0
78
—
No baseline selected
No major trust-signal divergence detected in the current selection.
Confirm ownership and provenance before trusting install instructions.
Source link availableRequired
Open the canonical repository and verify ownership.
Source provenance statusRequired
Marked as source-backed.
Metadata reviewed
Registry metadata indicates a reviewed listing.
Validate risk disclosures before installation or API wiring.
Safety notes presentRequired
Review the listed safety guidance before running commands.
Privacy notes presentRequired
Review data handling notes before connecting accounts or secrets.
Trust level risk gateRequired
Trust level does not block evaluation.
Check package metadata and artifact integrity signals.
Install payload available
Install or copy payload is available for review.
Package verification flag
No package verification flag provided.
Checksum metadata
No checksum provided for downloaded artifact.
Use compare context to validate trade-offs before adoption.
Compare tray has multiple entries
Add at least one more entry to compare trust differences.
Baseline comparison available
No baseline peer selected yet.
Diverging trust signals identified
No major trust-signal divergence found.
Setup at a glance
Copy-ready — paste the snippet to get started.
Adoption plan
Current risk score 16/100. Use staged verification before broader rollout.
Validate source and review signals before any execution.
Confirm source provenanceRequired
Source URL/provenance metadata is present.
Confirm metadata review state
Listing has review metadata.
Verify install payload
Install/config payload exists and can be inspected.
Confirm safety, privacy, and package integrity signals.
Review safety notesRequired
Safety notes are present.
Review privacy notesRequired
Privacy notes are present.
Verify package integrity metadata
No package verification/checksum metadata.
Adopt in controlled steps based on the selected plan.
Run in isolated sandbox firstRequired
Use a constrained sandbox and observe behavior across multiple tasks.
Roll out graduallyRequired
Roll out to a small cohort before wider usage.
Set monitoring and fallback
Define rollback path and monitor errors after adoption.
Evidence readiness
Required evidence gates are covered (5/6 signals complete).
Source repository/provenance is listed.
Required in this preset
Review metadata is present.
Required in this preset
Safety notes are present.
Required in this preset
Privacy notes are present.
Optional in this preset
Package integrity metadata is missing.
Optional in this preset
Install payload is available.
Required in this preset
Required evidence gates are covered for this preset.
Decision timeline
5/6 steps complete with no blocking gaps for this preset.
triage
Source/provenance metadata is available.
triage
Review metadata is available.
verify
Safety notes are available.
verify
Privacy notes are available.
verify
Package integrity metadata is missing.
rollout
Install payload is available.
No required blockers for this timeline preset.
Prerequisite readiness
4 prerequisites to line up before setup. Have accounts and credentials ready first.
Safety & privacy surface
3 safety and 4 privacy notes across 4 risk areas. Review closely: credentials & tokens, permissions & scopes.
#!/usr/bin/env bash
set -u
main() {
if [ -z "${ANTHROPIC_ADMIN_API_KEY:-}" ]; then
echo "cc analytics: admin key missing"
exit 0
fi
if ! command -v curl >/dev/null 2>&1; then
echo "cc analytics: curl missing"
exit 0
fi
if ! command -v jq >/dev/null 2>&1; then
echo "cc analytics: jq missing"
exit 0
fi
day="${CLAUDE_CODE_ANALYTICS_DAY:-$(date -u +%F)}"
limit="${CLAUDE_CODE_ANALYTICS_LIMIT:-1000}"
email="${CLAUDE_CODE_ANALYTICS_EMAIL:-}"
budget="${CLAUDE_CODE_DAILY_BUDGET_USD:-50}"
url="https://api.anthropic.com/v1/organizations/usage_report/claude_code?starting_at=${day}&limit=${limit}"
api_key="$ANTHROPIC_ADMIN_API_KEY"
unset ANTHROPIC_ADMIN_API_KEY
json=$(ANTHROPIC_ADMIN_API_KEY= curl -fsS \
--config <(printf '%s\n' \
'header = "anthropic-version: 2023-06-01"' \
"header = \"x-api-key: ${api_key}\"" \
'header = "User-Agent: heyclaude-statusline/1.0"') \
"$url" 2>/dev/null || true)
unset api_key
if [ -z "$json" ]; then
echo "cc analytics: unavailable"
exit 0
fi
if [ -n "$email" ]; then
cents=$(printf '%s' "$json" | jq --arg email "$email" '[.data[]? | select(.actor.email_address == $email) | .model_breakdown[]?.estimated_cost.amount // 0] | add // 0' 2>/dev/null || echo 0)
sessions=$(printf '%s' "$json" | jq --arg email "$email" '[.data[]? | select(.actor.email_address == $email) | .core_metrics.num_sessions // 0] | add // 0' 2>/dev/null || echo 0)
scope="user"
else
cents=$(printf '%s' "$json" | jq '[.data[]? | .model_breakdown[]?.estimated_cost.amount // 0] | add // 0' 2>/dev/null || echo 0)
sessions=$(printf '%s' "$json" | jq '[.data[]? | .core_metrics.num_sessions // 0] | add // 0' 2>/dev/null || echo 0)
scope="org"
fi
cost=$(awk -v cents="$cents" 'BEGIN { printf "%.2f", cents / 100 }')
hour=$(date -u +%H)
minute=$(date -u +%M)
elapsed_minutes=$((10#$hour * 60 + 10#$minute + 1))
burn=$(awk -v cost="$cost" -v minutes="$elapsed_minutes" 'BEGIN { printf "%.2f", cost * 60 / minutes }')
pct=$(awk -v cost="$cost" -v budget="$budget" 'BEGIN { if (budget > 0) printf "%.0f", cost * 100 / budget; else print 0 }')
if [ "$pct" -ge 90 ]; then
state="limit"
elif [ "$pct" -ge 70 ]; then
state="watch"
else
state="ok"
fi
printf 'cc analytics: %s | $%s today | burn $%s/h | sessions %s | budget %s%% | %s\n' "$scope" "$cost" "$burn" "$sessions" "$pct" "$state"
}
case $- in
*n*) ;;
*) main "$@" ;;
esac{
"statusLine": {
"type": "command",
"command": "$CLAUDE_PROJECT_DIR/.claude/statuslines/claude-code-analytics-burn-statusline.sh"
}
}Checked existing statuslines, live HeyClaude statuslines, open pull requests, and repository content for claude-code-analytics-burn-statusline, Claude Code Analytics, Claude cost, burn rate, real-time-cost-tracker, and burn-rate-monitor. Existing cost entries use local statusline JSON estimates; this entry uses Anthropic's Claude Code Analytics Admin API with an organization/user reporting scope and a different canonical source.
Editorial statusline recipe. No paid placement or affiliate link is used.
Show that Claude Code Analytics Burn Statusline is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.
[](https://heyclau.de/entry/statuslines/claude-code-analytics-burn-statusline)Claude Code Analytics Burn Statusline side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.
1 trust signal differ across this comparison (Submitter).
| Field | Claude Code statusline that reads Anthropic Claude Code Analytics Admin API data and shows daily estimated cost, hourly pace, sessions, and budget pressure. Open dossier | A Claude Code statusline that reads prompt-cache token metrics from session JSON and renders a color-coded hit-rate bar with an estimated token-savings readout. Open dossier | Real-time burn rate monitor showing cost per minute, tokens per minute, and projected daily spend to prevent budget overruns during Claude Code sessions. Open dossier | Real-time AI cost tracking statusline with per-session spend analytics, model pricing, and budget alerts Open dossier |
|---|---|---|---|---|
| Next steps | ||||
| Trust | ||||
| Review status | ReviewedMaintainer reviewed | ReviewedMaintainer reviewed | ReviewedMaintainer reviewed | ReviewedMaintainer reviewed |
| Package trust | Package not verified | Package not verified | Package not verified | Package not verified |
| Source provenance | Source-backed | Source-backed | Source-backed | Source-backed |
| SubmitterDiffers | MkDev11 | — | — | — |
| Install risk | Review first | Review first | Review first | Review first |
| Notes | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ |
| Brand | — | — | — | — |
| Category | statuslines | statuslines | statuslines | statuslines |
| Source | Source-backed | Source-backed | Source-backed | Source-backed |
| Author | MkDev11 | JSONbored | JSONbored | JSONbored |
| Added | 2026-06-04 | 2025-10-25 | 2025-10-25 | 2025-10-16 |
| Platforms | ||||
| Harness | ||||
| Source repo | — | — | — | — |
| Safety notes | ✓Claude Code Analytics data is daily aggregated and can lag recent activity, so the burn-rate display is a pacing signal rather than real-time billing control. Keep the refresh interval moderate because the statusline calls an authenticated Admin API endpoint. Treat budget thresholds as operational prompts; reconcile invoices and Console reports before making spending decisions. | ✓Runs a bash script on every status-line refresh (about every 2 seconds) that pipes session JSON through jq and bc; it is read-only and makes no network calls or file writes, but status-line commands execute with your shell's permissions, so review the script before adding it to settings.json. | ✓Runs as a Claude Code statusline command on every refresh and depends on the local shell environment; a failure only affects status rendering, not your session. | ✓Runs as a Claude Code statusline command on every refresh and depends on the local shell environment; a failure only affects status rendering, not your session. |
| Privacy notes | ✓The script sends an Admin API request to Anthropic and receives organization-level Claude Code analytics. It prints aggregate cost, session, and budget numbers, not email addresses, model names, prompts, file paths, or code. Admin API keys can expose organization analytics; store them in a scoped local secret manager or shell environment with restricted access. The script feeds the API key to curl through a config file descriptor instead of command-line arguments and unsets the exported key before launching curl, reducing process-list exposure on shared machines. | ✓Reads Claude Code session cost and token metrics from the status-line JSON on stdin and prints them to your terminal; no data leaves the machine, but the displayed figures may be visible to anyone viewing your screen or a terminal recording. | ✓Reads the Claude Code statusline JSON from stdin (model, workspace path, token usage) and renders it in the local terminal; it does not send data off-machine. | ✓Reads the Claude Code statusline JSON from stdin (model, token usage, and cost) and renders it in the local terminal; it does not send data off-machine. |
| Prerequisites |
|
|
|
|
| Install | — | — | — | — |
| Config | | | | |
| Citations | ||||
| Claim | Unclaimed | Unclaimed | Unclaimed | Unclaimed |
Source-backed guides for putting this to work.
Choose fast mode vs standard Opus using official /fast tradeoffs, pricing, and rate-limit behavior.
Loading live community signals…
A short, calm digest of reviewed Claude resources. Unsubscribe any time.