Does Claude's API output carry the watermark?
For developers: whether text from the Anthropic API is marked, which models, and what it means for products built on Claude.
Removing the watermark · 2 min read
Short answer: yes. Anthropic applies the mark at the model level, which means it does not matter which surface the text came from — the app, claude.ai, the API, or your own product built on top.
Why model-level matters
If watermarking were applied at the product layer, API output could plausibly be exempt. It is not. Anthropic's documentation states marking is applied at the model, so every route to that model inherits it.
For anyone shipping a product on Claude, that has direct consequences:
- Text your app generates for end users carries the mark.
- Your users cannot opt out, and neither can you.
- The mark travels with the text when it is copied out of your product.
Which models
Every Claude model launched on or after 2 August 2026 marks generated text at launch. Support for models released before that date is described by Anthropic as "in progress".
So model choice currently affects this. If you are pinned to an older model, its output may not be marked yet — but "in progress" means that will change, and pinning to an old model to avoid marking is a plan with an expiry date.
What it means for your product
If you generate user-facing prose — marketing copy, summaries, drafts — that output is marked, and your users may not know. Whether you disclose that is a product decision, but the EU AI Act's transparency obligations sit with providers of generative systems, and depending on how you deploy, that may include you rather than only Anthropic.
If you generate structured output — JSON, code, short field values — the mark is far less relevant. Anthropic states very short passages lack enough text for reliable detection. A model returning a 12-token JSON object is not carrying a usable signal.
If you post-process output — summarising, templating, mixing with your own content — Anthropic lists "mixing with other content" among the things the mark may not survive. Heavy templating likely degrades it as a side effect.
What you cannot do
Check for it. Anthropic has not published a detection mechanism, so you cannot audit your own pipeline's output for the mark, and you cannot verify whether your post-processing removed it. That is an unusual position to be in as an engineer: a signal you know is present, that you cannot measure.
Practical notes
- Do not build a feature that promises watermark-free output. You cannot test it, so you cannot support the claim.
- Do strip the character layer. Claude output contains em dashes, curly quotes and U+2026 heavily. If your product writes to a system that expects ASCII, or you care about consistent typography, normalise it. That part is deterministic and testable.
- Watch for the detector. When Anthropic publishes its detection documentation, anything you assumed about your pipeline becomes measurable. Design so that finding out does not break a promise you already made.
Related: does Anthropic watermark Claude's text? · EU AI Act Article 50 · how to remove it
Sources: Anthropic Help Center