Anthropic Says It Will Charge for Some Claude Requests Blocked Before an Answer

Anthropic said September 24 that it would resume charging for some Claude requests stopped by safeguards before Claude answers. The company cited coordinated attacks on its systems in recent weeks. Billing for blocked attempts could make repeated probing more costly, but the policy also means a mistaken block could carry a charge.

Which blocks would cost money

The change applies when a safeguard blocks a request before Claude responds, not whenever someone dislikes an answer. Anthropic limits the new charges to three categories: biology, distillation attacks and frontier LLM development.

These are categories of blocked requests, not a charge on every request about biology or AI development. Anthropic calls the policy one layer of defense against the attacks it says it has seen. Charging for a rejected attempt changes its cost, not whether the safeguard lets it through.

99.7%Accounts with no affected block

Anthropic says this share of Claude Code, Claude.ai and Cowork accounts encountered none of the newly billable blocks in recent testing.

Below 0.1%Classifier false-positive rate

Anthropic says the classifiers behind those blocks are tuned to a false-positive rate below this level.

Rare is not the same as impossible

The two figures measure different things. The account figure describes how often people in Anthropic’s recent testing avoided these blocks altogether. It does not say whether blocks seen by other accounts were correct. The false-positive figure describes how the classifiers are tuned, not the share of customers who will receive a mistaken charge.

Anthropic acknowledges that its false-positive rate is not zero and says it will keep improving the classifiers to interrupt work less often. A low overall rate cannot settle whether any particular block was justified. For a user whose legitimate request is stopped, the distinction now affects both the work and the bill.

How to flag a suspected mistake

Anthropic directs Claude Code users who think a request was blocked incorrectly to report it with /feedback. The announcement does not specify how a charge for a mistaken block would be handled. Feedback offers a way to flag the interruption, but the financial remedy remains unclear.

The September 24 post said charging would resume “today,” without giving a time for the switch. It announces a billing change; it does not confirm that charges had already appeared. For affected users, the first bills will show how the stated policy is applied to requests that produce no answer.