# AI use cases for Oh My Cpa (WizisCool/oh-my-cpa) Repo: [WizisCool/oh-my-cpa](https://github.com/WizisCool/oh-my-cpa) | Use cases: 4 | Page: https://dedupedai.com/use-cases/wiziscool-oh-my-cpa/ Oh My CPA is a self-hosted web console that manages a CLIProxyAPI gateway's providers, credentials and client keys, and records the usage and cost of every request. This file holds every use case of this repo. Each one starts with a "## " heading and ends with its URL. - Install Oh My CPA by handing the setup to an agent: https://dedupedai.com/use-cases/wiziscool-oh-my-cpa/install-oh-my-cpa-with-a-coding-agent/ - Track request volume, tokens and cost per model: https://dedupedai.com/use-cases/wiziscool-oh-my-cpa/track-request-cost-and-usage/ - Add providers and client keys behind one gateway: https://dedupedai.com/use-cases/wiziscool-oh-my-cpa/route-clients-through-one-gateway/ - Check Codex and Claude quota windows before a busy day: https://dedupedai.com/use-cases/wiziscool-oh-my-cpa/check-oauth-quota-windows/ ## How to install Oh My CPA by handing the setup to an agent with Oh My Cpa Repo: [WizisCool/oh-my-cpa](https://github.com/WizisCool/oh-my-cpa) | Difficulty: Intermediate | Time: 45 minutes | Basis: From the README A coding agent inspects the machine, picks an install method and sets up the console. **Who it is for:** A developer with Claude Code, Codex or Cursor open who wants CLIProxyAPI's console running without reading the install docs. **The problem:** Choosing between Docker, Compose and a native executable, and finding the right setup for an existing CPA, takes time. **The outcome:** The agent installs Oh My CPA with a method that matches the machine, and the console is ready to sign in. ### Steps 1. Open Claude Code, Codex or Cursor on the machine where Oh My CPA should run. 2. Paste this into the agent: `Install Oh My CPA for me by following https://raw.githubusercontent.com/WizisCool/oh-my-cpa/master/docs/install-for-agents.md` (inferred, check the README) 3. Let the agent inspect the machine and choose the matching install method, and review the commands it proposes before it runs them. 4. When the agent reports the install is done, open the console at `http://127.0.0.1:8080/omc/` and sign in with the CPA management key. ### Prompt to paste into your agent ```text Install Oh My CPA on this machine by following https://raw.githubusercontent.com/WizisCool/oh-my-cpa/master/docs/install-for-agents.md. Report which install method you chose and why. Verify that the console answers at http://127.0.0.1:8080/omc/ before you finish. ``` ### Caveat CPA has to be installed and reachable separately, and the README does not say the agent installs CPA itself. Risk, remote script: The agent follows an install guide fetched from a raw GitHub URL and changes the machine, so read the commands it plans to run before approving them. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/wiziscool-oh-my-cpa/install-oh-my-cpa-with-a-coding-agent/ ## How to track request volume, tokens and cost per model with Oh My Cpa Repo: [WizisCool/oh-my-cpa](https://github.com/WizisCool/oh-my-cpa) | Difficulty: Intermediate | Time: 30 minutes | Basis: From the README See which models, providers and client keys drive usage and spend across CPA requests. **Who it is for:** An operator running CLIProxyAPI for a team who needs to know what each model and client costs. **The problem:** CPA routes requests to many providers, and without a record of each request it is hard to tell where usage and cost come from. **The outcome:** A dashboard with request volume, token throughput, cache hit rate and cost, plus filterable request records for any time range. ### Steps 1. Save the Compose file from the install guide in a new directory, then run `docker compose up -d`. 2. Open `http://127.0.0.1:8080/omc/` and sign in with the `CPA_MANAGEMENT_KEY` value from `.env`. 3. On the Dashboard, pick a preset from 15 minutes to 90 days, the all-time window, or a custom range. 4. Open Request records and filter by model, provider, key or status to find the requests behind a cost spike. ### Prompt to paste into your agent ```text Use the Oh My CPA console at http://127.0.0.1:8080/omc/ in the directory to find the three models with the highest cost over the last 7 days. Report each model with its request count and cost. Verify the totals match the Request records filter for the same range. ``` ### Caveat CPA hands each usage record to a single reader, so if another usage tracker reads the same CPA, stop it or set OMCPA_USAGE_INGEST_MODE to "off" for management only. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/wiziscool-oh-my-cpa/track-request-cost-and-usage/ ## How to add providers and client keys behind one gateway with Oh My Cpa Repo: [WizisCool/oh-my-cpa](https://github.com/WizisCool/oh-my-cpa) | Difficulty: Intermediate | Time: 30 minutes | Basis: From the README Configure AI providers and named client keys once, then point every client at CPA. **Who it is for:** A developer who wants several apps or teammates to use the same set of AI providers through one endpoint. **The problem:** Each provider has its own credentials, models and limits, and sharing them safely across clients is error-prone. **The outcome:** Providers are enabled in the console, each client has its own named key, and clients send requests to CPA at http://127.0.0.1:8317. ### Steps 1. Complete the install from the Compose guide and sign in at `http://127.0.0.1:8080/omc/` with the `CPA_MANAGEMENT_KEY` value from `.env`. 2. Add an AI provider in the console and set its priority and enable switch. 3. Create a client key in the console and give it a name so it appears in request records. 4. Point each client at `http://127.0.0.1:8317` and send a test request from the Playground. ### Prompt to paste into your agent ```text In the Oh My CPA console at http://127.0.0.1:8080/omc/, add one provider and one client key named . Report the provider's status and the key name. Verify with a Playground request that the routed model answers before you finish. ``` ### Caveat The README describes clients sending requests to CPA at http://127.0.0.1:8317 for the local Compose install, so other network setups need the reaching CPA guide. Risk, credentials: Client keys and provider credentials grant access to paid model usage, so store them carefully and revoke any key that leaks. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/wiziscool-oh-my-cpa/route-clients-through-one-gateway/ ## How to check Codex and Claude quota windows before a busy day with Oh My Cpa Repo: [WizisCool/oh-my-cpa](https://github.com/WizisCool/oh-my-cpa) | Difficulty: Intermediate | Time: 30 minutes | Basis: From the README Read quota and window capacity estimates for each OAuth credential in one console. **Who it is for:** A person with Codex or Claude OAuth sign-ins who needs to know how much capacity each credential has left. **The problem:** Quota is spread across several sign-ins and windows, and checking each provider separately is slow. **The outcome:** A per-credential view of quota readings and estimated window capacity, with refresh times set in OMC Settings. ### Steps 1. Install Oh My CPA from the Compose guide and sign in at `http://127.0.0.1:8080/omc/`. 2. Open OAuth management and sign in for Codex or Claude from the console. 3. Read the window capacity estimate and the previous cycle shown as a labelled reference for each credential. 4. Adjust how often quota readings refresh in OMC Settings if the default six hours does not suit you. ### Prompt to paste into your agent ```text In the Oh My CPA console at http://127.0.0.1:8080/omc/, list each Codex and Claude OAuth credential with its estimated window capacity. Report the credentials that have less than half their window left. Verify each figure against the quota reading shown for that credential before you finish. ``` ### Caveat The README calls window capacity an estimate, so treat it as guidance rather than an exact provider limit. Risk, account pooling: Running several sign-ins behind one gateway can conflict with the terms of the provider, so check what each provider allows before you pool accounts. Risk, credentials: OAuth sign-ins store tokens in the console's encrypted database, so keep the .env master key backed up and never share it. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/wiziscool-oh-my-cpa/check-oauth-quota-windows/