Data Model & Usage

A reference for the NFT Portal data model and how assets flow through the Revenue Rail.

NFTAsset Entity

Every NFT in the ecosystem is a single NFTAsset record. All portal pages read from and write to this entity — there is no separate public API.

FieldTypeDescription
namestringNFT name (required)
descriptionstringOptional description
image_urlstringCover image URL
site_idstringOriginating ecosystem site
tierenumPrediction · Sample · Full Card · Limited · Group Pack · Archive
chainenumSolana · Ethereum · Polygon
mint_pricenumberMint price (USD)
statusenumpending · minted · listed · sold
minted_atdatetimeWhen the NFT was minted
tx_hashstringOn-chain transaction hash
sale_pricenumberSale price (USD)
sold_atdatetimeWhen the NFT sold
appraisal_statusenumpending · certified
appraisal_valuestringCertified appraisal range

Revenue Rail Flow

  1. 1Receive & Source
  2. 2Appraise & Certify
  3. 3Mint & Make Available
  4. 4Distribute Across Sites
  5. 5Collect Revenue
  6. 6Report & Reinvest

Usage

  • Dashboard — counts and revenue computed live from NFTAsset.
  • Mint — creates a real NFTAsset record with status minted.
  • Marketplace — shows records where status is listed.
  • Reports — shows records where appraisal_status is certified.
  • Revenue — aggregates sale_price over sold_at.
  • Sites — NFT counts grouped by site_id.

There is no public REST API. All data access is through the portal's entity layer.

Powered by SciFiBot v4.1.2 · © 2026 xyztechteam, Global Consulting Business Trust · NFTs on Etsy

base44
Edit with Base44