cpa-status

/cpa in chat for CLIProxyAPI (CPA) pools: account health per provider (active, limited, cooling, error, disabled), the CPA version with an update hint, and on request each account's live quota (Claude, Codex, xAI, Antigravity, Devin, Kimi, Kiro), the same usage reads as CPA's own web UI. Companion to cliproxyapi-provider and reads the same cliproxyapi config. Disclosure — only when you type /cpa, and with the management key env var you name per instance: GETs the credentials list from your configured CPA and CPA's own update check (at most once per 6 hours); for /cpa quota, POSTs CPA's api-call so CPA sends each built-in vendor's private usage request (Anthropic, ChatGPT/Codex, xAI, Google Antigravity, Codeium/Devin, Kimi) with that account's token, using the vendor clients' own User-Agent and client headers as CPA's web UI does (Antigravity and Devin are vendor POSTs, the rest GETs), and GETs CPA plugin quota for Kiro; at most 20 accounts, 4 requests in flight. Stops at the first rejected key: one failed try, or up to 4 if the key is revoked mid-run; CPA bans an IP after five failed management logins. Writes only lock files and a rejected-key marker (salted HMAC, never a key) under $HERMES_HOME/cache/cliproxyapi/locks/. Known limit: Hermes strips from agent subprocesses only the key env vars a registered provider declares, so the management key env var stays readable by agent shells.

duu2614Modelsv0.7.3Updated 2 hours ago

About

cpa-status

/cpa for Hermes Agent: account
health for every CLIProxyAPI
(CPA) pool in your config, and live per-account usage on request.
Companion to the
cliproxyapi-provider
model-provider plugin; it reads the same cliproxyapi: section.

hermes plugins install duu261/hermes-cliproxyapi-provider#cpa-status
hermes plugins enable cpa-status

Requires Hermes 0.21.7 or newer and mgmt_key_env on each instance you want
to see (an instance without it on the same CPA base_url as one with it is
shown under that one as same CPA). Restart running gateways after enabling.
Upgrade it together with the provider plugin: both share one lock per CPA.

/cpa                       every instance: accounts per provider
/cpa <pool>                one instance, plus the last hour of requests
/cpa <pool> <provider>     one line per account
/cpa quota <pool> [provider]   live usage from each vendor

/cpa: one read-only GET /v8/management/credentials per instance, only
when you type it. No timers, no retries; repeats within 20 seconds use
memory. Last-seen 5h and weekly quota for Claude and Codex accounts, as CPA
recorded it on real traffic.
/cpa quota: like CPA's web UI quota page, for Claude, Codex, xAI,
Antigravity, Devin and Kimi accounts through CPA's api-call route with the
web UI's fixed requests (the account's token filled in by CPA), and for
other providers through their CPA quota plugin (e.g. Kiro). Nothing paid,
no downloads, no resets; the full request list is in the
README. At most 20 accounts and 3
requests per account per run, first request alone, then 4 at a time;
repeats within 60 seconds use memory.
Emails are masked; email, account and path are never read. CPA's
account index, the Codex account id, the Antigravity project id and the CPA
plugin id are used only to build the quota requests, never shown or stored.
Idle chats only: sent during an agent turn it goes to Hermes' busy handling.
The management key is full admin on CPA, and Hermes does not strip it from
agent shells. CPA bans an IP after five failed management keys in a row; a
rejected key is never sent again (salted HMAC in
$HERMES_HOME/cache/cliproxyapi/locks/rejected.json). Read
Never get locked out of CPA.

Full documentation: the repository README.

README from the reviewed commit 08fdae8; it updates when the author re-pins.

More by duu261

3 plugins by duu261 in the catalog.

duu261openai-compatibleGPT Image through CLIProxyAPI, New API, or any OpenAI Images-compatible gateway, with gateway-aware errors and requested-vs-returned size reporting. Disclosure — sends image prompts and any source images (local files, data URLs or public HTTPS URLs) to the OpenAI-compatible gateway base_url you configure, authenticated with OPENAI_COMPAT_IMAGE_API_KEY.Communitytools5 duu261cliproxyapi-providerCLIProxyAPI as native Hermes model providers: discovers each CPA provider group (Claude, Codex, xAI, Gemini, Kiro and others) and registers one profile per group on the wire its CPA executor accepts (Anthropic Messages, Responses or Chat Completions), with context windows and reasoning levels from CPA. Disclosure — sends model-list and inference requests, authenticated with the API key env var you name, to the CPA base_url you configure; with an optional management key it also makes bounded read-only GETs to CPA's management API; with an optional billing route it sends inference, and a model-list GET, to the gateway URL you configure, authenticated with the gateway key env var you name. Known limit: Hermes strips from agent subprocesses only the key env vars a registered provider declares, so the management key env var, and on a routed instance the CPA key env var, stay readable by agent shells. Writes its model cache under $HERMES_HOME/cache/cliproxyapi/, plus lock files and a rejected-key marker (salted HMAC, never a key) under $HERMES_HOME/cache/cliproxyapi/locks/.Communitymodels4