The Hallmark · Embed
The embeddable Evidence badge
The owner of a Hallmarked engagement can show its badge on their own website or in a tender response. The badge fetches its state from the Register each time it renders, and links to the public record — so it cannot be forged by copying the image.
As it renders
The production Register has no issued Hallmarks yet, so the badge shown is a specimen. A live badge carries its real state in place of the specimen tag.
- Issued
- The Hallmark is in force on the Register.
- Superseded
- A later record replaces this one; the badge links to it.
- Not on the Register
- Withdrawn, revoked or unknown identifiers. The badge never claims a Hallmark it cannot find.
- Could not verify
- The Register could not be reached; nothing is asserted.
The embed
Two lines of code
Paste these where the badge should appear, replacing the specimen identifier AF-0000-0000-SPX with your engagement’s own. The script sets no cookies and makes a single request to the Register.
<!-- Assay — Evidence badge -->
<div data-assay-hallmark="AF-0000-0000-SPX"></div>
<script src="https://assayfoundation.org/widget/assay-hallmark.js" defer></script>Static-image fallback
Where script embeds are not permitted — many tender portals strip them — use the static badge image, linked to the canonical record. The image asserts nothing on its own; the link is the proof.
<a href="https://assayfoundation.org/register/af-0000-0000-spx">
<img src="https://assayfoundation.org/widget/badge/af-0000-0000-spx.svg"
alt="Assay Evidence badge AF-0000-0000-SPX — open the Register record" />
</a>How verification works
The badge checks itself
On render, the badge reads its identifier, requests the published Register (https://assayfoundation.org/register.json), matches the identifier and shows its current state. An issued Hallmark verifies; a withdrawn, revoked or unknown one reports “Not on the Register”.
The Register file is generated at build time and served with cross-origin access so the badge can verify from any site. It contains Hallmarked engagements only — proving records never receive a badge. The contract is stable: if the Register moves to a database-backed service, embedded badges keep working.