> ## Documentation Index > Fetch the complete documentation index at: https://tokenterminal.com/docs/llms.txt > Use this file to discover all available pages before exploring further. > ## Agent Instructions > To query the Token Terminal data catalog, read https://tokenterminal.com/docs/catalog/agents-manual.md first. It is the whole catalog as one page: table naming grammar, key columns, partition and cluster rules, units, additivity, and the tables that are documented but not served yet. > Never query a catalog table on a time bound alone. Also filter its cluster key, which you read from INFORMATION_SCHEMA.COLUMNS; an empty result means the object is a view, whose pruning contract is on its page. Compute is billed to the caller's own Google Cloud project. # Get a list of all assets > Use this endpoint to retrieve a list of all assets that are available on the API. ## OpenAPI ````yaml /api-reference/openapi.json get /v2/assets openapi: 3.0.0 info: title: Token Terminal API termsOfService: https://tokenterminal.com/terms version: 2.0.0 servers: - url: https://api.tokenterminal.com security: - bearerAuth: [] tags: [] paths: /v2/assets: get: tags: - Assets summary: Get a list of all assets description: > Use this endpoint to retrieve a list of all assets that are available on the API. parameters: - name: asset_ids in: query description: > List of asset IDs to filter by. Allows you to select one or more assets. When including multiple assets, separate each one with a comma. Example: `usdc,usdt`. explode: false schema: type: array items: type: string example: - usdc - usdt - name: asset_types in: query description: > List of asset types to filter by. Allows you to filter assets by their type. When including multiple types, separate each one with a comma. explode: false schema: type: array items: type: string - name: market_sectors in: query description: > List of market sector IDs to filter assets by. Allows you to select one or more market sectors to filter the results. Only assets belonging to any of the specified market sectors will be included. When including multiple market sectors, separate each one with a comma. Example: `blockchains-l1,lending`. The full list of available market sectors can be retrieved from the `/v2/market-sectors` endpoint. explode: false schema: type: array items: type: string example: - blockchains-l1 - lending - name: reference_asset_ids in: query description: > List of reference asset IDs to filter by. A reference asset is the price reference a tokenized asset tracks (for example `creditfund`, `sp500`, `btc`). Use this to select a specific slice of a broad `asset_type` — for instance tokenized credit funds only, rather than every tokenized fund. Assets that do not track a reference asset are excluded. The full list of available reference assets can be retrieved from the `/v2/reference-assets` endpoint. When including multiple reference assets, separate each one with a comma. explode: false schema: type: array items: type: string example: - creditfund - name: limit in: query description: Maximum number of assets to return. schema: type: integer minimum: 1 maximum: 1000 default: 1000 - name: offset in: query description: Number of assets to skip for pagination. schema: type: integer minimum: 0 default: 0 - name: has_fact_sheet in: query description: >- Filter by researched fact-sheet availability. True means a disclosure record exists; legacy description-only pages do not count. Applied before pagination and to total_count. schema: type: boolean responses: '200': description: OK content: application/json: schema: type: object properties: data: type: array items: type: object properties: asset_id: type: string description: >- Required input on the API when retrieving data for an asset. asset_type: type: string nullable: true description: The type of the asset. name: type: string description: The asset's name. symbol: type: string description: The asset's ticker symbol. coingecko_id: type: string nullable: true description: The CoinGecko ID for the asset. coinmarketcap_id: type: string nullable: true description: The CoinMarketCap ID for the asset. reference_asset_id: type: string nullable: true description: >- The price reference this asset tracks (for example `creditfund`, `sp500`, `btc`), or null if it tracks none. Resolve against the `/v2/reference-assets` endpoint. addresses: type: array description: >- List of addresses where the asset exists across different chains. items: type: object properties: chain_id: type: string nullable: true description: The chain ID where the asset exists. token_address: type: string nullable: true description: The token contract address on the chain. token_name: type: string nullable: true description: The token name on the chain. token_symbol: type: string nullable: true description: The token symbol on the chain. products: type: array description: List of products associated with this asset. items: type: object properties: data_id: type: string description: The project data ID. product_id: type: string description: The product ID. tags: type: array items: type: string description: Tags associated with the product. relation_to_the_project: type: string nullable: true description: >- The relationship of the asset to the project (e.g., "issuer"). logo: type: string nullable: true description: URL of the product's logo. created_at: type: string description: Timestamp when the asset was created. inserted_at: type: string description: >- Timestamp when the asset was inserted into the database. first_onchain_data_at: type: string nullable: true description: >- Timestamp of the asset's earliest on-chain data point, or null if it has no on-chain data yet. chain_ids: type: array items: type: string description: >- The chains the asset has metric data on. This can be narrower than `addresses`, which lists every chain the asset is configured on. has_fact_sheet: type: boolean description: >- Whether a researched fact sheet is available from /v2/assets/{asset_id}/fact-sheet. total_count: type: integer description: >- Total number of assets matching the filters, ignoring `limit` and `offset`. components: securitySchemes: bearerAuth: type: http scheme: bearer bearerFormat: string ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.