{
 "schema_version": 1,
 "generated": "2026-10-24",
 "id": "gesta-run-subpool--track-token-use-and-quota-per-key",
 "repo": "gesta-run/subpool",
 "repo_url": "https://github.com/gesta-run/subpool",
 "repo_slug": "gesta-run-subpool",
 "title": "Track token use and quota per employee key",
 "page_title": "How to track token use and quota per employee key with Subpool",
 "summary": "Review aggregate token telemetry and remaining subscription capacity for each key.",
 "who": "A team lead or finance-minded administrator who needs to see how shared AI capacity is being consumed.",
 "problem": "Without per-key numbers, the team cannot tell which employees use the pool or how much subscription quota remains.",
 "outcome": "A per-key view of input and output tokens and a current reading of remaining subscription capacity and reset timing.",
 "steps": [
  "Open the Accounts view in the Subpool console and check each account's remaining subscription capacity and reset availability.",
  "Review the aggregate input and output token telemetry shown for each employee API key.",
  "Run `curl http://localhost:8080/metrics` to read the Prometheus metrics endpoint on the employee API listener. (inferred, check the README)",
  "Note that token figures use provider-native units, so compare them only within the same provider."
 ],
 "agent_prompt": "Using the gesta-run/subpool repository, query the metrics endpoint at <Subpool API URL>/metrics and list the request counters and token-related series you find. Expected output: a short table of metric names and current values. Verify that each metric name appears in the response body before reporting it.",
 "agents": [
  "any"
 ],
 "difficulty": "Intermediate",
 "time": "45 minutes",
 "basis": "readme",
 "caveat": "Telemetry is aggregate and in provider-native units, so it does not show per-request content and should not be treated as a cross-provider cost figure.",
 "category": "Work and operations",
 "tags": [
  "Work and operations"
 ],
 "lang": "go",
 "requirements": [
  "Docker Engine and Docker Compose installed",
  "openssl available to generate secrets",
  "AI subscription or API accounts that you are authorized to manage",
  "Administrator credentials for a running Subpool console (set in .env)"
 ],
 "risk": "sensitive",
 "seen_in_the_wild": false,
 "mentioned_publicly": false,
 "risks": [],
 "best": false,
 "score": 0.7,
 "evidence": [],
 "url": "https://dedupedai.com/use-cases/gesta-run-subpool/track-token-use-and-quota-per-key/",
 "md": "https://dedupedai.com/use-cases/gesta-run-subpool/track-token-use-and-quota-per-key/index.md",
 "disclaimer": "Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked \"Seen in the wild\", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email hello@dedupedai.com and we will look at it promptly.",
 "api": "https://dedupedai.com/api/v1/usecases/gesta-run-subpool--track-token-use-and-quota-per-key.json",
 "api_version": "v1"
}