All your AI quotas in one panel.
An iPhone panel for your AI subscription quotas. Claude, Codex, Grok, Cursor, Minimax and MiMo come built in, with endpoints verified against real accounts — and any other service with a JSON usage endpoint can be added by pointing at the fields. In the app, in widgets, on the Lock Screen and in the Dynamic Island. Available on the App Store.
- PlatformiOS 17+iPhone
- StackSwiftUI · WidgetKit · SwiftData
- ProvidersClaude, Codex, Grok, Cursor, Minimax, MiMo + JSON
- AuthenticationOAuth (Anthropic, OpenAI) · login por sessão · API key
Six sites open just to find out where you still have headroom
Anyone subscribing to more than one AI service knows the ritual: open each provider's dashboard to find out what's left of Claude's 5-hour window, Cursor's cycle, Minimax's credits. The information exists — scattered across six places, each with its own login and format.
Okami Tally queries each service directly from the iPhone and shows everything on one screen — or the Lock Screen, or the Dynamic Island. There is no backend, no agent running on your Mac, and your data touches nothing beyond the device and the service itself. Zero telemetry.
It is the first closed-source product in the Okami suite — a native iPhone app, distributed through the App Store. The same engineering as the open-source products, applied where a paid-app model makes more sense than an open repository.
What Okami Tally does
Six verified providers + generic endpoint
Claude, Codex, Grok, Cursor, Minimax and MiMo come ready, verified against real accounts. Any other service with a JSON usage endpoint joins by pointing at the field paths — percentage, reset, window.
Zero backend, zero telemetry
The app talks directly to each service, from the device. There is no Okami server in the path, no analytics, and no outbound call other than the queries to the services you connected.
Credentials live only in the device Keychain
Tokens, keys and session cookies live in the Keychain with AfterFirstUnlockThisDeviceOnly — they never leave the device, not even in backups. Raw API responses live only in memory and are never written to disk.
Widgets, Lock Screen and Dynamic Island
Quotas show up where you look: home-screen widgets, Lock Screen and a Live Activity in the Dynamic Island. The medium and large widgets have a refresh button — one tap fetches instantly, without opening the app.
Real-time model recommendation
With the real state of every quota, the app points at which model to use right now — before you burn the wrong plan's window in the middle of a long session.
Plan windows separated from secondary quotas
Every service has more than one quota, and the app shows them all — separating the ones that block usage when exhausted (Claude's 5h window, Cursor's cycle) from paid credits, per-model limits and on-demand spend.
Spec sheet and when to use it
- Platform
- iOS 17+ (iPhone)
- Stack
- SwiftUI · WidgetKit · SwiftData
- Providers
- Claude, Codex, Grok, Cursor, Minimax, MiMo + JSON
- Authentication
- OAuth (Anthropic, OpenAI) · login por sessão · API key
- Data
- Keychain (AfterFirstUnlockThisDeviceOnly) · App Group
- Backend
- —
- Distribution
- App Store
Anyone with more than one AI subscription
Claude for code, Codex for review, Cursor in the editor. Tally shows where you still have headroom — and recommends which one to use now — without opening six dashboards.
Long agent sessions
Before dispatching a batch of tasks to agents, a glance at the Lock Screen tells you whether the plan window can take it — or whether it's time to route to another provider.
Anyone who won't put credentials on a third-party server
Session cookies are equivalent to a password. In Tally they live in the device Keychain, queries go straight from the iPhone to the service, and there is no intermediary server to leak anything.
Okami Tally FAQ
Is Okami Tally open-source like the other products?
No — it is the suite's first closed-source product, a native iPhone app distributed through the App Store. The other six Okami products remain open-source on GitHub.
Do my credentials pass through any Okami server?
There is no Okami server — by design the app has no backend. Tokens, keys and cookies live in the device Keychain (AfterFirstUnlockThisDeviceOnly), and queries go straight from the iPhone to each service. There is no telemetry or analytics.
How often do the widgets refresh?
The app requests 5 minutes, but iOS decides, within a daily budget — in practice it lands between 5 and 20 minutes. That's why the medium and large widgets have a refresh button: one tap fetches instantly without opening the app. With the app open, refresh is every minute.
Does it work with Google login? And on Android?
Google login doesn't work inside any app, by Google's own decision — use email on the same screen or an API key where the service offers one. Android is out of scope for v1; the app is iPhone-native (iOS 17+).
The products that carry the consulting
Okami Agent
Sovereign AI coding agent: capability parity across LLMs, self-improvement (skills, persona, memory) and mandatory design-system adherence. In the terminal, on Telegram, wherever you want.
Okami Monitor
Mission control for multi-agent environments: usage and cost per period, sessions, Kanban, logs, API keys and external runtime connections — in one cockpit.
OkamiCode
Local-first desktop cockpit for AI coding CLIs: folder-bound projects, native sessions per provider, chat, email, Kanban, usage/cost analytics and durable memory — without paying a second API bill.
Okami Maturity
OWASP SAMM v2 maturity assessment: 5 functions, 15 practices, 90 questions — with scorecard, radar, prioritized roadmap and a board-ready PDF report.
Okami Sentinel
Local workbench for OpenAI Codex Security scans: run, inspect, compare up to six runs and gate changes with versioned guardrails — evidence, cost and context preserved in a local workspace.
OkTally
Every AI coding subscription quota in your macOS menu bar — Claude Code, Codex, Cursor, OpenRouter and more. Colored pins, a popover with the full picture and a notification before you hit the limit. All local, no telemetry.
OkamiUNI
Email and calendar together on the Mac. Unified inbox, macOS calendars and AI to summarize threads, draft replies and turn emails into appointments. Local data, your choice of AI provider.
Want Okami Tally running in your context?
The product is open and you can run it yourself. Rolling it out in your environment, with design-system integration and a documented hand-off, is the consulting.