Personal use and terms of service
Pool accounts you own, in sessions and agents you run yourself
tokenmaxxing pools accounts you own, in sessions and agents you run yourself. That wording is deliberate: Anthropic does not allow third-party products to offer claude.ai login or claude.ai rate limits, and that includes agents built on the Agent SDK. Do not ship anything built on tokenmaxxing to third parties. tokenmaxxing is not a proxy: it never handles API traffic, and it holds no OAuth refresh grant of its own for Claude. A pi session runs on pi's own login of a pooled account, which pi refreshes itself; the same terms apply to it. The only Anthropic endpoints tokenmaxxing calls are a read-only identity check at onboarding (a pi login included) and in doctor (GET /api/oauth/profile, to verify which account a token actually belongs to) and the no-spend usage read every sampler makes (GET /api/oauth/usage?at_wall=1&skip_spend=1, the same read Claude Code's own /usage makes); every other quota figure comes from Claude Code's statusline feed. tokenmaxxing holds no Claude refresh grant: when a stored access token has expired, the sample runs Claude Code under that store (claude -p /usage), and Claude Code refreshes the token itself. For Codex it calls OpenAI's usage endpoint and, for an idle account whose token is expiring, the standard refresh grant.