Cursor API does not expose per-model dollar spend. Model breakdown is local active-model / analytics grouping plus Auto/API meters. We do not invent per-model USD.
Group
Source
autoApi
Cursor usage-summary Auto % / API % plus local poll history from status/watch/report
surface
Local daily stats: Tab vs Composer accepted lines
model
Locally configured active models per surface — not a billed dollar split
Accounts
accounts discovers each product folder’s state.vscdb (cursorAuth/accessToken + cached email). use saves an email + product pointer to ~/.config/curse-monitor/config.json — never the token.
curse-monitor accounts
curse-monitor use 1
curse-monitor use [email protected]
curse-monitor use dCursor
curse-monitor status --account Cursor
Default when nothing is saved: prefer dCursor when [email protected] is signed in; otherwise the first discovered product folder. --token / CURSOR_TOKEN still override.
Auth
Source
Priority
--token <token>
1
CURSOR_TOKEN env
2
--account one-shot selector
3
Saved use pointer in config.json
4
Cursor state.vscdb (cursorAuth/accessToken)
5
The access token is never logged or written to JSON output. See Privacy.
Placeholder Worker under api/ exposes /api/curse-monitor/health and /api/curse-monitor/usage. Responses are structured stubs with usage: null — no invented numbers, no Cursor session tokens. Later this can bind on Mission Control at cursor-dev.lorapok.tech using the sibling admin wrangler service-binding pattern. See api/README.md.