The Hallmark
The embeddable Hallmark
A Hallmarked Engagement may carry its Hallmark on the owner's own website or in a response to a tender. The embed verifies itself against the Register each time it renders, so a Hallmark cannot be forged by copying the image alone.
The production Register opens empty, so the badge below is an illustrative specimen. A real badge renders exactly this way and, on a genuine Engagement, verifies live against the Register.
Specimen · illustrative only
On a live Engagement the badge fetches its own status from the published Register (https://assayfoundation.org/register.json). If the identifier is withdrawn, superseded, or unmatched, the streak desaturates and the verification line reads the true status — tamper-evidence by construction, not decoration.
Paste two lines into the page where the Hallmark should appear. Replace the identifier with the Engagement's own. The script is lightweight, sets no cookies, and makes a single request to the Register.
<!-- The Assay Foundation — Hallmark widget -->
<div data-assay-hallmark="AF-2026-0001-OII"></div>
<script src="https://assayfoundation.org/widget/assay-hallmark.js" defer></script>Static-image fallback
Where script embeds are not permitted — many RFP portals strip them — a static badge image links back to the canonical record, which carries the live verification. The image asserts nothing on its own; the link is the proof.
<a href="https://assayfoundation.org/register/af-2026-0001-oii">
<img src="https://assayfoundation.org/widget/badge/af-2026-0001-oii.svg"
alt="Hallmarked by The Assay — IDEA III, OII, 2026, AF-2026-0001-OII" />
</a>On render, the widget reads its identifier and requests the Foundation's Register. It matches the identifier, reads the Engagement's current status, and renders accordingly. A current Engagement verifies; a withdrawn, superseded, or unknown one does not, and says so.
For this release the Register is a published file, generated at build time, served with cross-origin access so the badge can verify from any site. It contains production (Hallmarked) Engagements only — so a badge becomes verifiable precisely when its Engagement is Hallmarked and entered on the Register, and not before. The verification contract is stable: when the Register moves to a database-backed service, the badge will point at the new endpoint without any change to an embedded page.