{"slug": "how-to-track-factory-droid-usage", "title": "How to track Factory Droid usage", "summary": "UsageAtlas added a Factory / Droid integration that reads account limits and balances through a Factory API key, letting users track Droid usage alongside other providers in the free open-source app for Windows, macOS, and Linux. The integration does not import per-request tokens, models, projects, or cost history, and it does not run Droid's /stats command or scan sessions for historical tokens, according to the connection documentation. Users can enter a key in Settings → Sources or supply FACTORY_API_KEY via the startup environment or the supported ~/.factory/.env file, and saved credentials are stored in the operating system's encrypted storage rather than cloud saves.", "body_md": "## Check Droid's own usage commands\n\nThe [Droid CLI reference](https://docs.factory.ai/droid-cli/cli-reference) lists `/limits` for limits and overage preferences, and `/stats` for usage statistics. Those are useful for checking what Factory reports before comparing it with a desktop tracker.\n\n## Track Factory / Droid in UsageAtlas\n\n1. [Download the free UsageAtlas app](https://usageatlas.com/#download) for Windows, macOS, or Linux.\n2. Open Settings → Sources, find Factory / Droid, and expand Connect. Enter a Factory API key.\n3. Choose Save and check, then open Limits. Read Standard and Core pools independently. Accounts on supported older billing formats may show different counters.\n\nUsageAtlas is open source and needs no UsageAtlas account for local tracking. Saved provider credentials use your operating system's encrypted storage and stay out of cloud saves.\n\n## Use an existing Factory key\n\nUsageAtlas also accepts `FACTORY_API_KEY` from its startup environment or the supported `~/.factory/.env` file. Browser and WorkOS login discovery are not part of this integration. If a saved key is stale, replace it in Settings and check again.\n\n## What this integration tracks\n\nThis connection reads current allowances and balances. It does not import per-request tokens, models, projects, or cost history. UsageAtlas shows a capacity meter only when the provider supplies enough information. A missing limit is unknown, not zero. See the [connection documentation](https://github.com/SRX9/UsageAtlas/blob/main/docs/QUOTA_PROVIDERS.md) for supported fields.\n\n## Questions, answered\n\n### Does UsageAtlas import Droid /stats history?\n\nNo. The current Factory integration reads account limits and balances. It does not run /stats or scan Droid sessions for historical tokens.\n\n### Why is a Factory pool missing a percentage?\n\nFactory may omit an allowance or report an unlimited pool. UsageAtlas does not invent a denominator to make a meter.", "url": "https://wpnews.pro/news/how-to-track-factory-droid-usage", "canonical_source": "https://usageatlas.com/guides/how-to-track-factory-droid-usage", "published_at": "2026-09-30 00:00:00+00:00", "updated_at": "2026-10-03 09:39:51.946329+00:00", "lang": "en", "topics": ["ai-tools", "developer-tools", "ai-products"], "entities": ["UsageAtlas", "Factory", "Droid", "FACTORY_API_KEY", "WorkOS"], "also_reported_by": [], "alternates": {"html": "https://wpnews.pro/news/how-to-track-factory-droid-usage", "markdown": "https://wpnews.pro/news/how-to-track-factory-droid-usage.md", "text": "https://wpnews.pro/news/how-to-track-factory-droid-usage.txt", "jsonld": "https://wpnews.pro/news/how-to-track-factory-droid-usage.jsonld"}}