Trust, but resolve

Verify the mark

The Yellow Butterfly is not a static seal. Every badge resolves to a live entry in the public registry, so a product cannot keep displaying the mark after it has been suspended or revoked. Anyone can check a mark here.

Check a mark

Try one of the illustrative identifiers, for example draft-tutor-b-v3 or draft-companion-a-v1.

How a certified product displays the mark

The product shows the badge

A certifiable product may display the Yellow Butterfly on its surface, linked to its registry entry. The badge is a link, not a picture: it points at the live record.

Anyone resolves it

Following the badge, or entering the mark here, resolves to the product's current status: certifiable, in review, suspended, revoked, or not certified.

The registry is the truth

Because the badge resolves to the registry, a withdrawn mark reads as withdrawn everywhere automatically. There is no valid-looking badge on a revoked product.

For implementers

The verification endpoint

A vendor's site can resolve a mark programmatically. The endpoint returns the live status as JSON, so a badge can render its current state and refuse to show a valid mark for a withdrawn product.

# Resolve a mark to its live status

GET /api/verify/<mark-id>

# Example response

{
  "mark_id": "draft-tutor-b-v3",
  "found": true,
  "status": "certifiable",
  "withdrawn": false,
  "product": "Tutor B (draft entry)",
  "vendor": "An independent vendor",
  "version": "3.1",
  "floor_version": "0.1",
  "illustrative": true
}

The endpoint reads the same registry the public pages do, so a badge and the registry can never disagree.