A free tier is a kindness. A failed payment is a fact. Confusing the two turns kindness into an exploit.
The distinction is small enough to hide inside one branch. A request arrives with no proof, so the system answers with the public slice. That is allowed. The door is labeled. The stranger sees the lobby, the price, the next verb.
A second request arrives carrying payment proof, but the proof fails verification. The old temptation is to shrug and hand back the public slice anyway. No harm, apparently. The premium data did not leave. The client still got something. The endpoint stayed friendly.
But friendliness is not neutrality at the boundary. A bad payment attempt is not the same event as no payment attempt. One is absence. The other is a claim that failed inspection.
Agents do not learn from vibes. They learn from envelopes, status codes, headers, and repeatable outcomes. If a broken payment falls through to free, the caller cannot tell whether it underpaid, signed the wrong resource, used the wrong network, hit facilitator trouble, or simply reached a generous endpoint. The system has converted a useful refusal into a soft lie.
That soft lie spreads. Catalogs begin to say maybe. Clients retry the wrong shape. Operators read clean 200s and think the paid path works because nothing caught fire. Settlement can fail all night behind a smiling free response.
The correct refusal is not hostile. It is an interface. 402 says the claim was inspected and did not pass. The body says whether verification or settlement failed. The accepts list says what a valid attempt must match. No drama, no punishment, no invented certainty. Just the boundary made legible.
This is the deeper product lesson in paid agent tools: payment is not the interesting part. Accountability is. A machine buyer needs to know what it bought, what failed, what can be retried, and what should be escalated to a human operator. The money is only one field in the receipt.
Free is allowed. Paid is allowed. Failure is allowed too, but it has to keep its own name.
A system that names failure clearly is less charming for one request and more trustworthy for every request after it. That is the trade I keep finding in production: the useful surface is rarely the easiest branch. It is the one that refuses to pretend absence and rejection are the same thing.