> For the complete documentation index, see [llms.txt](https://glint-analytics.gitbook.io/glint-analytics/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://glint-analytics.gitbook.io/glint-analytics/querying-and-data-analysis/schema-reference/tokens-table.md). # Tokens Table Tokens are curated metadata that identify the key properties of a token and identify the token type. | Name | Type | Description | | -------------------------- | --------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------- | | `MODEL` | `TEXT` | The type of object model used during ingestion of metadata. | | `RETRIEVAL_TIMESTAMP` | `FIXED` | The raw value of the time in Unix Epoch time (in UTC time zone) in which the token is retrieved. | | `RETRIEVAL_DATETIME` | `TIMESTAMP_NTZ` | The timestamp in UTC in which the token was retrieved. | | `TOKEN_ADDRESS` | `TEXT` | The mint address of the token. | | `SYMBOL` | `TEXT` | The symbol of the token being searched. | | `NAME` | `TEXT` | The name of the token. | | `PUBKEY_ADDRESS` | `TEXT` | The Public Key of the token mint address. | | `UPDATE_AUTHORITY_ADDRESS` | `TEXT` | The update authority address for this token. | | `JSON` | `VARIANT` | If JSON metadata is appended to the object model, additional token metadata will be displayed here. | | `JSON_LOADED` | `BOOLEAN` | Boolean to determine if JSON metadata was added to the model. | | `URI` | `TEXT` | The URI to the token JSON metadata. | | `IS_MUTABLE` | `BOOLEAN` | Boolean to identify if token metadata attributes are mutable. | | `PRIMARY_SALE_HAPPENED` | `BOOLEAN` | Indicates whether the first sale occurred. | | `SELLER_FEE_BASIS_POINTS` | `FIXED` | The fee basis points for the seller of the token. | | `EDITION_NONCE` | `FIXED` | The nonce value for the token edition | | `CREATORS` | `VARIANT` | The creators associated with the token. | | `TOKEN_STANDARD` | `TEXT` | The enumerated token standard used, determines whether token is unknown, semi-fungible, non-fungible edition, or programmable non-fungible (in this order). | | `TOKEN_STANDARD_NAME` | `TEXT` | Label for the token standard. | | `COLLECTION` | `VARIANT` | The collection associated with the token. | | `COLLECTION_DETAILS` | `VARIANT` | The details of the collection associated with the token. | | `USES` | `VARIANT` | The uses of the token. | | `PROGRAMMABLE_CONFIG` | `VARIANT` | The programmable configuration of the token. | | `LEGACY_EXTENSIONS` | `VARIANT` | If legacy object was used, displays user provided extensions associated with this token. | | `LEGACY_LOGO_URI` | `TEXT` | If legacy object was used, displays user provided logo URI for this token. | | `LEGACY_TAGS` | `VARIANT` | If legacy object was used, displays user provided tags associated with this token. | | `MINT_AUTHORITY` | `TEXT` | n/a | | `SUPPLY` | `TEXT` | n/a | | `DECIMALS` | `FIXED` | n/a | | `FREEZE_AUTHORITY` | `TEXT` | n/a | | `MINT_DATA` | `VARIANT` | n/a | | `METADATA_DATA` | `VARIANT` | n/a | | `EDITION_DATA` | `VARIANT` | n/a | | `DATE_CREATED` | `TIMESTAMP_NTZ` | n/a | | `DATE_UPDATED` | `TIMESTAMP_NTZ` | n/a | 🔍 Use these columns to gather comprehensive insights into token properties on the blockchain, such as its mint address, symbol, and any associated metadata. This information can be leveraged to filter or categorize tokens in your analysis (e.g., by name, symbol, or metadata presence) and to gain insights into how tokens are managed or updated on the blockchain, along with other key attributes. You can: * Identify each token by its mint address, symbol, and name using `TOKEN_ADDRESS`, `SYMBOL`, and `NAME`. * Access key metadata details via `PUBKEY_ADDRESS` and `UPDATE_AUTHORITY_ADDRESS`. * Retrieve additional metadata from `JSON`, `JSON_LOADED`, and `URI`. * Determine if token attributes are mutable using `IS_MUTABLE` and verify primary sale status with `PRIMARY_SALE_HAPPENED`. * Evaluate fee and edition information through `SELLER_FEE_BASIS_POINTS` and `EDITION_NONCE`. * Categorize tokens by standards and collections with `TOKEN_STANDARD`, `TOKEN_STANDARD_NAME`, `COLLECTION`, and `COLLECTION_DETAILS`. * Understand token usage and programmable configurations with `USES` and `PROGRAMMABLE_CONFIG`. * Review legacy metadata (extensions, logo URI, tags) using `LEGACY_EXTENSIONS`, `LEGACY_LOGO_URI`, and `LEGACY_TAGS`. * Monitor data recency with `DATE_CREATED` and `DATE_UPDATED`. 💡 For example, you might query `TOKEN_ADDRESS`, `SYMBOL`, and `COLLECTION` to filter tokens based on their collection affiliation, among other parameters. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://glint-analytics.gitbook.io/glint-analytics/querying-and-data-analysis/schema-reference/tokens-table.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.