Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Most Arch Linux + waybar users today who want a single AI quota widget for multiple vendors have been either (a) running claudebar for Claude only and maintaining separate vendor widgets for OpenAI / Z.AI / OpenRouter / DeepSeek, (b) writing per-vendor quota scripts by hand and wiring them into Waybar as custom JSON, or (c) running cloud-hosted dashboards that require sign-in and exfiltrate usage
Who should use it
Who should skip it
Consider AI-Usagebar: MIT Rust Multi-Vendor AI Quota Tracker (Claude + Codex + GLM + OpenRouter + DeepSeek, Waybar + TUI) lower priority if you already have a working solution in this category.
About this signal
AI-Usagebar: MIT Rust Multi-Vendor AI Quota Tracker (Claude + Codex + GLM + OpenRouter + DeepSeek, Waybar + TUI) is tracked by RepoRadar as a tool in the Radar section. It was first seen on 2026-07-08 and last updated on 2026-07-08. The current verdict is 'try now' with a Silver tier and easy setup difficulty. The standout signals for AI-Usagebar: MIT Rust Multi-Vendor AI Quota Tracker (Claude + Codex + GLM + OpenRouter + DeepSeek, Waybar + TUI) are setup ease (8.8) and workflow potential (8.7), while maturity (5.5) trails — that balance shapes where it fits best. This page summarizes the evidence RepoRadar has captured from captured source metadata. The score, tier, risk label, and verdict on this page are never influenced by sponsorship, ads, or tips — they reflect only the usefulness, popularity, novelty, momentum, maturity, and evidence signals described in the RepoRadar methodology.
How this item is evaluated
RepoRadar assigned AI-Usagebar: MIT Rust Multi-Vendor AI Quota Tracker (Claude + Codex + GLM + OpenRouter + DeepSeek, Waybar + TUI) a composite score of 7.6 out of 10, placing it in the Silver tier. This score combines weighted sub-signals: usefulness (35%), novelty (18%), momentum (14%), maturity (10%), open-source/build quality (7%), evidence quality (6%), workflow potential (6%), and setup ease (4%). Popularity is tracked separately at 0.0 and never affects the composite score or tier. The risk label of 'low' reflects inherent user-impacting hazards, not generic novelty. Items with no risk flag may still require normal code review before production use.
Putting this into practice? Read How to evaluate an AI tool before you adopt it for the checklist behind this score.
Risk explanation
The 176* / 33-fork / 1-subscriber repo is at active maintenance but the consumer SHOULD note 176* is below the typical 200+ star threshold for RepoRadar try_now picks -- the niche audience (Arch Linux + waybar users + multi-vendor AI quota tracking) is real but small; the consumer SHOULD note the project is a Rust port of `claudebar` and the vendor surface depends on the underlying undocumented endpoints of each AI provider -- schema drift is possible and the README's `make smoke` is the canonical drift-discovery mechanism; the consumer SHOULD note the atomic cache writes + flock mechanism protects multi-monitor Waybar instances but the consumer SHOULD verify their Waybar config invokes the binary correctly; the consumer SHOULD note the live API smoke tests require real API credentials for each vendor (Claude / Codex / GLM / OpenRouter / DeepSeek) -- the consumer SHOULD review the per-vendor config schema (`config.example.toml`) and ensure their credentials are stored securely (the README notes flock-protected OAuth refresh for Claude).