AI Provenance Mark
An AIPM record is a provenance URL — a plain HTTPS link with all provenance metadata encoded in its hash fragment. Nothing is sent to any server. From that URL you can generate a scannable QR mark, a clickable badge, or a formatted citation in text — all pointing back to the same record.
Pronounced "ape 'em" — rhymes with shape pum, phonetically ap-um.
Open Standard
Vendor-neutral and freely usable. No proprietary apps, no accounts, no tracking.
Declare AI involvement
From full AI generation to full human authorship — every meaningful level of involvement expressible in a single field.
Share your context
Provenance pages include direct links to open the context in Claude, ChatGPT, Gemini, and others — one click to continue the conversation that created the content.
What's New in 1.2
| Feature | Description |
|---|---|
| File integrity hashing | hs and hd store SHA-256 or SHA-384 hashes of the content file and Full Context Document in W3C SRI format (sha256-base64url) — algorithm-agile for 30-year durability. Anyone can drag-and-drop or paste a hash (SRI, base64url, or hex — auto-converted) to verify the file is unchanged since marking. |
Content type (type) |
Declares the media type — text, code, image, audio, video, multimodal. Recommended for disclosure under EU AI Act Article 50, where obligations differ by content type. |
Wrote role (role=wrote) |
New role for the most common AI-assisted writing scenario: you wrote the content, AI corrected grammar or clarity, you reviewed and approved. Show mode abbreviation: W. Intellectual authorship is fully human. |
| Automated role | New role=automated for AI-generated content with no human involvement — publishing pipelines, automated systems. Show mode abbreviation: AI. Use org to identify the responsible party. |
| File upload to context | Drop a .txt, .md, .pdf, .docx, or other text file onto the context field in the generator. Text is extracted client-side — nothing is uploaded to any server. |
| JSON-LD output | Each provenance page now emits structured Schema.org JSON-LD in its <head>, making AIPM records discoverable by search engines and AI crawlers without scanning. |
| Copy as citation | One-click button on the provenance page generates a formatted citation string suitable for footnotes, README files, and acknowledgements sections. |
| EU AI Act alignment | The type and org fields support Article 50 disclosure requirements. The provenance page shows an Article 50 notice for AI-generated text, image, audio, and video content. |
How It Works
The provenance URL is the canonical record. It encodes who created the content, which AI model was used, what role the human played, and any context you choose to share — all in the URL itself, with nothing stored on any server.
- Generate a provenance URL using the generator — fill in the model, your role, and context.
- Share the record in whichever form fits your medium:
- A scannable QR mark — for print, slides, and images
- A clickable badge — for web pages, GitHub, and email
- A citation in text — for footnotes, acknowledgements, and README files
- The provenance URL directly — for hyperlinks and APIs
- Anyone scanning or clicking sees a clear, human-readable disclosure page showing exactly how the content was created.
A 1.2 Provenance URL looks like this
All metadata is encoded in the URL hash fragment — nothing is sent to any server.
https://aipmq.org/1.2/aipm/#v=1.2&model=Claude+Sonnet+4.6&role=prompted%2Breviewed&date=2026-05-03T14%3A30-04%3A00&ctx=Internal+memo+draft&show=1
View example provenance page →
A 1.2 QR Code looks like this
Generated locally in your browser using the example URL above. The AIPM mark is centered in the QR code.
Scan this code or open the AIPM URL directly →
For digital content — GitHub READMEs, blog posts, web pages — use an AIPM Badge instead:
The badge is a clickable link to the provenance page. Download all badge variants from the Marks & Badges page →
Generate a QR Code Read the 1.2 Specification