Skip to main content
Tokenized real-world assets look like any other token on-chain: nothing in a contract tells you it represents a share of Apple stock, a T-bill, or a gram of gold. If your product has to treat regulated instruments differently, you end up maintaining address lists by hand and hoping you catch new listings. Zerion classifies these assets for you, so you can recognize a tokenized asset and what kind it is directly from the API response.
RWA classification is a paid add-on, enabled per organization. It is not part of the self-serve plans, and without it rwa_class is absent from responses. See Access below.

​
What gets classified

Fungibles carry an optional rwa_class attribute naming the kind of real-world value the asset represents: The attribute is returned on the fungibles endpoints:
  • GET /v1/fungibles/
  • GET /v1/fungibles/{fungible_id}
  • GET /v1/fungibles/by-implementation?implementation={chain}:{address}

​
Reading the field

Two behaviors matter if you build product logic on this attribute:
  • Absence is not a negative signal: the attribute is omitted when an asset is unclassified or its classification has been cleared. It does not assert that the asset is not an RWA. Treat a missing rwa_class as “no information”.
  • unknown is a positive classification: the asset was identified as a likely RWA with the specific class still pending. It is meaningfully different from the attribute being absent. Whether to block, flag, or simply label those assets depends on what you are building.

​
How assets are classified

Classification is issuer-driven rather than heuristic. Zerion tracks known real-world-asset issuers and the contracts they deploy, so an asset from a recognized issuer carries the same classification on every chain it appears on. Classifications set manually by Zerion’s asset team always take precedence over an inferred one. Coverage is strongest on the major issuers, which account for the large majority of tokenized-asset value, and expands as new issuers are onboarded. It is not exhaustive across the long tail of small tokenized assets.

​
What teams use it for

  • Product gating: restrict or hide regulated instruments for users in jurisdictions where you are not licensed to offer them.
  • Swap and trading guardrails: block quotes or routing on tokenized securities while leaving the rest of the token universe untouched.
  • Portfolio breakdowns: group holdings into stocks, treasuries, commodities, and stablecoins in your UI or reporting.
  • RWA discovery: surface tokenized-asset markets as a distinct category for users.

​
Access

RWA classification is a paid add-on to the Zerion API, enabled per organization. Until it’s enabled, rwa_class is absent from your responses. To request access, log in to the dashboard and message us through the support widget, or email us at api@zerion.io. If you already have a shared Slack or Telegram channel with us, reach out there.