Badges

GET /api/v1/badges/{credential_type} serves the official badge images for a credential. The endpoint is public — no API key — so you can embed it directly on any page, including pages you don’t control like a token listing.

Options

Parameter	Values	Default
`credential_type` (path)	`kyi_verified`, `proof_of_collateral`	—
`variant`	`icon`, `full`	`icon`
`theme`	`dark`, `light`	`dark`
`format`	`svg`, `png`	`svg`
`size`	`16`, `24`, `32`, `64`	`24`

icon is the square mark; full is the pill badge with the credential name. size applies to icon only and is ignored for full.
size=64 falls back to the 32 px asset — no 64 px icon exists.
webp is accepted as a value but returns 415 Unsupported Media Type — it isn’t available yet.

Every variant

KYI verified

kyi_verified · full · light

kyi_verified · full · dark

kyi_verified · icon · light

kyi_verified · icon · dark

Proof of Collateral

proof_of_collateral · full · light

proof_of_collateral · full · dark

proof_of_collateral · icon · light

proof_of_collateral · icon · dark

Embed it

<a href="https://verified.bluprynt.com/verified-assets/<address>/<chain>">
  <img
    src="https://integrations.bluprynt.com/api/v1/badges/kyi_verified?variant=full&theme=light"
    alt="KYI Verified by Bluprynt"
    height="32"
  />
</a>

Always link the badge to the asset’s verified page (the asset_url from an asset lookup) so anyone can check the claim behind it.

Caching

Badge responses are immutable:

Cache-Control: public, max-age=31536000, immutable

Cache and CDN them freely — the URL parameters fully determine the image. When a badge changes, the URL changes.

curl -s -o kyi.svg -w "%{http_code} %{content_type}\n" \
  "https://integrations.bluprynt.com/api/v1/badges/kyi_verified?variant=full"
# 200 image/svg+xml

Errors

All errors return a JSON body even though the route serves images:

Status	Body	Cause
`400`	`{"message":"Invalid credential_type \"x\". Allowed: kyi_verified, proof_of_collateral",…}`	Unknown credential type in the path.
`400`	`{"message":"Invalid format \"gif\". Allowed: svg, png, webp",…}`	Unsupported `format` value.
`400`	`{"message":"Invalid theme \"x\". Allowed: dark, light",…}`	Unsupported `theme`.
`400`	`{"message":"Invalid variant \"x\". Allowed: icon, full",…}`	Unsupported `variant`.
`400`	`{"message":"Invalid size \"x\". Allowed: 16, 24, 32, 64",…}`	Unsupported `size`.
`404`	`{"message":"Badge not available",…}`	The combination is valid but no asset exists for it.
`415`	`{"message":"WebP badges are not yet available. Use svg or png.",…}`	`format=webp`.

FAQ

Why is badge serving public while every other route needs a key?

The badge only displays a public verification status — it leaks nothing. Requiring a key would make it impossible to embed on third-party sites, which is its purpose.

Which theme should I use?

Match the surface the badge sits on. light for light backgrounds, dark for dark. The pill (full) reads better as a standalone element; the icon works inline next to a token name.

Does the badge image reflect live verification state?

The badge is a static claim image — it doesn’t check state at render time. Resolve the verification first with an asset lookup, then show the badge only when the asset is verified.

Recipe: KYI badge — the end-to-end walkthrough
Asset lookup — get asset_url and the verification state to gate the badge

KYI Widget SDK

Public API

Explorer API

Options

Every variant

KYI verified

Proof of Collateral

Embed it

Caching

Errors

FAQ

​Options

​Every variant

​KYI verified

​Proof of Collateral

​Embed it

​Caching

​Errors

​FAQ

​Related

Options

Every variant

KYI verified

Proof of Collateral

Embed it

Caching

Errors

FAQ

Related