Skip to main content
Asset lookups return the KYI-verified record for a token: its identity, its issuer, and the on-chain wallets that can control it. Use them when you already know a token’s address and want the verification state behind it.

Key concepts

How it works

A 404 is a meaningful answer: the token is not KYI-verified — or it’s verified on a different chain. The same address can exist on several chains, so always include the chain.

Look up one asset

Look up by CAIP-10

Replace the : separators with /. This form covers chains without a short name:
Both forms return the same record.

Response reference

Real response (Plume USD, trimmed)

token_details

authorities[]

business_details

Top level

token_image is a signed S3 URL with X-Amz-Expires=3600 — it expires one hour after the response. Fetch the asset again instead of caching the URL.

List every verified asset

GET /assets returns the full set, paged:
Response shape
meta.total is the full verified count, so loop until page_number covers it.

Errors

See Errors for the full table.

FAQ

The token exists on-chain but isn’t KYI-verified, or you asked on the wrong chain. Token addresses repeat across chains — check the same address on other chains before concluding it isn’t verified.
The spec lists solana, ethereum, base, plume, sepolia and avalanche. For anything else use the CAIP-2 form, which accepts any namespace and reference.
The record is the current verified state. Values change when an issuer updates their disclosure or when a verification is renewed or revoked — fetch at display time rather than caching.