Check a badge
Paste the badge identifier from a "Verified by VibefyCode" mark — it is the part before .svg in the image URL — and this will tell you what VibefyCode actually attested, and whether it still stands.
Checking it without us
The signing keys are published at /.well-known/vibefycode-badge-key as a JWKS, and each badge's signed payload is at /api/badge/<identifier>. Any Ed25519 implementation can verify it offline. The response documents the exact canonicalisation, because two implementations must produce identical bytes or the signature check is meaningless.
Building something that shows our mark
A signature says an assessment happened. It does not say the badge is still live, and suspension is how a mark stops meaning anything — so there are two more addresses, both public, both open to any origin, neither needing a key or an account.
/api/badge/<identifier>/status— is this one live, what was it measured against, when, and when does it stop being current. Cached five minutes./api/badges/live— every live badge in one document, cached an hour, so that anything checking a lot of sites can do it locally. There is deliberately no “does this domain have a badge” lookup: it would let a browser extension report every page its user visits to us, and this list does the same job without being able to.