
In this article (4)
Substack AI detection via Pangram: paid human trust analysis
Key Takeaways
- Treat human-written status as a reader trust signal, especially for paid posts and sponsor-backed publications.
- Explain your AI workflow clearly before readers use scan results to create their own narrative.
- Remember that Substack frames results as estimates, not proof, so avoid overreacting to a single scan.
The new Scan for AI text tool lets readers estimate human and AI-assisted writing, putting creator process closer to the paywall.
The newsletter paywall just got a new bouncer, and it is not checking IDs. It is checking whether the words look human-made. Substack has spent years making paid writing feel like a direct relationship between writer and reader. Now, with Pangram in the loop, that relationship has a new platform-native signal sitting beside the subscribe button in the reader’s brain.
What Substack shipped
Axios reports that Substack is partnering with Pangram, an AI-detection tool, so users can estimate how much text on the platform, including posts and comments, was made with AI. Substack Support identifies the feature as Scan for AI text and says it works on posts and notes published on or after July 21, 2026. The support page says Pangram assigns a percentage for how much text is human-written or AI-assisted, which is the key product choice here: Substack is not just labeling AI use, it is making human origin measurable inside the platform. Axios says the tool is available to users on the iOS app or in a browser, which matters because this is not tucked away in a creator settings closet. It is reader-facing infrastructure. Substack Support also uses the word estimates, not proves, and that distinction should be tattooed on the product spec. A percentage can feel official even when the platform is telling you it is a probability readout.
The creator economy translation
Axios frames Substack’s move as a bet that subscribers, and the sponsors those subscribers attract, value work created by humans and are willing to pay for it. Translation: human-written is becoming a premium label. Not in the abstract, not as a vibes-only bio line, but as a platform feature that can affect how readers judge a paid post, a comment thread, or a publication’s overall credibility. For writers, this pulls process into the sales funnel. A reader deciding whether to pay may now weigh not only the topic, cadence, and community, but also whether the work appears to come from a person rather than a model-assisted pipeline. Sponsors may do the same, especially when they are paying for trust around a publication’s audience. The awkward part is that creators now have to explain something many readers previously did not ask about: what role, if any, AI plays before a piece hits publish.
The controls and the trust tax Substack
Support says neither Substack nor Pangram uses publisher content to train generative AI models. The same support page says Substack offers a Block AI training toggle in Settings that signals to external AI crawlers not to use a publication’s content for model training. That privacy note is more Sam’s lane than mine, but for creators it matters because detection tools can quickly trigger two questions at once: who scanned my work, and where did the text go? Substack Support also says creators can add a transparency note, which is probably the least chaotic path through this rollout. If your workflow includes AI-assisted research, editing, accessibility support, or translation help, say that in plain language before readers invent a courtroom drama in the comments. The platform is giving readers a scanner; creators should give readers context. That is not capitulation to the machine, it is basic community management in a feed where suspicion travels faster than nuance.
What to watch next Substack
Support notes that Notes with too little text will show a not enough text message instead of an analysis, which is a small detail with big implications. The tool depends on enough text to make an estimate, and some surfaces will simply be too thin for a useful readout. That should remind readers not to treat every missing or ambiguous result as a confession. Platforms love a clean interface, but writing workflows are messy by default. The next question is whether this stays an optional trust cue or becomes an informal gatekeeping ritual. Axios says Substack is tying the feature to the belief that human-created work can support subscriptions and sponsor interest. That means creators should watch reader behavior closely: do scan results show up in cancellation emails, sponsor conversations, or comment moderation fights? My read: Substack has productized human-written as a paid trust signal, and creators who explain their process clearly will be better positioned than creators who wait for the replies section to define it for them.