Every AI quota,
one ring.
UsageLens puts your AI usage in one place: a single dashboard and a configurable Home Screen widget that show how much of your allowance you have used. It is a quota ring, not a battery icon — one glance tells you where you stand.
Four ways to track
Connect what reports. Count what doesn't.
Some AI services publish an official usage API. Some expose an internal gateway. Some publish nothing at all. UsageLens covers all three cases instead of pretending the last one doesn't exist.
OpenAI Platform
Connect an organization Admin API key and follow total tokens, model requests, or spend in USD through the official organization usage and cost endpoints, with cursor pagination.
Anthropic Claude Platform
Connect an organization Admin API key and follow total tokens, requests, or cost through the official Usage and Cost Admin API — including cached and cache-creation input tokens.
Custom REST
Point UsageLens at any authorized HTTPS endpoint that returns JSON. Map used, limit, remaining, reset and cost with simple paths like quota.used. Ideal for an internal gateway or a broker.
Manual tracker
For plans with no reporting API, keep your own count. Update it in the app, or with the “Log AI Usage” Shortcut without opening the app at all.
What it looks like
Built around one honest number.
Overall pressure is the highest quota pressure you are tracking — never a meaningless sum of tokens, dollars and messages. Every screen tells you how fresh the data is.
Security
Your keys never leave the Keychain.
An organization Admin API key can read sensitive usage and financial data. UsageLens is built so that key has exactly one place to live.
- Credentials are stored as Keychain items, device-only, and are never written to the file the widget reads.
- The widget is read-only and cannot reach your credentials at all.
- Custom endpoints are HTTPS-only and GET-only, with timeouts, no cookies, no cache, and a 2 MB response cap.
- Headers that look like credentials are rejected, so a secret can't be pasted somewhere it would be stored in plain text.
- Error messages never echo your keys, headers, or raw responses.
- Privacy mode hides exact amounts in widgets while keeping the ring visible.
- No account, no analytics, no advertising, no third-party SDKs. Nothing is sent to us.
Deploying to a team?
Handing an organization-wide Admin key to every device is a poor trade even with Keychain storage. Keep the key on a broker service that calls the provider server-side and returns only normalized numbers, then point the Custom REST connector at the broker.
The app never needs to see the upstream key.
What UsageLens does not do
The OpenAI and Anthropic connectors report usage for an API organization. They do not report ChatGPT or Claude consumer subscription message allowances, because those providers publish no API for them — Anthropic states its Admin API is unavailable to individual accounts. To follow a consumer plan, use a manual tracker or point the Custom REST connector at an endpoint you control.
UsageLens does not read other apps, does not scrape provider websites, and never asks for your browser cookies or session tokens. It reads official APIs, endpoints you configure yourself, and numbers you enter by hand.
A quota limit is a budget you define. It may not match the limit your provider enforces for billing. Background refresh is best effort — iOS decides when background work and widget updates actually run; pull to refresh in the app is always immediate.
Support
Questions, bugs, anything.
There is no account system and no ticket queue — just email. Include your iOS version and which connector you are using, and please never send an API key.
forall@tuta.com