tokenmaxx only knows subscription logins. Both providers now have two more ways to pay, and we show neither.
Extra usage is pay-as-you-go credit on top of a subscription, billed at API rates once the plan window is full. Both providers already report it on the usage endpoints we poll, so showing it costs zero new requests. Claude's payload has an extra_usage block (enabled, monthly limit, used credits, utilization) and a spend block (balance, auto reload). Codex's has a credits block (balance, overage state). One more reason this matters: when a third-party harness uses a Claude account, Anthropic bills extra usage, not the plan window. Anyone routing a harness through tokenmaxx is spending real dollars they can't see.
API keys are the provider-sanctioned way to run custom clients. tokenmaxx should let you add one like any other account and give it the same switching, metering, and analytics.
What to build:
- Add an account with an API key, stored in the Keychain like everything else.
- Keep one row per account. A row shows what its account can meter: plan windows for logins, an extra-usage cell when it's on, measured spend for API keys.
- Rotation gets one new choice per account: at the threshold, switch accounts or spill into extra usage. Default stays exactly today's behavior.
- In analytics, extra usage and API key spend are real dollars, not ≈. Label them that way.
Done when an API key account routes and meters like any other, extra usage shows on the row and in analytics when it's enabled, and the accounts view still reads at a glance.
Thanks @tedspare for the idea.
tokenmaxx only knows subscription logins. Both providers now have two more ways to pay, and we show neither.
Extra usage is pay-as-you-go credit on top of a subscription, billed at API rates once the plan window is full. Both providers already report it on the usage endpoints we poll, so showing it costs zero new requests. Claude's payload has an
extra_usageblock (enabled, monthly limit, used credits, utilization) and aspendblock (balance, auto reload). Codex's has acreditsblock (balance, overage state). One more reason this matters: when a third-party harness uses a Claude account, Anthropic bills extra usage, not the plan window. Anyone routing a harness through tokenmaxx is spending real dollars they can't see.API keys are the provider-sanctioned way to run custom clients. tokenmaxx should let you add one like any other account and give it the same switching, metering, and analytics.
What to build:
Done when an API key account routes and meters like any other, extra usage shows on the row and in analytics when it's enabled, and the accounts view still reads at a glance.
Thanks @tedspare for the idea.