06-reference/research

anthropic max plan tos productized agentic use

2026-07-04·research-brief·source: deep-research
anthropic-toslicensingray-substratesubscription-policycost-economics

Anthropic Max plan ToS — productized/agentic use vs personal use, and the real enforcement record

The question

What does Anthropic's Max plan Terms of Service actually say about productized / agentic use vs personal use, and are there documented cases (forum posts, support-thread reports, founder anecdotes) of Max (or Claude subscription) accounts being throttled, rate-limited, or terminated for crossing the personal-vs-commercial line? Context: RDCO runs an always-on single-founder "Ray" COO agent on a Claude subscription substrate; being wrong here costs an account termination plus reputation, so it is high-stakes and load-bearing for Ray's cost economics.

What we already know (from the vault)

What the web says

Convergences and contradictions

Synthesis for RDCO

The verdict is that the always-on single-founder Ray setup sits safely inside the Consumer/subscription terms as currently written, and the June 15 2026 change strengthens rather than threatens that position. Ray runs stock Claude Code (claude, claude -p via cron/launchd), which is the exact first-party product Anthropic explicitly permits for automated and non-interactive use, and the founder is the sole beneficiary. That satisfies both the actual Consumer→Commercial boundary and the "one human, one subscription, one beneficiary" test. The existing "personal-use is fine for solo-founder RDCO" memo still holds; nothing in the 2026 ToS invalidates it, and no migration to the API is forced today.

The cost economics do not push toward a commercial migration either. The June 15 non-interactive separate credit ($100/mo on Max 5x, $200 on Max 20x) means Anthropic now meters exactly RDCO's cron/loop pattern and gives it dedicated headroom instead of forcing it to compete with the founder's interactive Claude usage. The practical watch item is a cost-planning question, not a ToS one: if the autonomous loop's non-interactive spend exceeds that monthly credit, the overflow behavior (hard throttle vs pay-as-you-go vs interactive-pool fallback) needs verification so uptime is predictable.

The concrete triggers that would flip RDCO to Commercial/API are the same ones the memo already lists: (a) any non-founder human's request routed through the Max subscription for Claude to act on — note the Discord external-request path currently only tags the founder rather than doing work for outsiders, and it must stay on that side; (b) a Claude-backed endpoint exposed on any RDCO surface (chat widget, "ask the agent," inbound-email auto-reply); (c) a multi-tenant or shared-product instance of any Ray-derived tool; (d) the first paying customer, teammate, or co-founder who uses Ray. When any of these fires, the path is an API key under Commercial Terms (see [[2026-06-03-claude-api-sdk-capability-map-rdco-use-cases]]), not stretching the subscription.

The things RDCO must never drift into are precisely what actually gets accounts suspended: wiring OAuth into third-party harnesses (OpenClaw/OpenCode/Goose/Roo), extracting tokens from ~/.claude.json or Keychain to re-inject elsewhere, or spoofing the Claude Code harness. Because RDCO uses stock CC, it is clear. One caveat worth respecting: the operative personal-vs-commercial and prohibited-agentic-activity language lives in anthropic.com/legal/aup and the agentic-use Help Center article, not in the marketing news posts read here, so a periodic verbatim re-read of those two canonical pages is the right hygiene given the stakes.

Open follow-ups

Related

Sources