Asset Info

GET /v1/assets/:asset

Get comprehensive information about a specific native asset including supply data and metadata.

Parameters:

Parameter	Type	Description
asset	string	Asset identifier in format {policy_id}.{asset_name} where policy_id is 56 hex characters and asset_name is 0-64 hex characters

Query Parameters:

Parameter	Type	Default	Description
metadata_source	string	auto	Force metadata from specific source: auto, cip68, cip25, or registry

Example Request:

# IAG token with auto metadata
curl -X GET "https://api.insight.iagon.com/v1/assets/5d16cc1a177b5d9ba9cfa9793b07e60f1fb70fea1f8aef064415d114.494147" \
  -H "Authorization: Bearer YOUR_API_KEY"

# Force CIP-25 metadata
curl -X GET "https://api.insight.iagon.com/v1/assets/5d16cc1a177b5d9ba9cfa9793b07e60f1fb70fea1f8aef064415d114.494147?metadata_source=cip25" \
  -H "Authorization: Bearer YOUR_API_KEY"

# Force Token Registry metadata
curl -X GET "https://api.insight.iagon.com/v1/assets/5d16cc1a177b5d9ba9cfa9793b07e60f1fb70fea1f8aef064415d114.494147?metadata_source=registry" \
  -H "Authorization: Bearer YOUR_API_KEY"

# Policy-only token (empty asset name)
curl -X GET "https://api.insight.iagon.com/v1/assets/5d16cc1a177b5d9ba9cfa9793b07e60f1fb70fea1f8aef064415d114." \
  -H "Authorization: Bearer YOUR_API_KEY"

Response:

Content-Type: application/json;charset=utf-8

{
  "success": true,
  "data": {
    "policy_id": "5d16cc1a177b5d9ba9cfa9793b07e60f1fb70fea1f8aef064415d114",
    "asset_name": "494147",
    "asset_name_ascii": "IAG",
    "fingerprint": "asset1nzfpk7mtqc40pnzyf5daqy3csqcff6rjzqstgj",
    "total_supply": "1000000000000000",
    "mint_count": 1,
    "burn_count": 0,
    "first_mint_tx": "abc123def456...",
    "first_mint_slot": 58461241,
    "first_mint_time": "2022-03-15T10:30:00Z",
    "metadata": {
      "name": "Iagon",
      "ticker": "IAG",
      "description": "Iagon decentralized storage protocol token",
      "decimals": 6,
      "image": "ipfs://QmXyz...",
      "url": "https://iagon.com"
    },
    "metadata_source": "registry"
  }
}

Content-Type: application/json;charset=utf-8

{
  "success": false,
  "error": "Asset not found"
}

Content-Type: application/json;charset=utf-8

{
  "success": false,
  "error": "Invalid asset identifier format. Expected: {policy_id}.{asset_name} where policy_id is 56 hex characters"
}

Response Fields:

Field	Type	Description
policy_id	string	56-character hex policy ID
asset_name	string	Hex-encoded asset name (may be empty)
asset_name_ascii	string | null	ASCII representation if valid UTF-8, null otherwise
fingerprint	string	CIP-14 fingerprint (asset1...)
total_supply	string	Current circulating supply (mints - burns)
mint_count	integer	Number of mint transactions
burn_count	integer	Number of burn transactions
first_mint_tx	string	Transaction hash of first mint
first_mint_slot	integer	Slot number of first mint
first_mint_time	string	ISO 8601 timestamp of first mint
metadata	object | null	Asset metadata (see below)
metadata_source	string | null	Source of metadata: cip68, cip25, registry, or null

Metadata Object Fields:

Field	Type	Source	Description
name	string	All	Human-readable name
ticker	string	CIP-25/Registry	Short ticker symbol
description	string	All	Description text
decimals	number	CIP-68/Registry	Decimal places (default 0)
image	string	All	Image URI (ipfs://, https://, or data:)
url	string	All	Project website
logo	string	Registry only	Base64 encoded logo

---

Understanding Metadata Sources

Important

Asset metadata on Cardano can come from multiple sources, and different sources may return different data for the same asset. If you receive unexpected metadata, try forcing a specific source using the metadata_source query parameter.

Metadata Source Priority

When metadata_source=auto (default), the API checks sources in this order and returns the first successful result:

1. CIP-68 (On-chain datum) - Most authoritative for newer NFTs
2. CIP-25 (On-chain tx_metadata) - Common for older NFTs
3. Token Registry (Off-chain GitHub) - Fallback for fungible tokens

When to Force a Specific Source

Scenario	Recommended Source
NFT with on-chain metadata	cip68 or cip25
Fungible token (like IAG)	registry
Getting wrong image/name	Try each source to find correct data
Debugging metadata issues	Compare all three sources

Source Details

CIP-68 (cip68)

• Stores metadata in a reference token's datum on-chain
• Most reliable for tokens that use this standard
• Common for newer NFT collections

CIP-25 (cip25)

• Stores metadata in tx_metadata label 721 during minting
• Very common for NFTs minted 2021-2023
• Data is immutable once minted

Token Registry (registry)

• Off-chain registry maintained on GitHub
• Requires project to submit metadata
• Common for fungible tokens (ADA, IAG, SUNDAE, etc.)
• Can be updated by project owners