Data Model

The RWA.xyz data model captures the full lifecycle of tokenized real-world assets — from the legal entity that issues a product, to the on-chain tokens that represent it, to every mint, burn, and transfer.

How It Fits Together

Consider BlackRock’s BUIDL fund. In the data model:

BUIDL is an Asset — the tokenized financial product itself
BlackRock USD Institutional Digital Liquidity Fund is the Issuer — the legal vehicle (an SPV/trust)
BlackRock Fund Advisors is the Manager — the entity managing the portfolio
Securitize is the Platform — the entity that deploys tokens on-chain
Ethereum BUIDL and Polygon BUIDL are Tokens — separate on-chain deployments of the same asset
Ethereum and Polygon are Networks — the blockchains those tokens live on
Anchorage Digital is a Service Provider — the crypto custodian for the fund
Every mint and redemption is a Transaction

Core Entities

Asset

A tokenized financial product. One asset can have multiple tokens across different blockchains and platforms. Examples: USDC, BUIDL, USYC API endpoint: GET /v4/assets | Schema: Asset fields

Example response

{
  "id": 51,
  "name": "Circle USYC",
  "slug": "circle-usyc",
  "ticker": "USYC",
  "asset_class_name": "US Treasury Debt",
  "issuer_name": "Circle",
  "is_yield_bearing": true,
  "token_count": 3,
  "network_names": ["Ethereum", "Solana", "Polygon"],
  "market_cap_dollar": {
    "val": 1200000000,
    "val_7d": 1150000000,
    "chg_7d_pct": 4.35
  },
  "yield_to_maturity_percent": {
    "val": 4.32
  }
}

Token

A specific on-chain deployment of an asset on a particular network and platform. This is where blockchain-native data lives — contract addresses, token standards, transfer restrictions. Examples: Ethereum USDC, Polygon BUIDL, Solana USYC API endpoint: GET /v4/tokens | Schema: Token fields

Example response

{
  "id": 20,
  "name": "Circle USYC (Ethereum)",
  "asset_id": 51,
  "address": "0x136471a34f6ef19fe68e26ea0c4b5b3db652565f",
  "decimals": 6,
  "standards": ["ERC-20"],
  "network_name": "Ethereum",
  "protocol_name": "Securitize",
  "transferability_type": "Transferable within whitelist",
  "market_value_dollar": {
    "val": 950000000,
    "val_7d": 920000000,
    "chg_7d_pct": 3.26
  },
  "holding_addresses_count": {
    "val": 142
  }
}

Issuer

The entity that legally issues the asset. For a fund, this is the investment vehicle (trust, SPV, etc.), not the sponsor or manager. Examples: Circle, BlackRock USD Institutional Digital Liquidity Fund, Superstate Trust API endpoint: GET /v4/issuers

Example response

{
  "id": 1,
  "name": "BlackRock",
  "slug": "blackrock",
  "legal_name": "BlackRock, Inc.",
  "website": "https://www.blackrock.com",
  "legal_structure_type": "Corporation",
  "legal_structure_country_name": "United States",
  "asset_count": 3,
  "token_count": 8,
  "bridged_token_value_dollar": {
    "val": 2500000000,
    "val_7d": 2400000000,
    "chg_7d_pct": 4.17
  }
}

Platform

The entity that deploys tokens on a network. Sometimes the platform is the same as the issuer (e.g., Circle deploys USDC itself). Other times it’s a separate entity (e.g., Securitize deploys BUIDL on behalf of BlackRock). Examples: Circle, Securitize, Centrifuge API endpoint: GET /v4/platforms

In the API, platforms are referenced as protocol in field names (e.g., protocol_id, protocol_slug) for historical reasons. The terms are interchangeable.

Example response

{
  "id": 16,
  "name": "Securitize",
  "slug": "securitize",
  "asset_count": 12,
  "circulating_asset_value_dollar": {
    "val": 2500000000,
    "val_7d": 2400000000,
    "chg_7d_pct": 4.17
  }
}

Network

The blockchain network that a token is deployed on. Networks can have parent-child relationships (e.g., Arbitrum is an L2 on Ethereum). Examples: Ethereum, Polygon, Solana, Arbitrum API endpoint: GET /v4/networks

Example response

{
  "id": 1,
  "name": "Ethereum",
  "slug": "ethereum",
  "parent_network_id": null,
  "token_count": 245,
  "asset_count": 180,
  "bridged_token_market_cap_dollar": {
    "val": 1350000000,
    "val_7d": 1320000000,
    "chg_7d_pct": 2.27
  },
  "holding_addresses_count": {
    "val": 52341
  }
}

Manager

The entity responsible for managing an RWA fund or portfolio. Not all assets have a manager — stablecoins like USDC typically do not. Examples: BlackRock Fund Advisors, Reental America, Fasanara Capital API endpoint: GET /v4/managers

Example response

{
  "id": 74,
  "name": "Reental America",
  "slug": "reental-america",
  "asset_count": 20,
  "website": "https://www.reental.co/en",
  "bridged_token_value_dollar": {
    "val": 29034335.51,
    "val_7d": 29050231.26,
    "chg_7d_pct": -0.05
  }
}

Service Provider

Entities involved in RWA operations. These include custodians, auditors, fund administrators, transfer agents, and other roles in the asset servicing chain. Examples: Anchorage Digital, BitGo, PwC API endpoint: GET /v4/service-providers

Example response

{
  "id": 1,
  "name": "Anchorage Digital",
  "slug": "anchorage-digital",
  "description": "Anchorage Digital is a federally chartered digital asset bank.",
  "network_ids": [1, 5, 12]
}

Transaction

An on-chain event involving an RWA token. Each transaction is classified as a mint (new tokens created), burn (tokens destroyed), or transfer (tokens moved between addresses). API endpoint: GET /v4/transactions

Example response

{
  "id": "1-0x9d60a645b0a92c98...-42",
  "date": "2026-03-17T00:00:00.000Z",
  "timestamp": "2026-03-17T11:02:59.000Z",
  "transaction_hash": "0x9d60a645b0a92c98...",
  "amount": 22331806.95,
  "usd_amount": 24995829.91,
  "from_address": "0xfd78ee919681417d...",
  "to_address": "0x0000000000000000...",
  "transaction_type": {
    "id": 2,
    "slug": "token-burn",
    "name": "Token Burn"
  },
  "token": {
    "id": "20",
    "asset_id": "51",
    "network_name": "Ethereum"
  },
  "asset": {
    "id": "51",
    "name": "Circle USYC",
    "asset_class_name": "US Treasury Debt"
  }
}

Relationships

From	To	Cardinality	Description
Token	Asset	Many-to-one	One asset can have multiple tokens across different networks and platforms
Token	Platform	Many-to-one	Each token is deployed by one platform
Token	Network	Many-to-one	Each token lives on one network
Asset	Issuer	Many-to-one	Each asset has one issuer; an issuer can have multiple assets
Asset	Manager	Many-to-one	Each asset may have one manager (optional)
Asset	Service Provider	Many-to-many	Assets can have multiple service providers in different roles
Transaction	Token	Many-to-one	Each transaction involves one specific token

Data Catalog

Browse all entities, fields, and measures interactively in the Data Catalog.

Home

Methodology

Frameworks

Data Schemas

MCP Server

API

How It Fits Together

Core Entities

Asset

Token

Issuer

Platform

Network

Manager

Service Provider

Transaction

Relationships

Data Catalog

​How It Fits Together

​Core Entities

​Asset

​Token

​Issuer

​Platform

​Network

​Manager

​Service Provider

​Transaction

​Relationships

​Data Catalog

How It Fits Together

Core Entities

Asset

Token

Issuer

Platform

Network

Manager

Service Provider

Transaction

Relationships

Data Catalog