Claude Code on each member's Claude plan, with the team's logs and limits.
Every developer keeps Claude Code signed in to their own Claude Pro, Max, Team or Enterprise plan, and the plan keeps paying for the tokens. Pointed at Tempr, each request also gets what an API key would: a request log, rate and token limits, guardrails, and another model to carry on with when the plan's limit is reached.
Plan requests count toward your Gateway plan's request quota, like any other request.
The plan pays. Tempr records and governs.
Each member's own plan
Claude Code keeps its claude.ai sign-in and sends it with each request; Tempr forwards it to Anthropic and never stores it. Nobody shares a plan.
Every request logged
Tokens, latency and status for each request, which plan paid, the plan's 5-hour and weekly usage windows, and what it would have cost at API prices.
Limits that fit a plan
Rate limits, model allowlists, and budget rules on requests and tokens apply as usual. Dollar budgets don't count plan-paid requests, since they cost you nothing.
Guardrails on every request
Secrets and personal data are flagged or blocked on every plan; Pro and up can mask them before Anthropic sees them.
When a plan runs out
Give the key a used-up model, such as a coding plan or an API key, and Claude Code carries on there instead of stopping. The log says so.
Your organization decides
Organization keys accept plan logins only once an owner or admin turns on Plan logins, for the organization or for one key.
One setting in Claude Code.
Leave Claude Code signed in to claude.ai. Set only the base URL, and send your Tempr key in its own header. Don't set ANTHROPIC_API_KEY or ANTHROPIC_AUTH_TOKEN: either one replaces your sign-in.
// keeps each member's Claude plan { "env": { "ANTHROPIC_BASE_URL": "https://api.temprhq.io", "ANTHROPIC_CUSTOM_HEADERS": "x-tempr-key: tvk_..." } }
About Claude Code on Claude plans.
Can a team share one Claude Max plan through Tempr?
No. Each member's Claude Code sends that member's own sign-in, so each request is paid by that member's plan. Tempr doesn't pool plans, and a Claude Pro or Max plan belongs to one person.
Do dollar budgets apply to requests a Claude plan pays for?
No, since they cost you nothing. Rate limits, model allowlists and budget rules on requests and tokens do apply, and each request's log shows what it would have cost at API prices.
What happens when someone's 5-hour limit runs out?
By default the request stops, as it would without Tempr. If the key has a used-up model, the request goes there at once, on your stored key for it, and the log records both. Any other error from the plan comes back as it is, so nothing is spent on an API key by mistake.
Is routing a Claude plan through a gateway allowed?
Anthropic's Claude Code terms allow you to use your own subscription with Claude Code, but bar third parties from routing Pro or Max credentials on their users' behalf. They don't say how that applies to a gateway that forwards your own, unmodified Claude Code, and Anthropic may act on its terms without notice. Check the terms before you rely on it.
What does Tempr charge for this?
Nothing per token: the Claude plan pays Anthropic as before. Each request counts toward your Gateway plan's monthly requests: 10,000 on Free, 250,000 on Pro at $49 a month, and 2,000,000 on Scale at $249.
Point Claude Code at Tempr today.
One setting per developer. The plan keeps paying; the team gets the logs.