# Authentication Source: https://docs.messari.io/api-reference/authentication All Messari API endpoints require an API key for authentication. ### Generating an API Key Messari API Key Generation Interface ### Access the API Dashboard Navigate to the [API Access page](https://messari.io/account/api) in your Messari account. Your API Key will be visible at the top of the page. ## Using the API Key The API key must be included in the request headers using the `x-messari-api-key` header field: ```json theme={null} { "headers": { "x-messari-api-key": "YOUR_API_KEY_HERE" } } ``` ## Permissions API access is tiered based on your subscription level. By default, all users have access to the [Assets & Market Data](/api-reference/endpoints/metrics/metrics-api) and [Exchanges](/api-reference/endpoints/exchanges/exchanges-api) API endpoints. For access to additional endpoints and services such as Fundraising, Intel, News & Topics, and more, please contact [sales@messari.io](mailto:sales@messari.io). ### Example Request (cURL) The following example demonstrates how to send a request to the Messari API using cURL with the `x-messari-api-key` header: ```bash theme={null} curl --location 'https://api.messari.io/ai/v1/chat/completions' \ --header 'x-messari-api-key: YOUR_API_KEY_HERE' \ --header 'Content-Type: application/json' \ --data '{ "messages": [ { "role": "user", "content": "Briefly explain what the Hyperliquid HyperEVM is" } ], "verbosity": "succinct", "response_format": "markdown" }' ``` ## Security Best Practices Never share your API key publicly or commit it to version control Store API keys in environment variables rather than hardcoding them Periodically update your API key for security purposes # Agents API Source: https://docs.messari.io/api-reference/endpoints/ai/agents-api Call Messari's Search and Compute agents directly and write the answer yourself. Copilot answers a question for you: it picks the agents, runs them, and synthesizes prose. The Agents API gives you the agents on their own. Each one does its half of the work and hands back structured output, and **you** write the answer. Reach for these endpoints when you are building your own agent or product flow and want Messari's retrieval and text-to-SQL as components rather than a finished answer. Retrieves source documents from Messari's research and news corpus. Returns the documents, not an answer. Turns a question into SQL over Messari's quantitative datasets and returns the executed query and its rows. ## Which agent to call | Use | Endpoint | | - | - | | Explanations, background, news, governance, diligence — anything needing text evidence you can cite | Search | | Numbers, rankings, aggregates, time series — price, volume, TVL, fees, revenue, supply, funding | Compute | Ask one thing per call. Several focused calls beat one loaded query. ## Search responses `sources` holds the retrieved documents. Each carries a `domain` (`research`, `news`, `external_news`, `diligence`, `governance`, `twitter`, `video_transcript` and others), a `title`, a `url`, the document `content`, and `published_at` where the domain carries a date. There is no synthesized answer and no citation numbering. Cite the `title` and `url` of every document you use, and state no fact the documents do not support. `error` is set only when a run finds no usable document, and explains why. ## Compute responses `results` holds each query the agent ran. `query` is the executed SQL, `query_result` holds the rows JSON-encoded as an array of arrays, and `columns` names each position in those rows, which are otherwise unlabelled. `truncated` reports that the row cap was reached, so more rows may match. `query_error` explains why an individual query returned nothing. The SQL and column names reflect Messari's internal schema, which may change without notice. Read them, do not parse them. `error` is set only when a run produces no usable result. ## Authorization These endpoints require an authenticated **Enterprise** user whose team holds the `ai_toolkit_permission` API permission, shown as **Messari AI API** in team settings. A caller without it receives `403`. Refer to our [Authentication](/api-reference/authentication) docs for creating an API key. ## Rate limits Each endpoint allows **30 requests per minute per user**, counted in its own bucket — Search traffic does not consume Compute's allowance. Exceeding a bucket returns `429`. ## Credits These endpoints do not consume AI credits. [Get in touch](https://blockworks.com/contact) about access. # AI API Source: https://docs.messari.io/api-reference/endpoints/ai/ai-api AI-powered APIs for crypto research and analysis using Messari's knowledge graph. The Messari AI API provides three services for programmatic access to AI-powered crypto intelligence: Real-time chat completions for contextual crypto responses. Supports OpenAI-compatible, Vercel AI SDK, and Messari native formats. Messari's Search and Compute agents on their own, returning documents and query results for you to write the answer from. Asynchronous long-form research report generation on any crypto topic, backed by cited sources. ## Authorization Refer to our [Authentication](/api-reference/authentication) docs for creating an API key. ### Pay-Per-Request with x402 No API key? Copilot chat completions are also available via [x402 micropayments](/api-reference/x402-payments) — pay per request with USDC on Base Mainnet, no account required. Deep Research is not currently available through x402. ### AI Credits Copilot and Deep Research consume credits per request; the Agents endpoints do not. [Get in touch](https://blockworks.com/contact) about enrolling in our consumption-based credit system. # Chat Completions API Source: https://docs.messari.io/api-reference/endpoints/ai/chat-completions-api AI-powered chat endpoints for crypto insights using Messari's knowledge graph. The Copilot family of Chat completion endpoints are used for generating contextual crypto responses using Messari's knowledge graph and specialized tools. The family offers three endpoint options for generating contextual crypto responses using Messari's knowledge graph: * [Chat Completions (Messari v2)](/api-reference/endpoints/ai/post-v2-chat-completions) * [Chat Completions (OpenAI compatible)](/api-reference/endpoints/ai/post-openai-chat-completions) * [Chat Completions (Messari Format)](/api-reference/endpoints/ai/post-v1-chat-completions) The OpenAI-compatible endpoint returns data in the standard OpenAI response format, making it compatible with popular SDKs like the OpenAI Python package. This endpoint supports both streaming and synchronous response modes, allowing you to plug directly into packages expecting OpenAI format. The Vercel DSP-compatible endpoint implements the [Vercel Data Stream Protocol](https://sdk.vercel.ai/docs/ai-sdk-ui/stream-protocol#data-stream-protocol), enabling direct integration with Vercel's AI SDK library through the useChat function; it only supports streaming responses. The Messari Format endpoint serves as the standard option but uses Messari's proprietary format. For most implementations, the OpenAI-compatible endpoint is recommended for its broader compatibility and flexibility. ## Chat Completions Quickstart Get started quickly with our SDK example for AI Copilot Chat. This guide walks you through instantiating the client, making chat completion requests, and handling responses. ## Authorization Refer to our [Authentication](/api-reference/authentication) docs for creating an API key. ### Pay-Per-Request with x402 No API key? You can also access the MessariAI API using [x402 micropayments](/api-reference/x402-payments) — pay per request with USDC on Base Mainnet, no account required. ### Copilot Rate Limits | **User Tier** | **Requests** | | - | - | | Unpaid | 10 per day | | Enterprise | 600 per minute | ### AI Credits If more Copilot requests are needed, [get in touch](https://blockworks.com/contact) about enrolling in our consumption based credit system. If you run out of credits, your requests will fallback to our default rate limits defined in the above table. After exhausting the credits and daily rate limit, the API will respond with a `429` error with the message of `"rate limit exceeded. Resets in "` # Deep Research API Source: https://docs.messari.io/api-reference/endpoints/ai/deep-research-api Generate comprehensive, long-form research reports on any crypto topic using Messari's knowledge graph. The Deep Research API enables you to generate in-depth research reports asynchronously. Each report is backed by Messari's knowledge graph and includes cited sources. ## How It Works Deep research jobs run asynchronously and typically take **5-10 minutes** to complete. The workflow is: 1. **Create a job** — Submit a research query via [POST /ai/v1/deep-research](/api-reference/endpoints/ai/post-v1-deep-research) 2. **Poll for status** — Check progress via [GET /ai/v1/deep-research/](/api-reference/endpoints/ai/get-v1-deep-research-id) until status is `completed` 3. **Retrieve the report** — The completed response includes the full markdown report and cited sources ### Job Statuses | Status | Description | | - | - | | `queued` | Job is waiting to be processed | | `in_progress` | Research generation is underway | | `completed` | Report is ready — check the `output` field | | `failed` | Job failed — check the `error` field | | `cancelled` | Job was cancelled via the cancel endpoint | ## Endpoints * [Create Deep Research Job](/api-reference/endpoints/ai/post-v1-deep-research) — Start a new research report * [List Deep Research Jobs](/api-reference/endpoints/ai/get-v1-deep-research) — View your research jobs with pagination and status filtering * [Get Deep Research Job](/api-reference/endpoints/ai/get-v1-deep-research-id) — Poll for status and retrieve completed reports * [Cancel Deep Research Job](/api-reference/endpoints/ai/post-v1-deep-research-id-cancel) — Cancel a queued or in-progress job ## Follow-up Research You can iteratively refine a report by passing the original `job_id` in a subsequent create request. This sends a follow-up message to the same research conversation, allowing you to ask clarifying questions or request additional analysis on the same topic. ## Authorization Refer to our [Authentication](/api-reference/authentication) docs for creating an API key. ### Credits Each deep research request consumes **500 credits**. Enterprise teams receive **10 free report generations per month** — these are shared across the Messari platform and API, and are consumed before credits are deducted. # List Deep Research Jobs Source: https://docs.messari.io/api-reference/endpoints/ai/get-v1-deep-research GET /ai/v1/deep-research Returns a paginated list of deep research jobs for the authenticated user. # Get Deep Research Job Source: https://docs.messari.io/api-reference/endpoints/ai/get-v1-deep-research-id GET /ai/v1/deep-research/{id} Returns the current status of a deep research job. When status is 'completed', the response includes the generated report and sources. # Trending Questions Source: https://docs.messari.io/api-reference/endpoints/ai/get-v1-questions-trending GET /ai/v1/questions/trending The Trending Questions endpoint fetches suggested Copilot questions based on the latest trending topics Trending questions are generated based on the latest trending topics each question corresponds to a topic the are ordered by the topic's trending score. The topics are part of the [Topics API](/api-reference/endpoints/topics/get-v1-current) # Chat Completion - OpenAI Format Source: https://docs.messari.io/api-reference/endpoints/ai/post-openai-chat-completions POST /ai/openai/chat/completions The MessariAI API's Chat Completion endpoint is used for generating contextual crypto responses using Messari's knowledge graph and specialized tools. It follows OpenAI's chat completions API specification for easy integration with libraries like [OpenAI's official python SDK](https://github.com/openai/openai-python). If you'd like to play around with the responses feel free to try on the [Messari web-app](https://messari.io/copilot), it uses the same underlying endpoint implementation. The chat completion endpoint leverages a graph architecture with agents to: * Access Messari's real-time quantitative (compute) dataset which includes but is not limited to: Market data, Asset metrics, Fundraising, Token unlocks * Access Messari's qualitative (search) dataset which includes but is not limited to: News, Blogs, Youtube transcriptions, RSS-feeds, Twitter, Webcrawl documents, Proprietary datasets of: Research, Quarterlies, Diligence Reports * Generate market insights and analysis * Process natural language queries about crypto assets, protocols and projects For a more interactive experience trying out the API, [here is our Replit in Typescript](https://replit.com/@malcolm22/MessariAI-API-Examples#index.ts). Simply populate the `API_KEY` field with your Enterprise API key generated in the [Messari Account > API page](https://messari.io/account/api) of our webapp and you're off! ### Request Params #### verbosity The `verbosity` parameter controls the level of detail in the model's response. When set to `"verbose"`, the model provides more comprehensive and detailed explanations, including additional context, examples, and supporting information. Other possible values might include `"balanced"` or `"succinct"` for shorter responses. Example usage: ```json theme={null} { "verbosity": "verbose" } ``` #### response\_format The `response_format` parameter specifies the desired formatting style for the model's response. When set to `"markdown"`, the output will be formatted using Markdown syntax, allowing for structured text with headings, lists, code blocks, and other formatting elements. Other common option might include `"text"`. **Example usage:** ```json theme={null} { "response_format": "markdown" } ``` #### inline\_citations The `inline_citations` parameter determines whether the response metadata should include citations within its response text. When set to `true`, the model will reference sources directly in the text where information is being drawn from. This is particularly useful for academic, research, or factual content where attribution is important. **Example usage:** ```json theme={null} { "inline_citations": true } ``` #### stream The `stream` parameter controls whether the API response is delivered as a complete response or as a stream of partial responses. When set to `false`, the API will wait until the entire response is generated and then deliver it in one piece. When set to `true`, the API would begin sending partial responses as they are generated, useful for implementing real-time typing effects or processing responses incrementally. **Example usage:** ```json theme={null} { "stream": false } ``` #### generate\_related\_questions The `generate_related_questions` parameter determines whether the response metadata should include AI-generated related questions to the user query. This feature is useful for receiving follow up questions as part of the API response payload to prompt the user with potential next questions. Note: A maximum of 5 is allowed. **Example usage:** ```json theme={null} { "generate_related_questions": 2 } ``` # Run the Compute agent Source: https://docs.messari.io/api-reference/endpoints/ai/post-v1-agent-compute POST /ai/v1/agent/compute Runs Messari's Compute agent standalone over Messari's quantitative datasets. Returns each executed SQL query in `results`, with `query_result` rows, the `columns` naming each row position, and `truncated` reporting that the row cap was reached. `error` carries the agent's explanation when a run produces no usable result. There is no synthesized answer: this endpoint computes, and the caller writes the answer. The SQL and column names reflect Messari's internal schema, which may change without notice: read them, do not parse them. Requires an authenticated Enterprise user holding the `ai_toolkit_permission` API permission. Limited to 30 requests per minute per user. # Run the Search agent Source: https://docs.messari.io/api-reference/endpoints/ai/post-v1-agent-search POST /ai/v1/agent/search Runs Messari's Search agent standalone over Messari research and news. Returns the retrieved documents in `sources`. There is no synthesized answer and no citation numbering: this endpoint retrieves, and the caller writes the answer. Requires an authenticated Enterprise user holding the `ai_toolkit_permission` API permission. Limited to 30 requests per minute per user. # Chat Completion - Messari Format Source: https://docs.messari.io/api-reference/endpoints/ai/post-v1-chat-completions POST /ai/v1/chat/completions The MessariAI API's Chat Completion endpoint is used for generating contextual crypto responses using Messari's knowledge graph and specialized tools. If you'd like to play around with the responses feel free to try on the [Messari web-app](https://messari.io/copilot), it uses the same underlying endpoint implementation. The chat completion endpoint leverages a graph architecture with agents to: * Access Messari's real-time quantitative (compute) dataset which includes but is not limited to: Market data, Asset metrics, Fundraising, Token unlocks * Access Messari's qualitative (search) dataset which includes but is not limited to: News, Blogs, Youtube transcriptions, RSS-feeds, Twitter, Webcrawl documents, Proprietary datasets of: Research, Quarterlies, Diligence Reports * Generate market insights and analysis * Process natural language queries about crypto assets, protocols and projects For a more interactive experience trying out the API, [here is our Replit in Typescript](https://replit.com/@malcolm22/MessariAI-API-Examples#index.ts). Simply populate the `API_KEY` field with your Enterprise API key generated in the [Messari Account > API page](https://messari.io/account/api) of our webapp and you're off! ### Request Params #### verbosity The `verbosity` parameter controls the level of detail in the model's response. When set to `"verbose"`, the model provides more comprehensive and detailed explanations, including additional context, examples, and supporting information. Other possible values might include `"balanced"` or `"succinct"` for shorter responses. Example usage: ```json theme={null} { "verbosity": "verbose" } ``` #### response\_format The `response_format` parameter specifies the desired formatting style for the model's response. When set to `"markdown"`, the output will be formatted using Markdown syntax, allowing for structured text with headings, lists, code blocks, and other formatting elements. Other common option might include `"text"`. **Example usage:** ```json theme={null} { "response_format": "markdown" } ``` #### inline\_citations The `inline_citations` parameter determines whether the response metadata should include citations within its response text. When set to `true`, the model will reference sources directly in the text where information is being drawn from. This is particularly useful for academic, research, or factual content where attribution is important. **Example usage:** ```json theme={null} { "inline_citations": true } ``` #### stream The `stream` parameter controls whether the API response is delivered as a complete response or as a stream of partial responses. When set to `false`, the API will wait until the entire response is generated and then deliver it in one piece. When set to `true`, the API would begin sending partial responses as they are generated, useful for implementing real-time typing effects or processing responses incrementally. **Example usage:** ```json theme={null} { "stream": false } ``` #### generate\_related\_questions The `generate_related_questions` parameter determines whether the response metadata should include AI-generated related questions to the user query. This feature is useful for receiving follow up questions as part of the API response payload to prompt the user with potential next questions. Note: A maximum of 5 is allowed. **Example usage:** ```json theme={null} { "generate_related_questions": 2 } ``` # Create Deep Research Job Source: https://docs.messari.io/api-reference/endpoints/ai/post-v1-deep-research POST /ai/v1/deep-research Start a new deep research report generation. The job runs asynchronously and typically takes 5-10 minutes to complete. # Cancel Deep Research Job Source: https://docs.messari.io/api-reference/endpoints/ai/post-v1-deep-research-id-cancel POST /ai/v1/deep-research/{id}/cancel Cancel a running deep research job. Only jobs with status 'queued' or 'in_progress' can be cancelled. # Chat Completion - Messari v2 Source: https://docs.messari.io/api-reference/endpoints/ai/post-v2-chat-completions POST /ai/v2/chat/completions Messari v2 chat completion endpoint for contextual crypto responses. **x402 Support:** Supported. See the [x402 guide](/api-reference/x402-payments#supported-endpoints). This endpoint provides Messari's v2 chat completion interface for contextual crypto analysis. For implementation details and authentication options, see: * [Chat Completions API Overview](/api-reference/endpoints/ai/chat-completions-api) * [Pay-Per-Request with x402](/api-reference/x402-payments) # Bulk API Source: https://docs.messari.io/api-reference/endpoints/bulk/bulk-api The Bulk API provides high-performance access to download large historical datasets in CSV or JSONL format. Designed for data scientists, analysts, and researchers who need to download comprehensive timeseries data at scale. ## Overview The Bulk API is optimized for downloading large amounts of historical data efficiently. Unlike standard API endpoints that return paginated JSON responses, the Bulk API streams data directly to files in formats optimized for data analysis and processing. ## Available Endpoints The Bulk API consists of two main endpoints: * [**Get Available Datasets**](/api-reference/endpoints/bulk/get-v1-datasets) - Returns a catalog of all bulk datasets available based on your subscription tier, including available columns and supported granularities. * [**Download Dataset**](/api-reference/endpoints/bulk/get-v1-datasets-datasetSlug-granularity-data) - Downloads bulk timeseries data for a specific dataset at a given granularity in CSV or JSONL format. ## Key Features ### Multiple Output Formats * **CSV**: Comma-separated values, ideal for Excel, pandas, and other data analysis tools * **JSONL**: JSON Lines format, perfect for streaming data processing and loading into databases ### Flexible Granularities Download data at different time intervals based on your needs: * **1d**: Daily intervals * **1w**: Weekly intervals ### Large Time Ranges Download months or years of historical data in a single request, with appropriate limits to prevent excessive downloads. ## Use Cases The Bulk API is ideal for: * **Data Science & Machine Learning**: Download training datasets for ML models and backtesting algorithms * **Historical Analysis**: Analyze long-term trends and patterns across multiple assets * **Data Warehousing**: Populate your data warehouse with comprehensive crypto market data * **Research**: Academic research requiring large historical datasets * **Backtesting**: Test trading strategies against extensive historical data ## Getting Started 1. **Get your API key**: Visit [messari.io/account/api](https://messari.io/account/api) to obtain your API key 2. **Check available datasets**: Call the `/bulk/v1/datasets` endpoint to see which datasets you have access to 3. **Download data**: Use the dataset download endpoint with your desired parameters ## Rate Limits & Best Practices * The Bulk API has concurrency limits to ensure system stability * Downloads are limited by time range based on granularity to prevent excessive data transfer * For very large datasets, consider breaking requests into smaller time ranges * Downloaded files are gzip-compressed when supported by your client to reduce transfer time ## Authentication All Bulk API requests require authentication via the `x-messari-api-key` header. Access to specific datasets depends on your subscription tier (FREE, PROFESSIONAL, or ENTERPRISE). # Get Available Datasets Source: https://docs.messari.io/api-reference/endpoints/bulk/get-v1-datasets GET /bulk/v1/datasets Lists all bulk datasets available to the authenticated user based on their subscription tier. Each dataset includes its name, slug, description, required tier, available columns, and supported granularities. ## Overview This endpoint returns a catalog of all bulk datasets available to you based on your subscription tier. Each dataset includes metadata about available columns, supported granularities, and the minimum tier required for access. ## Response Structure The response includes an array of datasets, where each dataset contains: * **name**: Human-readable name of the dataset * **slug**: URL-safe identifier used in download requests * **description**: Detailed explanation of the dataset contents * **tier**: Minimum subscription tier required (FREE, PROFESSIONAL, or ENTERPRISE) * **columns**: Array of available columns with their names, slugs, descriptions, and data types * **granularities**: Supported time intervals for this dataset (e.g., 1h, 1d) ## Usage Example Use this endpoint to discover what data is available to you before making download requests: ```bash theme={null} curl -X GET "https://api.messari.io/bulk/v1/datasets" \ -H "x-messari-api-key: YOUR_API_KEY" ``` ## Subscription Tier Access Different datasets require different subscription tiers: * **FREE**: Access to basic datasets * **PROFESSIONAL**: Additional datasets with more metrics * **ENTERPRISE**: Full access to all bulk datasets including premium metrics ## Next Steps After identifying the dataset you want to download, use the [Download Dataset endpoint](/api-reference/endpoints/bulk/get-v1-datasets-datasetSlug-granularity-data) with the appropriate `datasetSlug` and `granularity` values. # Download Dataset Source: https://docs.messari.io/api-reference/endpoints/bulk/get-v1-datasets-datasetSlug-granularity-data GET /bulk/v1/datasets/{datasetSlug}/{granularity}/data Downloads bulk timeseries data for a specific dataset at a given granularity. Data can be exported in CSV or JSONL format. The response includes all metric columns configured for bulk output. Time range is limited to prevent excessive data downloads. ## Overview Downloads bulk timeseries data for a specific dataset at the specified granularity. The data is streamed directly as a file in either CSV or JSONL format, making it ideal for large-scale data downloads. ## Path Parameters * **datasetSlug** (required): The slug identifier of the dataset to download. Use the [Get Available Datasets](/api-reference/endpoints/bulk/get-v1-datasets) endpoint to discover available dataset slugs. * **granularity** (required): The time interval for the data points. Available options: `1d`, `1w` ## Query Parameters * **rangeStart** (required): Start of the time range in ISO 8601 format (e.g., `2024-01-01T00:00:00Z`) * **rangeEnd** (required): End of the time range in ISO 8601 format (e.g., `2024-12-31T23:59:59Z`) * **format** (optional): Output format - either `csv` (default) or `jsonl` ## Output Formats ### CSV Format Comma-separated values with a header row. Compatible with Excel, Google Sheets, pandas, and most data analysis tools. ```csv theme={null} asset_id,timestamp,price_usd,market_cap_usd,volume_24h btc,2024-01-01T00:00:00Z,42500.50,834215000000,18234567890 eth,2024-01-01T00:00:00Z,2250.75,270500000000,8945123456 ``` ### JSONL Format JSON Lines format with one JSON object per line. Ideal for streaming processing and database imports. ```jsonl theme={null} {"asset_id":"btc","timestamp":"2024-01-01T00:00:00Z","price_usd":42500.50,"market_cap_usd":834215000000,"volume_24h":18234567890} {"asset_id":"eth","timestamp":"2024-01-01T00:00:00Z","price_usd":2250.75,"market_cap_usd":270500000000,"volume_24h":8945123456} ``` ## Time Range Limits To prevent excessive data downloads, time ranges are limited based on granularity: * **1d**: Maximum 365 days per request * **1w**: Maximum 1095 days (3 years) per request For larger time ranges, make multiple requests with different date ranges. ## Usage Examples ### Download CSV Data ```bash theme={null} curl -X GET "https://api.messari.io/bulk/v1/datasets/asset_price/1d/data?rangeStart=2024-01-01T00:00:00Z&rangeEnd=2024-12-31T23:59:59Z&format=csv" \ -H "x-messari-api-key: YOUR_API_KEY" \ -o asset_price_data.csv ``` ### Download JSONL Data ```bash theme={null} curl -X GET "https://api.messari.io/bulk/v1/datasets/asset_price/1h/data?rangeStart=2024-01-01T00:00:00Z&rangeEnd=2024-01-31T23:59:59Z&format=jsonl" \ -H "x-messari-api-key: YOUR_API_KEY" \ -o asset_price_data.jsonl ``` ### Python Example with pandas ```python theme={null} import pandas as pd import requests url = "https://api.messari.io/bulk/v1/datasets/asset_price/1d/data" params = { "rangeStart": "2024-01-01T00:00:00Z", "rangeEnd": "2024-12-31T23:59:59Z", "format": "csv" } headers = {"x-messari-api-key": "YOUR_API_KEY"} response = requests.get(url, params=params, headers=headers) df = pd.read_csv(pd.io.common.BytesIO(response.content)) print(df.head()) ``` ## Response Headers The response includes helpful headers: * **Content-Type**: `text/csv; charset=utf-8` or `application/x-ndjson` * **Content-Disposition**: Suggests a filename for the download (e.g., `asset_price_1d_2024-01-01_2024-12-31.csv`) * **Content-Encoding**: `gzip` if compression is applied ## Error Responses ### 400 Bad Request * Invalid date format * End date before start date * Time range exceeds maximum allowed for the granularity * Invalid format parameter ### 403 Forbidden * Your subscription tier does not have access to this dataset ### 404 Not Found * Dataset slug does not exist * Granularity not supported for this dataset ## Best Practices 1. **Start with the datasets catalog**: Always check available datasets first to see supported granularities 2. **Respect time range limits**: Break large downloads into smaller time windows 3. **Use appropriate granularity**: Choose the coarsest granularity that meets your needs to reduce data transfer 4. **Handle errors gracefully**: Implement retry logic for transient network errors 5. **Store data efficiently**: Consider using columnar formats like Parquet for long-term storage after download # Exchanges API Source: https://docs.messari.io/api-reference/endpoints/exchanges/exchanges-api Track crypto exchange volumes including spot volume, futures volume and futures open interest # Available Endpoints * [**List Exchanges**](/api-reference/endpoints/exchanges/list-exchanges): Returns a list of all exchanges. * [**Get Exchange**](/api-reference/endpoints/exchanges/get-exchange): Returns a specified exchange. * [**List Exchange Metrics**](/api-reference/endpoints/exchanges/list-exchanges-metrics): Returns all metrics avaialble for exchanges. * [**Exchange Timeseries Metric**](/api-reference/endpoints/exchanges/get-exchange-timeseries-metric): Returns the timeseries for metrics of an exchange. # Available Endpoints The Exchange API allows developers to: * Track spot volume across different crypto exchanges * Measure futures volume and open interest * Determine changes in volume over time # Get Exchange Source: https://docs.messari.io/api-reference/endpoints/exchanges/get-exchange GET /metrics/v1/exchanges/{exchangeIdentifier} Retrieve a specific exchange **x402 Support:** Supported. See the [x402 guide](/api-reference/x402-payments#supported-endpoints). # Exchange Time Series Metric Source: https://docs.messari.io/api-reference/endpoints/exchanges/get-exchange-timeseries-metric GET /metrics/v1/exchanges/{entityIdentifier}/metrics/{datasetSlug}/time-series/{granularity} Retrieve a specific exchange's timeseries data **x402 Support:** Supported. See the [x402 guide](/api-reference/x402-payments#supported-endpoints). # List Exchanges Source: https://docs.messari.io/api-reference/endpoints/exchanges/list-exchanges GET /metrics/v1/exchanges Retrieve a list of exchanges **x402 Support:** Supported. See the [x402 guide](/api-reference/x402-payments#supported-endpoints). # List Exchanges Metrics Source: https://docs.messari.io/api-reference/endpoints/exchanges/list-exchanges-metrics GET /metrics/v1/exchanges/metrics Get metric catalog of datasets for exchanges. **x402 Support:** Supported. See the [x402 guide](/api-reference/x402-payments#supported-endpoints). # Organizations Source: https://docs.messari.io/api-reference/endpoints/funding/entities/get-v1-organizations GET /funding/v1/organizations Lookup Organizations given a set of filters. **x402 Support:** Supported. See the [x402 guide](/api-reference/x402-payments#supported-endpoints). # Projects Source: https://docs.messari.io/api-reference/endpoints/funding/entities/get-v1-projects GET /funding/v1/projects Lookup Projects given a set of filters. **x402 Support:** Supported. See the [x402 guide](/api-reference/x402-payments#supported-endpoints). # Fundraising API Source: https://docs.messari.io/api-reference/endpoints/funding/funding-api Access comprehensive data on fundraising rounds, mergers and acquisitions, and funding entities in the crypto and blockchain ecosystem to track capital flows and investment trends. ## Available Endpoints The Fundraising API is organized into four main categories: ### Fundraising Rounds * [**Get Rounds**](/api-reference/endpoints/funding/fundraising-rounds/get-v1-rounds) - Returns details about fundraising rounds, including amount raised, investors, and project information. * [**Get Investors**](/api-reference/endpoints/funding/fundraising-rounds/get-v1-rounds-investors) - Returns information about investors participating in fundraising rounds. ### Mergers and Acquisitions * [**Get M\&A**](/api-reference/endpoints/funding/mergers-acquisitions/get-v1-mergers-and-acquisitions) - Returns data on mergers and acquisitions in the crypto industry, including deal values and participants. ### Entities * [**Get Organizations**](/api-reference/endpoints/funding/entities/get-v1-organizations) - Returns information about organizations in the ecosystem, including investment firms and corporate entities. * [**Get Projects**](/api-reference/endpoints/funding/entities/get-v1-projects) - Returns data on crypto projects that have received funding. ### Funds * [**Get Funds**](/api-reference/endpoints/funding/funds/get-v1-funds) - Returns information about investment funds operating in the crypto space. * [**Get Fund Managers**](/api-reference/endpoints/funding/funds/get-v1-funds-managers) - Returns details about managers of crypto investment funds. ## Use Cases The Funding API enables developers to: * Track investment trends across the crypto and blockchain industry * Monitor capital inflows to specific sectors or technologies * Create dashboards showing the most active investors and their portfolios * Analyze funding stages and valuations for comparable projects * Track merger and acquisition activity in the blockchain space * Identify emerging funding trends and hot investment sectors * Build competitive analysis tools comparing funding across similar projects # Rounds Source: https://docs.messari.io/api-reference/endpoints/funding/fundraising-rounds/get-v1-rounds GET /funding/v1/rounds Lookup Funding Rounds given a set of filters. **x402 Support:** Supported. See the [x402 guide](/api-reference/x402-payments#supported-endpoints). # Rounds Investors Source: https://docs.messari.io/api-reference/endpoints/funding/fundraising-rounds/get-v1-rounds-investors GET /funding/v1/rounds/investors Lookup Investors that participated in a set of Funding Rounds given a set of filters. Filters are applied to the Funding Rounds, and then their Investors are returned. **x402 Support:** Supported. See the [x402 guide](/api-reference/x402-payments#supported-endpoints). # Funds Source: https://docs.messari.io/api-reference/endpoints/funding/funds/get-v1-funds GET /funding/v1/funds Lookup Funds given a set of filters. **x402 Support:** Supported. See the [x402 guide](/api-reference/x402-payments#supported-endpoints). # Funds Managers Source: https://docs.messari.io/api-reference/endpoints/funding/funds/get-v1-funds-managers GET /funding/v1/funds/managers Lookup the Managers of a set of Funds defined by the filters. Filters are applied to the Funds, and then their Managers are returned. **x402 Support:** Supported. See the [x402 guide](/api-reference/x402-payments#supported-endpoints). # Mergers and Acquisitions Source: https://docs.messari.io/api-reference/endpoints/funding/mergers-acquisitions/get-v1-mergers-and-acquisitions GET /funding/v1/mergers-and-acquisitions Lookup M&A Deals given a set of filters. **x402 Support:** Supported. See the [x402 guide](/api-reference/x402-payments#supported-endpoints). # List all assets Source: https://docs.messari.io/api-reference/endpoints/intel/get-v1-assets GET /intel/v1/assets Retrieve a list of all assets # List Events (deprecated GET form) Source: https://docs.messari.io/api-reference/endpoints/intel/get-v1-events GET /intel/v1/events [DEPRECATED] Use POST /events instead. Retrieve a list of all events based on query parameters # Event and History by ID Source: https://docs.messari.io/api-reference/endpoints/intel/get-v1-events-eventId GET /intel/v1/events/{eventId} Retrieve an event and its history using the event ID # Intel API Source: https://docs.messari.io/api-reference/endpoints/intel/intel-api Access Messari's database of crypto events and developments, providing structured information about key happenings across the ecosystem. ## Available Endpoints The Intel API consists of four main endpoints: * [**Get Assets**](/api-reference/endpoints/intel/get-v1-assets) - Returns a list of assets that have associated events in the Intel database. * [**Get Events**](/api-reference/endpoints/intel/get-v1-events) - Returns a paginated list of events from the Intel database, with filtering options. * [**Get Event Details**](/api-reference/endpoints/intel/get-v1-events-eventId) - Returns comprehensive details about a specific event identified by its unique ID. ## Use Cases The Intel API enables developers to: * Track significant events across the crypto ecosystem in a structured format * Build custom event monitoring dashboards or notification systems * Integrate crypto events timeline into asset research platforms * Create historical analyses of how specific event types impact markets * Filter events by type, asset, or date range for targeted monitoring * Correlate market movements with specific ecosystem developments # List all events via POST Source: https://docs.messari.io/api-reference/endpoints/intel/post-v1-events POST /intel/v1/events Retrieve a list of all events based on body parameters # Asset & Market Data API Source: https://docs.messari.io/api-reference/endpoints/metrics/metrics-api Messari's Asset & Market Data API provides comprehensive data on crypto assets and networks, enabling developers to access market data, on-chain metrics, and analytical insights. The Assets API consists of 6 endpoints: * [**List Assets**](/api-reference/endpoints/metrics/v2/assets/get-v2-assets) - Returns all available assets and their coverage within Messari. Supports filtering by sector, category, tag * [**Get Asset Details**](/api-reference/endpoints/metrics/v2/assets/get-v2-assets-details) - Queries and returns the detailed information for 1 or more assets. Details include market data, qualitative info, supply, ath, roi and more. * [**Get Return on Investments (ROIs)**](/api-reference/endpoints/metrics/v2/assets/get-v2-assets-roi) - Returns the ROI data for 1 or more assets. Supports filtering by sector, category, tag * [**Get All Time Highs (ATHs)**](/api-reference/endpoints/metrics/v2/assets/get-v2-assets-ath) - Returns the ATH data for 1 or more assets. Supports filtering by sector, category, tag * [**List Metrics**](/api-reference/endpoints/metrics/v2/assets/get-v2-assets-metrics) - Returns a list of the available timeseries metrics for assets along with the supported granularity * [**Get Asset Timeseries Metric**](/api-reference/endpoints/metrics/v2/assets/get-asset-timeseries) - Returns the data points for the chosen timeseries metrics. Typically used for data export or graphical visualizations ## Demo: Trading Terminal See the power of Messari's Metrics API in action with our interactive Trading Terminal demo. This comprehensive visualization tool showcases how the data from our Metrics endpoints can be combined to create powerful market analytics dashboards. Explore real-time market data visualizations powered by Messari's Metrics API ### Featured Charts The Trading Terminal demonstrates how developers can leverage Messari's Metrics API to build sophisticated market analysis tools, including: * **Multi-Factor Overview** - Combined visualization of price, sentiment, and mindshare data * **Market Cap Analysis** - Track circulating market capitalization over time * **Mindshare Overview** - Monitor social attention metrics for assets * **Momentum Breakdown** - Analyze price, trend, and acceleration components of momentum * **Sentiment Analysis** - Hourly breakdown of positive, neutral, and negative sentiment * **Futures Volume & Open Interest** - Track derivatives market activity and capital commitment * **Price & Volume** - Analyze price movements in relation to trading volume * **Hourly Sentiment & Volume** - Monitor social sentiment alongside discussion intensity By integrating these data points, developers can create comprehensive market intelligence tools that combine price data, trading activity, derivatives metrics, and social signals. # Get asset timeseries data Source: https://docs.messari.io/api-reference/endpoints/metrics/v1/get-asset-timeseries GET /metrics/v1/assets/{entityIdentifier}/metrics/{datasetSlug}/time-series Retrieve a specific asset's timeseries data # Get Market Timeseries Source: https://docs.messari.io/api-reference/endpoints/metrics/v1/get-market-timeseries-with-granularity GET /metrics/v1/markets/{entityIdentifier}/metrics/{datasetSlug}/time-series/{granularity} Retrieve a specific market's timeseries data with specified granularity. Price data is denominated in USD. Volume data is denominated in USD. **x402 Support:** Supported. See the [x402 guide](/api-reference/x402-payments#supported-endpoints). # Get network timeseries data Source: https://docs.messari.io/api-reference/endpoints/metrics/v1/get-time-series-timeseries-with-granularity GET /metrics/v1/networks/{entityIdentifier}/metrics/{datasetSlug}/time-series/{granularity} Retrieve a specific network's timeseries data # Get assets Source: https://docs.messari.io/api-reference/endpoints/metrics/v1/get-v1-assets GET /metrics/v1/assets Retrieve a list of assets # Get asset Source: https://docs.messari.io/api-reference/endpoints/metrics/v1/get-v1-assets-assetIdentifier GET /metrics/v1/assets/{assetIdentifier} Retrieve a specific asset # Get timeseries metrics catalog Source: https://docs.messari.io/api-reference/endpoints/metrics/v1/get-v1-assets-metrics GET /metrics/v1/assets/metrics Get metric catalog of datasets for assets. # Get Markets Source: https://docs.messari.io/api-reference/endpoints/metrics/v1/get-v1-markets GET /metrics/v1/markets Retrieve a list of markets **x402 Support:** Supported. See the [x402 guide](/api-reference/x402-payments#supported-endpoints). # Get Market Source: https://docs.messari.io/api-reference/endpoints/metrics/v1/get-v1-markets-marketIdentifier GET /metrics/v1/markets/{marketIdentifier} Retrieve a specific market **x402 Support:** Supported. See the [x402 guide](/api-reference/x402-payments#supported-endpoints). # Get Market Timeseries Metrics Source: https://docs.messari.io/api-reference/endpoints/metrics/v1/get-v1-markets-metrics GET /metrics/v1/markets/metrics Get the catalog of available timeseries datasets and granularities for markets. Use this to discover valid `datasetSlug` and `granularity` values for the market timeseries endpoints. **x402 Support:** Supported. See the [x402 guide](/api-reference/x402-payments#supported-endpoints). # Markets API Source: https://docs.messari.io/api-reference/endpoints/metrics/v1/markets-api The Markets API provides price and volume data for trading pairs across cryptocurrency exchanges. ## Available Endpoints The Markets API consists of following endpoints: * [**Get Markets**](/api-reference/endpoints/metrics/v1/get-v1-markets) - Returns a list of all markets. * [**Get Market Metrics**](/api-reference/endpoints/metrics/v1/get-v1-markets-metrics) - Returns a list of metrics support for markets. * [**Get Market**](/api-reference/endpoints/metrics/v1/get-v1-markets-marketIdentifier) - Returns a specific market. * [**Get Market Timeseries**](/api-reference/endpoints/metrics/v1/get-market-timeseries) - Returns the timeseries for a specific market and metric. # Asset Timeseries Source: https://docs.messari.io/api-reference/endpoints/metrics/v2/assets/get-asset-timeseries GET /metrics/v2/assets/{assetID}/metrics/{datasetSlug}/time-series/{granularity} Retrieve a specific asset's timeseries data **x402 Support:** Supported. See the [x402 guide](/api-reference/x402-payments#supported-endpoints). ## Granularity Parameter The `granularity` path parameter controls the time interval for each data point: | Granularity | Description | Max Datapoints | | - | - | - | | `5m` | 5-minute data points | 1,440 | | `1h` | Hourly data points | 5,000 | | `1d` | Daily data points (default) | 5,000 | | `1w` | Weekly data points | 5,000 | Not all datasets support all granularities. See the table below for supported granularities by dataset. ### Dataset Granularity Support | Dataset | `5m` | `1h` (Hourly) | `1d` (Daily) | `1w` (Weekly) | | - | - | - | - | - | | `price` | ✅ | ✅ | ✅ | ✅ | | `futures-funding-rate` | ❌ | ✅ | ✅ | ❌ | | `futures-open-interest` | ❌ | ✅ | ✅ | ❌ | | `futures-volume` | ❌ | ✅ | ✅ | ❌ | | `marketcap` | ❌ | ✅ | ✅ | ✅ | | `supply` | ❌ | ❌ | ✅ | ✅ | | `volatility` | ❌ | ❌ | ✅ | ✅ | | `sharpe-ratio` | ❌ | ❌ | ✅ | ✅ | | `stablecoin-network-breakdown` | ❌ | ❌ | ✅ | ✅ | | `stablecoin-supply` | ❌ | ❌ | ✅ | ✅ | | `stablecoin-transfers` | ❌ | ❌ | ✅ | ✅ | # List Assets Source: https://docs.messari.io/api-reference/endpoints/metrics/v2/assets/get-v2-assets GET /metrics/v2/assets Returns ALL assets that match the filter criteria along with their coverage. **x402 Support:** Supported. See the [x402 guide](/api-reference/x402-payments#supported-endpoints). # Get All-Time Highs Source: https://docs.messari.io/api-reference/endpoints/metrics/v2/assets/get-v2-assets-ath GET /metrics/v2/assets/ath Retrieve a specific asset's ATH **x402 Support:** Supported. See the [x402 guide](/api-reference/x402-payments#supported-endpoints). # Get Asset Details Source: https://docs.messari.io/api-reference/endpoints/metrics/v2/assets/get-v2-assets-details GET /metrics/v2/assets/details Returns detailed information for up to 20 assets specified by their ids or slugs. **x402 Support:** Supported. See the [x402 guide](/api-reference/x402-payments#supported-endpoints). # List Metrics Source: https://docs.messari.io/api-reference/endpoints/metrics/v2/assets/get-v2-assets-metrics GET /metrics/v2/assets/metrics Returns a list of the available market data and derivatives timeseries metrics for assets along with the supported granularity. **x402 Support:** Supported. See the [x402 guide](/api-reference/x402-payments#supported-endpoints). # Get ROIs Source: https://docs.messari.io/api-reference/endpoints/metrics/v2/assets/get-v2-assets-roi GET /metrics/v2/assets/roi Retrieve a specific asset's ROI **x402 Support:** Supported. See the [x402 guide](/api-reference/x402-payments#supported-endpoints). # Get All Networks Time Series Source: https://docs.messari.io/api-reference/endpoints/metrics/v2/networks/all-networks-timeseries GET /metrics/v2/networks/metrics/{datasetSlug}/time-series/{granularity} Returns one timeseries per network, for every network the networks listing serves, in a single response. Use this instead of calling the per-network endpoint once for each network. Every network is included, so narrow start and end to limit the response size. Returns one series per network in a single response, rather than one request per network. ## Supported datasets | Dataset | Description | | - | - | | `activity` | Addresses, transactions and other onchain activity | | `financial` | Fees, revenue and other financial metrics | | `ecosystem` | Ecosystem-level metrics | | `stablecoin` | Stablecoin supply and transfers | | `staking` | Staking supply, rate and rewards | | `perp-dex` | Perpetual DEX metrics | Any other value returns `400`, naming the datasets that are accepted. # Network Time Series with Granularity Source: https://docs.messari.io/api-reference/endpoints/metrics/v2/networks/get-time-series-timeseries-with-granularity GET /metrics/v2/networks/{entityIdentifier}/metrics/{datasetSlug}/time-series/{granularity} Retrieve a specific network's timeseries data **x402 Support:** Supported (conditions apply). **Conditions:** x402 is available only when `granularity` is one of `5m`, `15m`, `1h`, `1d`. See the [x402 guide](/api-reference/x402-payments#supported-endpoints). ## Granularity Parameter The `granularity` path parameter controls the time interval for each data point. | Granularity | Description | | - | - | | `5m` | 5-minute data points | | `15m` | 15-minute data points | | `1h` | Hourly data points | | `1d` | Daily data points | | `1w` | Weekly data points | # Networks Source: https://docs.messari.io/api-reference/endpoints/metrics/v2/networks/get-v2-networks GET /metrics/v2/networks Retrieve a list of networks **x402 Support:** Supported. See the [x402 guide](/api-reference/x402-payments#supported-endpoints). # Network Metrics Source: https://docs.messari.io/api-reference/endpoints/metrics/v2/networks/get-v2-networks-metrics GET /metrics/v2/networks/metrics Get metric catalog of datasets for networks. **x402 Support:** Supported. See the [x402 guide](/api-reference/x402-payments#supported-endpoints). # Networks API Source: https://docs.messari.io/api-reference/endpoints/metrics/v2/networks/networks The Networks API provides on-chain metrics and analytics for blockchain networks, enabling developers to track network activity, performance, and growth. It consists of 4 endpoints: * [**List Networks**](/api-reference/endpoints/metrics/v2/networks/get-v2-networks) - Returns all available networks tracked by Messari * [**List Network Metrics**](/api-reference/endpoints/metrics/v2/networks/get-v2-networks-metrics) - Returns a list of the available timeseries metrics for networks along with the supported granularity * [**Get Network Timeseries**](/api-reference/endpoints/metrics/v2/networks/get-network-timeseries) - Returns timeseries data for specific network metrics * [**Get Timeseries with Granularity**](/api-reference/endpoints/metrics/v2/networks/get-time-series-timeseries-with-granularity) - Returns network timeseries data with specified time granularity ## Datasets The timeseries endpoints take a `datasetSlug` path parameter. Five datasets are available: | Dataset | Contents | | :- | :- | | `activity` | Transactions, addresses, contracts, and throughput | | `ecosystem` | TVL, DEX volume, and developer activity | | `financial` | Fees, revenue, and supply | | `stablecoin` | Stablecoin supply and flows on the network | | `staking` | Stake, staking yield, validators, and delegators | Call [List Network Metrics](/api-reference/endpoints/metrics/v2/networks/get-v2-networks-metrics) for the full metric list of each dataset, along with the granularities it supports. ## Staking metrics The `staking` dataset carries the 22 metrics below, at `1d` and `1w` granularity. Coverage varies by network. Networks that do not use proof of stake, such as Bitcoin and the rollups, return no staking data at all. A proof-of-stake network reports only some of the fields below, and the set differs by network. A field a network does not report returns `null`, so check for `null` rather than assuming a value is present. ### Stake | Field | Definition | | :- | :- | | `totalStakedNative` | Total native tokens staked on the network. | | `totalStakedUsd` | USD value of total stake on the network. | | `stakingRatePct` | Percentage of native circulating supply staked. | | `nativeStakedNative` | Native tokens staked directly, excluding liquid staking. | | `nativeStakedUsd` | USD value of tokens staked directly, excluding liquid staking. | | `liquidStakedNative` | Native tokens staked through liquid staking protocols. | | `liquidStakedUsd` | USD value of tokens staked through liquid staking protocols. | | `liquidStakingRatePct` | Percentage of native circulating supply in liquid staking. | | `netStakeFlowNative` | Net stake flow in native tokens over the period. A negative value means net unstaking. | | `netStakeFlowUsd` | Net stake flow in USD over the period. A negative value means net unstaking. | `nativeStakedNative` and `liquidStakedNative` split `totalStakedNative`. ### Rewards and yield | Field | Definition | | :- | :- | | `stakingRewardsNative` | Staking rewards paid in native tokens over the period. | | `stakingRewardsUsd` | Staking rewards paid in USD over the period. | | `stakingApr30dPct` | 30 day trailing staking APR. | | `stakingApy30dPct` | 30 day trailing staking APY. | | `realStakingApy30dPct` | 30 day trailing staking APY, net of native token inflation. | | `stakingInflationRate30dPct` | 30 day trailing annualized native token inflation rate. | ### Validators and stakers | Field | Definition | | :- | :- | | `validatorCount` | Number of validators on the network. | | `activeValidatorCount` | Number of active validators on the network. | | `delegatorCount` | Number of delegators on the network. | | `stakerCount` | Number of unique staking participants on the network. | | `avgValidatorCommissionRate` | Average validator commission rate. | | `stakeWeightedCommissionRate` | Stake-weighted validator commission rate. | A field that ends in `Pct` is a **percentage on a 0 to 100 scale**, not a fraction. `stakingRatePct` returns `68.68` for a network with 68.68% of supply staked. The two commission rates carry no `Pct` suffix, because they are **fractions between 0 and 1**. A field that ends in `Native` is denominated in the network's own token. A field that ends in `Usd` is the USD value of the same measure. Staking fields take no `24Hour` infix, unlike most of the `activity` and `financial` metrics. Most of them are point-in-time measures rather than rolling 24 hour aggregates. `netStakeFlow*` and `stakingRewards*` are the exceptions: they cover the period of the data point, so they cover one day at `1d` granularity and one week at `1w`. ## Throughput on the activity dataset The `activity` dataset carries one further metric: | Field | Definition | | :- | :- | | `transactionsPerSecond` | Average transactions per second processed by the network. | # List Categories Source: https://docs.messari.io/api-reference/endpoints/monitoring/get-v2-categories GET /monitoring/v2/categories Full intel taxonomy — top-level categories with their nested subcategories. Static data, no filters or pagination. # List Developments Source: https://docs.messari.io/api-reference/endpoints/monitoring/get-v2-developments GET /monitoring/v2/developments Paginated list of developments with rich filtering. Asset tokens (`assetIds`) may be UUIDs or slugs; unresolved tokens are silently dropped and if none of the supplied tokens resolve, the response is an empty page. Other multi-value filters (`intelCategories`, `intelSubcategories`, `assetSectors`, `assetSubsectors`, `assetEcosystemNetworkIds`) accept comma-separated tokens and apply the same silent-drop semantic — typos return an empty result rather than an error. Use `eventIds` if you need a token to be validated; it returns 400 with the offending token quoted. Results are ordered most recent first. Every development includes a nested `event` reference linking to its parent event. # Get Development Source: https://docs.messari.io/api-reference/endpoints/monitoring/get-v2-developments-developmentId GET /monitoring/v2/developments/{developmentId} Single development detail. Returns 404 if the development is not found. # List Events Source: https://docs.messari.io/api-reference/endpoints/monitoring/get-v2-events GET /monitoring/v2/events Paginated list of events. Events are logical groupings of related developments; the filter surface matches `/v2/developments` since downstream the service joins on the matching developments. Filter semantics also match: silent-drop on unresolved `assetIds` and unknown taxonomy slugs in `intelCategories` / `intelSubcategories`, 400 from `eventIds` on unresolvable tokens. Results are ordered most recent first. # Get Event Source: https://docs.messari.io/api-reference/endpoints/monitoring/get-v2-events-eventId GET /monitoring/v2/events/{eventId} Single event detail plus its nested developments. Returns 404 if the event is not found. # List Monitoring Views Source: https://docs.messari.io/api-reference/endpoints/monitoring/get-v2-monitoring-views GET /monitoring/v2/monitoring-views Paginated list of monitoring views the caller can read. Visibility includes views the caller owns plus views team-shared with any of the caller's teams, resolved from the `x-client-info` identity header. # All matched developments Source: https://docs.messari.io/api-reference/endpoints/monitoring/get-v2-monitoring-views-all-developments GET /monitoring/v2/monitoring-views/all/developments Deduplicated union of developments matching any view the caller can see (personal + team-shared). Response items use the canonical Development shape. # All matched events Source: https://docs.messari.io/api-reference/endpoints/monitoring/get-v2-monitoring-views-all-events GET /monitoring/v2/monitoring-views/all/events Deduplicated union of events matching any view the caller can see (personal + team-shared). # Get Monitoring View Source: https://docs.messari.io/api-reference/endpoints/monitoring/get-v2-monitoring-views-monitoringViewId GET /monitoring/v2/monitoring-views/{monitoringViewId} View definition plus aggregate stats. Accepts either a full UUID or the slug-with-id-prefix form (e.g. `my-defi-view-a1b2c3d4`). Returns 404 if the view is not found or the caller cannot access it. # Developments matched by a view Source: https://docs.messari.io/api-reference/endpoints/monitoring/get-v2-monitoring-views-monitoringViewId-developments GET /monitoring/v2/monitoring-views/{monitoringViewId}/developments Paginated developments matching the saved view's predicates. Optional free-text `search` further narrows the result set. Response items use the canonical Development shape. # Events matched by a view Source: https://docs.messari.io/api-reference/endpoints/monitoring/get-v2-monitoring-views-monitoringViewId-events GET /monitoring/v2/monitoring-views/{monitoringViewId}/events Paginated events matching the saved view's predicates. Optional free-text `search` further narrows the result set. # Monitoring API Source: https://docs.messari.io/api-reference/endpoints/monitoring/monitoring-api Agentic monitoring for crypto's most demanding teams. Programmatic access to AI-surfaced, analyst-verified events across 1,000+ assets and 700+ sources. Messari Monitoring replaces keyword alerts and manual checks with AI agents that continuously read, evaluate, and escalate the events that matter. Every event is reviewed by Messari's Intel Analyst team before it reaches your pipeline, so you get speed and accuracy, not a firehose. The Monitoring API is the programmatic interface to that system, and the next-generation replacement for the legacy [Intel API](/api-reference/endpoints/intel/intel-api). ## What you get * **Agentic coverage, not keyword rules.** Agents understand context, severity, and relevance. They distinguish a \$50M unlock from a blog post that mentions one. * **1,000+ assets, including long-tail.** Bitcoin through small-cap DeFi. Standardized coverage so you catch sector spillovers, not just the majors. * **700+ sources ingested continuously.** On-chain data, governance, filings, news, and social, all monitored in real time. * **Analyst-verified.** AI flags developing signals instantly; analysts verify before anything is marked `verified: true`. Minutes, not hours. * **Structured output.** Events, developments, categorized taxonomy, and resolved assets, ready to feed dashboards, risk systems, PagerDuty, or custom workflows. ## Core concepts * **Development.** The atomic unit of coverage. A single dated, verified occurrence (e.g. "Binance.US lists TRX"). Tagged with category, subcategory, importance, resolved assets (each marked `primary` or `secondary`), and a nested `event` reference pointing at the parent event. Every endpoint that returns developments uses the same shape. * **Event.** A logical grouping of related developments over time (e.g. a multi-stage hack and its subsequent disclosures, responses, and post-mortems). Carries its own `slug`, `createdAt` / `updatedAt`, and aggregate `developmentCount` / `documentCount`. * **Monitoring View.** A saved filter over the stream. `simple` views are deterministic predicates (assets, categories, importance). `agentic` views are prompt-based; the prompt is stored on the view itself and matched items come back in the canonical Development shape. ## Summaries Developments and events both expose a `summary` field, but they behave differently: * **Development summaries.** For verified developments (`verified: true`), the summary is human-curated by Messari's Intel Analyst team and reflects the most up-to-date information at the time of verification. Treat it as authoritative. * **Event summaries.** Rolled up across the event's child developments, so they update as new developments land. Expect some latency between a fresh development being added and the event-level summary catching up — if you need the latest narrative, read the most recent development under the event rather than the event summary. ## Versions * **`/monitoring/v2/*` (current).** The canonical surface, aligned with what powers messari.io's Intel product. Use this for new integrations. * **Migrating from `/intel/v1/*`?** The legacy v1 surface is still served at the [Intel API](/api-reference/endpoints/intel/intel-api) — same paths, parameters, and response shapes. Continue calling `/intel/v1/*` until you can adopt v2. ## Use cases * **Risk & response.** Feed verified `security_and_hacks` developments for your portfolio assets straight into PagerDuty or an on-call rota. * **Portfolio intelligence.** Save a monitoring view scoped to the assets you hold (including long-tail) and pull `minimumImportance=medium` developments on a cron. * **Research automation.** Pull agentic views that surface developments matching a natural-language thesis (e.g. "stablecoin peg stress" or "L2 sequencer outages"). * **Client-facing alerting.** Power customer-facing event timelines and notifications in your own product without running your own monitoring stack. * **Governance & ops dashboards.** Filter for `governance=true` developments across assets your DAO or treasury cares about. ## Access Monitoring is available to Messari API customers. Already a customer? Monitoring is available as an add-on to your existing plan. [Contact sales](https://messari.io/contact-sales) to enable it. # Get News Assets Source: https://docs.messari.io/api-reference/endpoints/news/get-v1-news-assets GET /news/v1/news/assets Get the assets that Messari News covers. Use the returned slug or id to filter the news feed by asset. Returns the assets that Messari News covers, paginated. Use the returned `slug` or `id` to filter the [news feed](/api-reference/endpoints/news/get-v1-news-feed) by asset. # News Feed Source: https://docs.messari.io/api-reference/endpoints/news/get-v1-news-feed GET /news/v1/news/feed Gets the news feed for the user **x402 Support:** Supported. See the [x402 guide](/api-reference/x402-payments#supported-endpoints). # Get News Sources Source: https://docs.messari.io/api-reference/endpoints/news/get-v1-news-sources GET /news/v1/news/sources Get News Sources **x402 Support:** Supported. See the [x402 guide](/api-reference/x402-payments#supported-endpoints). # News API Source: https://docs.messari.io/api-reference/endpoints/news/news-api Messari's News API provides developers with access to a curated feed of crypto news from trusted sources. Stay informed about the latest developments in the crypto space with real-time news updates filtered by asset or source. ## Available Endpoints The News API consists of two main endpoints: * [**Get News Feed**](/api-reference/endpoints/news/get-v1-news-feed) - Returns a paginated feed of crypto news articles from all available sources. Supports filtering by date range. * [**Get News Sources**](/api-reference/endpoints/news/get-v1-news-sources) - Returns a list of all available news sources integrated with Messari's news system. ## Use Cases The News API enables developers to: * Build news aggregators focused on the crypto industry * Create asset-specific news feeds for portfolio tracking applications * Monitor market-moving announcements and developments * Integrate real-time crypto news into trading or analytics platforms * Filter content by trusted sources to reduce noise and focus on quality information # List All Protocols Source: https://docs.messari.io/api-reference/endpoints/protocols/core/list-protocols GET /metrics/v2/protocols Returns a complete list of all available protocols supported by Messari, along with core metrics. Protocols aggregate deployments across multiple blockchain networks (e.g., Aave includes V3, V2, and V1 versions). # List Protocols Core Metrics Source: https://docs.messari.io/api-reference/endpoints/protocols/core/list-protocols-metrics GET /metrics/v2/protocols/metrics Returns a list of timeseries core metrics available for all protocols # Get Protocol Core Timeseries Metric Source: https://docs.messari.io/api-reference/endpoints/protocols/core/protocol-timeseries-metric GET /metrics/v2/protocols/{protocolIdentifier}/metrics/core/time-series/{granularity} Returns a timeseries metric for a specific protocol. Protocols represent an aggregation of all deployments across all chains (e.g., Aave will include V3, V2, and V1). # Get All DAT Holdings Time Series Source: https://docs.messari.io/api-reference/endpoints/protocols/dats/all-dat-holdings-timeseries GET /metrics/v2/protocols/dats/holdings/time-series/{granularity} Returns every company's crypto holdings history in a single response: every digital asset treasury company, every asset it holds, over the window. Use this instead of calling the per-company holdings endpoint once for each company. Every metric and the full history are returned by default; narrow start and end to limit the response size. # Get All DATs Time Series Source: https://docs.messari.io/api-reference/endpoints/protocols/dats/all-dats-timeseries GET /metrics/v2/protocols/dats/time-series/{granularity} Returns one treasury time series per digital asset treasury company, for every company the DAT listing serves, in a single response. Use this instead of calling the per-company treasury endpoint once for each company. Every metric and the full history are returned by default; narrow start and end to limit the response size. A company with no data in the window is still present, with an empty points array. # Get DAT Holdings Time Series Source: https://docs.messari.io/api-reference/endpoints/protocols/dats/dat-holdings-timeseries-metric GET /metrics/v2/protocols/dats/{datIdentifier}/metrics/holdings/time-series/{granularity} Returns one company's crypto holdings history, one time series per asset it holds, tracking units held, USD value and daily purchases. A company holding three assets returns three series. Each series carries its own assetSymbol, so you do not have to parse the composite series id. Only the 1d granularity is available for this dataset. # Get DAT Treasury Time Series Source: https://docs.messari.io/api-reference/endpoints/protocols/dats/dat-treasury-timeseries-metric GET /metrics/v2/protocols/dats/{datIdentifier}/metrics/treasury/time-series/{granularity} Returns one company's capital structure history: share counts, market cap, enterprise value, cash, debt, NAV and the four mNAV variants. The identifier is the company's stock ticker (MSTR) or its Messari project slug. Only the 1d granularity is available for this dataset. # List DAT Metrics Source: https://docs.messari.io/api-reference/endpoints/protocols/dats/list-dat-metrics GET /metrics/v2/protocols/dats/metrics Returns the metric catalog for both digital asset treasury datasets in one response: treasury, at the company grain, and holdings, one series per company and held asset. Use the metric slugs here to read the point arrays the DAT time series endpoints return. # List DATs Source: https://docs.messari.io/api-reference/endpoints/protocols/dats/list-dats GET /metrics/v2/protocols/dats Returns one row per digital asset treasury (DAT) company, each with the assets it holds and its latest treasury values. A DAT is a public company holding crypto on its balance sheet, and its id is its stock ticker (for example MSTR). The holdings summary lists which assets the company holds, so you can see the by-asset coverage before calling the holdings endpoints. Latest values are read from the most recent point in the last 30 days; a company that reported nothing in that window returns nulls and a null asOfTime. # Get All DEX Time Series Source: https://docs.messari.io/api-reference/endpoints/protocols/dex/all-dex-timeseries GET /metrics/v2/protocols/dex/time-series/{granularity} Returns one timeseries per DEX protocol, for every protocol the DEX listing serves, in a single response. Use this instead of calling the per-protocol DEX endpoint once for each protocol. Protocols are an aggregation of all deployments across all chains (e.g. Uniswap includes V3, V2 and V1). Every protocol is included, so narrow start and end to limit the response size. # Get DEX Timeseries Metric Source: https://docs.messari.io/api-reference/endpoints/protocols/dex/dex-timeseries-metric GET /metrics/v2/protocols/{protocolIdentifier}/metrics/dex/time-series/{granularity} Returns a timeseries metric for a specific DEX. Protocols will be an aggregation of all deployments across all chains (e.g., Uniswap will include V3, V2, and V1). # List DEX Metrics Source: https://docs.messari.io/api-reference/endpoints/protocols/dex/list-dex-metrics GET /metrics/v2/protocols/dex/metrics Returns a list of timeseries metrics available for DEXs # List DEX Protocols Source: https://docs.messari.io/api-reference/endpoints/protocols/dex/list-dex-protocols GET /metrics/v2/protocols/dex Returns a complete list of all available DEX protocols supported by Messari, along with metrics. Protocol data represents an aggregation across all chain deployments (e.g., Uniswap includes V3, V2, and V1 versions). # Get All ETF Assets Time Series Source: https://docs.messari.io/api-reference/endpoints/protocols/etfs/all-etf-assets-timeseries GET /metrics/v2/protocols/etfs/assets/time-series/{granularity} Returns one time series per underlying crypto asset, for every asset the asset listing serves, in a single response. Every asset metric and the full history are returned by default; narrow start and end to limit the response size. An asset with no data in the window is still present, with an empty points array. # Get All ETF Providers Time Series Source: https://docs.messari.io/api-reference/endpoints/protocols/etfs/all-etf-providers-timeseries GET /metrics/v2/protocols/etfs/time-series/{granularity} Returns one time series per ETF issuer, for every issuer the provider listing serves, in a single response. Use this instead of calling the per-issuer endpoint once for each issuer. Every provider metric and the full history are returned by default; narrow start and end to limit the response size. An issuer with no data in the window is still present, with an empty points array. # Get ETF Asset Time Series Source: https://docs.messari.io/api-reference/endpoints/protocols/etfs/etf-asset-timeseries GET /metrics/v2/protocols/etfs/assets/{assetIdentifier}/metrics/overview/time-series/{granularity} Returns one underlying crypto asset's ETF history: AUM, net flow and product count split by product type (spot and futures), by region (US, Europe and APAC) and by strategy (delta-one and leveraged), plus traded volume by region. Only the 1d granularity is available for this dataset. # Get ETF Provider Time Series Source: https://docs.messari.io/api-reference/endpoints/protocols/etfs/etf-provider-timeseries GET /metrics/v2/protocols/etfs/{providerIdentifier}/metrics/overview/time-series/{granularity} Returns one issuer's history: AUM, daily and rolling 30-day net flow, product count, AUM-weighted expense ratio, and the bitcoin and spot shares of AUM. The identifier is the issuer's Blockworks Research provider slug (blackrock) or its Messari project slug (bitwise-asset-management). Only the 1d granularity is available for this dataset. # List ETF Assets Source: https://docs.messari.io/api-reference/endpoints/protocols/etfs/list-etf-assets GET /metrics/v2/protocols/etfs/assets Returns one row per underlying crypto asset held through ETFs, with the asset's latest values split by product type, by region and by strategy. This is a sibling of the provider listing, not a child of it: an issuer and an underlying asset are two independent cuts of the same data. Latest values are read from the most recent point in the last 30 days; an asset that reported nothing in that window returns nulls and a null asOf. Sourced from Blockworks Research. # List ETF Metrics Source: https://docs.messari.io/api-reference/endpoints/protocols/etfs/list-etf-metrics GET /metrics/v2/protocols/etfs/metrics Returns the metric catalog for both ETF datasets in one response: the provider grain, one series per issuer, and the asset grain, one series per underlying crypto asset. Both publish a dataset slugged overview, so each entry carries a grain telling them apart. Use the metric slugs here to read the point arrays the ETF time series endpoints return. # List ETF Providers Source: https://docs.messari.io/api-reference/endpoints/protocols/etfs/list-etf-providers GET /metrics/v2/protocols/etfs Returns one row per crypto ETF issuer, with the issuer's latest values. An ETF provider is an asset manager running crypto exchange-traded products, and its id is its Blockworks Research provider slug (for example blackrock). Latest values are read from the most recent point in the last 30 days; an issuer that reported nothing in that window returns nulls and a null asOf. Sourced from Blockworks Research. # Get Interoperability Timeseries Metric Source: https://docs.messari.io/api-reference/endpoints/protocols/interoperability/interop-timeseries-metric GET /metrics/v2/protocols/{protocolIdentifier}/metrics/interop/time-series/{granularity} Returns a timeseries metric for a specific interoperability protocol. Protocol data represents an aggregation of all deployments across all chains. # List Interoperability Metrics Source: https://docs.messari.io/api-reference/endpoints/protocols/interoperability/list-interop-metrics GET /metrics/v2/protocols/interop/metrics Returns a list of timeseries metrics available for interoperability protocols # List Interoperability Protocols Source: https://docs.messari.io/api-reference/endpoints/protocols/interoperability/list-interop-protocols GET /metrics/v2/protocols/interop Returns a complete list of all available interoperability (bridging) protocols supported by Messari, along with metrics. Protocol data represents an aggregation across all chain deployments. # Get All Lending Time Series Source: https://docs.messari.io/api-reference/endpoints/protocols/lending/all-lending-timeseries GET /metrics/v2/protocols/lending/time-series/{granularity} Returns one timeseries per lending protocol, for every protocol the lending listing serves, in a single response. Use this instead of calling the per-protocol lending endpoint once for each protocol. The response aggregates data across all deployments and versions of protocols (e.g., AAVE includes V3, V2, and V1). This is the protocol grain only; for a series per instance or per market, use the lending-instances and lending-markets endpoints. Every protocol is included, so narrow start and end to limit the response size. # Get Lending Instances Timeseries Source: https://docs.messari.io/api-reference/endpoints/protocols/lending/lending-instances-timeseries-metric GET /metrics/v2/protocols/{protocolIdentifier}/metrics/lending-instances/time-series/{granularity} Returns one timeseries per instance of a lending protocol, where an instance is a product on a chain (for example aave-v3 on ethereum). Each series carries its own productSlug and chain, so you do not have to parse the composite series id. A protocol that Blockworks Research does not map returns 200 with an empty series list; an unknown identifier returns 404. The response caps at 100 series, above which a 400 names the filters that narrow it. # Get Lending Markets Timeseries Source: https://docs.messari.io/api-reference/endpoints/protocols/lending/lending-markets-timeseries-metric GET /metrics/v2/protocols/{protocolIdentifier}/metrics/lending-markets/time-series/{granularity} Returns one timeseries per market of a lending protocol, where a market is an individual pool (for example a USDC pool of aave-v3 on ethereum). Each series carries its own marketName, productSlug and chain. A protocol that Blockworks Research does not map returns 200 with an empty series list; an unknown identifier returns 404. The response caps at 250 series, above which a 400 names the product and chain filters that narrow it. # Get Lending Timeseries Metric Source: https://docs.messari.io/api-reference/endpoints/protocols/lending/lending-timeseries-metric GET /metrics/v2/protocols/{protocolIdentifier}/metrics/lending/time-series/{granularity} Returns a timeseries metric for a specific Lending Protocol. Protocol data represents an aggregation of all deployments across all chains. # List Lending Instance Metrics Source: https://docs.messari.io/api-reference/endpoints/protocols/lending/list-lending-instance-metrics GET /metrics/v2/protocols/lending-instances/metrics Returns the timeseries metrics available for the lending-instances dataset. The dataset carries the same ten Blockworks Research lending metrics as the protocol-grain lending dataset, at product x chain grain. # List Lending Market Metrics Source: https://docs.messari.io/api-reference/endpoints/protocols/lending/list-lending-market-metrics GET /metrics/v2/protocols/lending-markets/metrics Returns the timeseries metrics available for the lending-markets dataset. The market grain deliberately carries fewer metrics than the protocol and instance grains. # List Lending Markets Source: https://docs.messari.io/api-reference/endpoints/protocols/lending/list-lending-markets GET /metrics/v2/protocols/lending-markets Returns a paginated list of Blockworks Research lending markets, one row per individual pool, filterable by protocol, product and chain. The protocol object is the parent protocol, so its slug passes straight back as the protocol filter; the specific product (aave-v3 rather than aave) is the sibling productSlug field, which the product filter matches. Each marketId is a composite of parent slug, product slug, chain and market key, keyed on the pool address rather than the market name so that it survives an upstream rename. # List Lending Metrics Source: https://docs.messari.io/api-reference/endpoints/protocols/lending/list-lending-metrics GET /metrics/v2/protocols/lending/metrics Returns a list of timeseries metrics available for lending protocols # List Lending Protocols Source: https://docs.messari.io/api-reference/endpoints/protocols/lending/list-lending-protocols GET /metrics/v2/protocols/lending Returns a complete list of all available Lending protocols supported by Messari, along with metrics. The response aggregates data across all deployments and versions of protocols (e.g., AAVE includes V3, V2, and V1). # Get Liquid Staking Timeseries Metric Source: https://docs.messari.io/api-reference/endpoints/protocols/liquid-staking/liquid-staking-timeseries-metric GET /metrics/v2/protocols/{protocolIdentifier}/metrics/liquid-staking/time-series/{granularity} Returns a timeseries metric for a specific liquid staking protocol. Protocol data represents an aggregation of all deployments across all chains. # List Liquid Staking Metrics Source: https://docs.messari.io/api-reference/endpoints/protocols/liquid-staking/list-liquid-staking-metrics GET /metrics/v2/protocols/liquid-staking/metrics Returns a list of timeseries metrics available for liquid staking protocols # List Liquid Staking Protocols Source: https://docs.messari.io/api-reference/endpoints/protocols/liquid-staking/list-liquid-staking-protocols GET /metrics/v2/protocols/liquid-staking Returns a complete list of all available liquid staking protocols supported by Messari, along with metrics. Protocol data represents an aggregation across all chain deployments. # Protocols API Source: https://docs.messari.io/api-reference/endpoints/protocols/protocols-api The Protocols API provides access to comprehensive data on DeFi protocols, including DEXs and lending platforms. Access aggregated metrics across all protocol deployments and versions on multiple blockchain networks. ## Available Endpoints The Protocols API is organized into the categories below: ### Core Protocols * [**List All Protocols**](/api-reference/endpoints/protocols/core/list-protocols) - Returns a complete list of all available protocols supported by Messari, along with core metrics. * [**List Protocols Core Metrics**](/api-reference/endpoints/protocols/core/list-protocols-metrics) - Returns a list of timeseries core metrics available for all protocols. * [**Get Protocol Core Timeseries**](/api-reference/endpoints/protocols/core/protocol-timeseries-metric) - Returns timeseries data for a specific protocol's core metrics. ### DEX Protocols * [**List DEX Protocols**](/api-reference/endpoints/protocols/dex/list-dex-protocols) - Returns all available DEX protocols supported by Messari. * [**List DEX Metrics**](/api-reference/endpoints/protocols/dex/list-dex-metrics) - Returns a list of timeseries metrics available for DEXs. * [**Get DEX Timeseries**](/api-reference/endpoints/protocols/dex/dex-timeseries-metric) - Returns timeseries data for a specific DEX protocol. * [**Get All DEX Time Series**](/api-reference/endpoints/protocols/dex/all-dex-timeseries) - Returns one timeseries per DEX protocol, for every DEX protocol, in a single response. ### Lending Protocols * [**List Lending Protocols**](/api-reference/endpoints/protocols/lending/list-lending-protocols) - Returns all available lending protocols supported by Messari. * [**List Lending Metrics**](/api-reference/endpoints/protocols/lending/list-lending-metrics) - Returns a list of timeseries metrics available for lending protocols. * [**Get Lending Timeseries**](/api-reference/endpoints/protocols/lending/lending-timeseries-metric) - Returns timeseries data for a specific lending protocol. * [**Get All Lending Time Series**](/api-reference/endpoints/protocols/lending/all-lending-timeseries) - Returns one timeseries per lending protocol, for every lending protocol, in a single response. * [**List Lending Instance Metrics**](/api-reference/endpoints/protocols/lending/list-lending-instance-metrics) - Returns a list of timeseries metrics available at instance grain. * [**Get Lending Instances Timeseries**](/api-reference/endpoints/protocols/lending/lending-instances-timeseries-metric) - Returns one timeseries per instance of a lending protocol. * [**List Lending Markets**](/api-reference/endpoints/protocols/lending/list-lending-markets) - Returns a filterable list of individual lending markets. * [**List Lending Market Metrics**](/api-reference/endpoints/protocols/lending/list-lending-market-metrics) - Returns a list of timeseries metrics available at market grain. * [**Get Lending Markets Timeseries**](/api-reference/endpoints/protocols/lending/lending-markets-timeseries-metric) - Returns one timeseries per market of a lending protocol. ### DATs Digital asset treasury (DAT) companies are public companies holding crypto on their balance sheet. They are not DeFi protocols, so a DAT is keyed by its **stock ticker** (`MSTR`) rather than a protocol slug, and its data comes at two grains: the company's own capital structure, and its holdings broken out per asset. * [**List DATs**](/api-reference/endpoints/protocols/dats/list-dats) - Returns one row per digital asset treasury company, with the assets it holds and its latest treasury values. * [**List DAT Metrics**](/api-reference/endpoints/protocols/dats/list-dat-metrics) - Returns the metric catalog for both DAT datasets, treasury and holdings, in one response. * [**Get DAT Treasury Time Series**](/api-reference/endpoints/protocols/dats/dat-treasury-timeseries-metric) - Returns one company's capital structure history. * [**Get All DATs Time Series**](/api-reference/endpoints/protocols/dats/all-dats-timeseries) - Returns one treasury timeseries per company, for every company, in a single response. * [**Get DAT Holdings Time Series**](/api-reference/endpoints/protocols/dats/dat-holdings-timeseries-metric) - Returns one company's holdings history, one timeseries per asset it holds. * [**Get All DAT Holdings Time Series**](/api-reference/endpoints/protocols/dats/all-dat-holdings-timeseries) - Returns every company's holdings history, one timeseries per company and held asset, in a single response. ### ETFs Crypto exchange-traded funds are covered at two grains, and they are **independent cuts, not a parent and a child**: one series per **issuer** (`blackrock`), and one series per **underlying crypto asset** (`bitcoin`). They ship as two sibling collections, so neither nests inside the other. * [**List ETF Providers**](/api-reference/endpoints/protocols/etfs/list-etf-providers) - Returns one row per crypto ETF issuer, with the issuer's latest values. * [**List ETF Metrics**](/api-reference/endpoints/protocols/etfs/list-etf-metrics) - Returns the metric catalog for both ETF datasets, provider and asset, in one response. * [**Get ETF Provider Time Series**](/api-reference/endpoints/protocols/etfs/etf-provider-timeseries) - Returns one issuer's history. * [**Get All ETF Providers Time Series**](/api-reference/endpoints/protocols/etfs/all-etf-providers-timeseries) - Returns one timeseries per issuer, for every issuer, in a single response. * [**List ETF Assets**](/api-reference/endpoints/protocols/etfs/list-etf-assets) - Returns one row per underlying crypto asset held through ETFs, with the asset's latest values. * [**Get ETF Asset Time Series**](/api-reference/endpoints/protocols/etfs/etf-asset-timeseries) - Returns one underlying asset's ETF history. * [**Get All ETF Assets Time Series**](/api-reference/endpoints/protocols/etfs/all-etf-assets-timeseries) - Returns one timeseries per underlying asset, for every asset, in a single response. ### TCG Trading-card and collectibles platforms are covered **per platform and chain**. A platform is keyed by its **Blockworks Research slug** (`courtyard`), and a series is keyed by the platform and the chain together (`courtyard_polygon`), because a platform running on more than one chain reports separately on each. * [**List TCG Platforms**](/api-reference/endpoints/protocols/tcg/list-tcg-platforms) - Returns one row per trading-card platform, each with the chains it runs on. * [**List TCG Metrics**](/api-reference/endpoints/protocols/tcg/list-tcg-metrics) - Returns the metric catalog for the TCG overview dataset. * [**Get TCG Platform Time Series**](/api-reference/endpoints/protocols/tcg/tcg-platform-timeseries) - Returns one platform's history, one timeseries per chain it runs on. * [**Get All TCG Platforms Time Series**](/api-reference/endpoints/protocols/tcg/all-tcg-platforms-timeseries) - Returns one timeseries per platform and chain, across every platform, in a single response. ### Interoperability Protocols * [**List Interoperability Protocols**](/api-reference/endpoints/protocols/interoperability/list-interop-protocols) - Returns all available interoperability (bridging) protocols supported by Messari. * [**List Interoperability Metrics**](/api-reference/endpoints/protocols/interoperability/list-interop-metrics) - Returns a list of timeseries metrics available for interoperability protocols. * [**Get Interoperability Timeseries**](/api-reference/endpoints/protocols/interoperability/interop-timeseries-metric) - Returns timeseries data for a specific interoperability protocol. ### Liquid Staking Protocols * [**List Liquid Staking Protocols**](/api-reference/endpoints/protocols/liquid-staking/list-liquid-staking-protocols) - Returns all available liquid staking protocols supported by Messari. * [**List Liquid Staking Metrics**](/api-reference/endpoints/protocols/liquid-staking/list-liquid-staking-metrics) - Returns a list of timeseries metrics available for liquid staking protocols. * [**Get Liquid Staking Timeseries**](/api-reference/endpoints/protocols/liquid-staking/liquid-staking-timeseries-metric) - Returns timeseries data for a specific liquid staking protocol. ## Lending and DEX metrics Lending and DEX protocols carry the additional metrics below. Coverage varies by protocol: not every protocol reports every field, and one that does not returns `null`. Check for `null` rather than assuming a value is present. ### Lending Available on [List Lending Protocols](/api-reference/endpoints/protocols/lending/list-lending-protocols) and on [Get Lending Timeseries](/api-reference/endpoints/protocols/lending/lending-timeseries-metric) at `1d` and `1w` granularity. | Field | Definition | | :- | :- | | `depositsUsd` | Value deposited with the lending protocol, in USD. | | `borrowedUsd` | Total value of assets borrowed from the protocol, in USD. | | `interest24HourUsd` | Interest paid by borrowers, in USD. | | `netInterestIncome24HourUsd` | Interest earned less the interest paid out to depositors, in USD. | | `flashLoanFees24HourUsd` | Fees earned on flash loans, in USD. | | `liquidationFees24HourUsd` | Fees earned on liquidations, in USD. | | `royalties24HourUsd` | Royalties paid to the protocol, in USD. | | `revenueUsd` | Daily lending revenue in USD: net interest income plus flash loan, liquidation and royalty fees. Timeseries only. | `depositsUsd` is a **balance** and carries no `24Hour` qualifier, so it aggregates as an average over a longer granularity. The existing `netDeposits24HourUsd` is a daily **flow**, and the two are not interchangeable. Likewise `flashLoanFees24HourUsd` is a **fee**, while the existing `flashLoanVolume24HourUsd` on DEX protocols is a **volume**. `revenueUsd` is the Blockworks Research lending revenue. It is **not** `revenue24HourUsd`, which comes from a different source and is served by the core protocol and network endpoints. The two measure different things and report different values for the same protocol on the same day. Keep them apart. ### Lending grains Lending data is served at three grains. Each one is a separate dataset with its own metrics and its own route: | Dataset | Grain | Example | Metrics | | :- | :- | :- | :- | | `lending` | Protocol | Aave | 16 | | `lending-instances` | Product on a chain | aave-v3 on ethereum | 10 | | `lending-markets` | Individual pool | an aave-v3 pool on ethereum | 3 | The two finer grains return **many series in one response**, so their shape differs from both single-protocol routes and from [Get All Lending Time Series](/api-reference/endpoints/protocols/lending/all-lending-timeseries), which keys each series on a `protocol` object instead of on dimensions. Here each entry carries its own `id` and its own dimensions, and `metadata.pointSchemas` names the columns of every `points` row: ```json theme={null} { "data": { "series": [ { "id": "aave_aave-v3_arbitrum_0x794a61358d6845594f94dc1db02a252b5b4814ad", "marketName": "arbitrum-core", "productSlug": "aave-v3", "chain": "arbitrum", "points": [[1748736000, 1553455825.6, 794874331.0, 758581494.6]] } ] }, "metadata": { "pointSchemas": [ { "name": "Timestamp", "slug": "time", "is_timestamp": true }, { "name": "Deposits (USD)", "slug": "depositsUsd", "is_timestamp": false }, { "name": "Borrowed (USD)", "slug": "borrowedUsd", "is_timestamp": false }, { "name": "TVL (USD)", "slug": "tvl24HourUsd", "is_timestamp": false } ], "granularity": "1d", "seriesCount": 23 } } ``` `marketName` is present on the `lending-markets` dataset only. Both finer grains serve `1d` only. The protocol grain still serves `1d` and `1w`. Blockworks Research maps a fraction of lending protocols. A protocol it does not map returns `200` with an empty `series` list, not a `404`. A `404` means the identifier is not a Messari protocol at all. Note also that a product slug is not a protocol identifier: pass `aave`, not `aave-v3`. #### Finding instances and markets [List Lending Protocols](/api-reference/endpoints/protocols/lending/list-lending-protocols) carries an `instances` array on each protocol, so you can see which products and chains a protocol reports before you request a timeseries: ```json theme={null} "lending": { "depositsUsd": 29279393027.2, "instances": [ { "productSlug": "aave-v2", "chain": "ethereum" }, { "productSlug": "aave-v3", "chain": "ethereum" } ] } ``` The array is empty for a protocol that Blockworks Research does not map. Instances need no listing of their own, because the per-protocol route returns all of them. Markets do: their ids are pool addresses, and there are thousands. Use [List Lending Markets](/api-reference/endpoints/protocols/lending/list-lending-markets) to discover them, filtered by `protocol`, `product` or `chain`. The `protocol` object on each row is the **parent** protocol, so its `slug` passes straight back as the `protocol` filter. The specific product is the sibling `productSlug` field, which the `product` filter matches: ```json theme={null} { "marketId": "aave_aave-v3_arbitrum_0x794a61358d6845594f94dc1db02a252b5b4814ad", "marketName": "arbitrum-core", "productSlug": "aave-v3", "chain": "arbitrum", "protocol": { "id": "675b85dc-…", "name": "Aave", "slug": "aave" } } ``` `marketId` is a composite of parent slug, product slug, chain and market key. It is keyed on the pool address rather than the market name, so it survives an upstream rename. Some source rows carry no name; `marketName` is then the market key, and it can be an empty string. #### Response caps A single request returns at most 100 instance series or 250 market series. Above that the request returns `400` and names the filters that narrow it. Pass `product` and `chain` to the markets timeseries route to stay under the cap — a large protocol such as Euler or Morpho needs them. ### DEX Available on [List DEX Protocols](/api-reference/endpoints/protocols/dex/list-dex-protocols) and on [Get DEX Timeseries](/api-reference/endpoints/protocols/dex/dex-timeseries-metric) at `1d` and `1w` granularity. | Field | Definition | | :- | :- | | `correlatedVolume24HourUsd` | Volume traded between correlated assets, in USD. | | `aggregatorVolume24HourUsd` | Volume the exchange received through aggregators, in USD. | | `platformVolume24HourUsd` | Volume traded directly on the exchange's own front end, in USD. | | `aggregatorTradeCount24Hour` | Number of trades the exchange received through aggregators. | | `platformTradeCount24Hour` | Number of trades made directly on the exchange's own front end. | ### DEX volume splits Three more DEX fields are available on the listing endpoint only, not on the timeseries endpoints: | Field | Definition | | :- | :- | | `memecoinVolumeShare` | Share of 24 hour volume traded in memecoins, as a fraction between 0 and 1 — not a percentage. | | `volumeByCategory` | 24 hour volume split across asset categories, in USD. | | `volumeByPair` | 24 hour volume split across trading pairs, in USD. | `volumeByCategory` has the keys `nativeStablecoin`, `chainToken`, `foreignToken`, `stablecoinSwaps`, `lstSwaps`, `composites`, `tokenizedAssets`, `projectTokens` and `memes`. `volumeByPair` has the keys `bitcoinUsd`, `ethereumUsd`, `solanaUsd`, `avalancheUsd`, `bnbUsd`, `bitcoinEthereum`, `bitcoinSolana`, `ethereumSolana`, `fx` and `eurUsd`. Both objects are **omitted entirely** for a protocol that reports no split at all. Within an object that is present, a category or pair with no reported volume is `null`. An absent object and a `null` value therefore carry different meanings: the first means the protocol reports no split, the second means the protocol reports a split but not for that one category or pair. ## Digital asset treasury companies DAT data is served at two grains. Each is a separate dataset with its own metrics and its own route: | Dataset | Grain | Example series key | Metrics | | :- | :- | :- | :- | | `treasury` | Company | `MSTR` | 16 | | `holdings` | Company and held asset | `MSTR_btc` | 3 | Both serve `1d` only. Every route exists in a one-entity and an all-entities form, so a full sweep of either grain is a single request rather than one call per company. ### Identifiers A DAT's `id` is its **stock ticker**, not a protocol slug. The per-company routes accept either the ticker or the company's Messari project slug. Identifiers are **case-sensitive**. `MSTR` and `micro-strategy` both resolve; `mstr` returns `404`. A ticker is upper-case and a slug is lower-case, so pass each one as the API stores it. Not every company maps to a Messari project. Where none exists, `slug` is an empty string and `projectId` is absent — the company is still returned with full treasury data. ### Holdings and `assetSymbol` A holdings series is keyed on `companyTicker_assetSymbol`, and both halves are published beside the composite id so you never have to split it: ```json theme={null} { "id": "MSTR_btc", "name": "Strategy BTC", "companyTicker": "MSTR", "assetSymbol": "btc", "networkSlug": "bitcoin" } ``` `assetSymbol` is a lower-cased **ticker symbol** (`btc`, `eth`, `hype`), not a Messari asset slug such as `bitcoin`. It is lower-cased so that `companyTicker` + `_` + `assetSymbol` reconstructs the series `id` exactly. `networkSlug` is a genuine slug, but it is `null` for some assets, so it is not a substitute. The listing's `assetSymbol` filter narrows to companies holding a given asset, and matches either casing. Each row also carries a `holdings` summary naming every asset the company holds, so you can see the by-asset coverage before calling the holdings routes. ### Latest values on the listing The listing reports each company's most recent treasury point from the last 30 days. A company that reported nothing in that window returns `null` values and a `null` `asOfTime`, rather than a stale figure presented as current. Always read `asOfTime` to see which you got. ## Crypto ETFs ETF data is served at two grains. Unlike the DAT grains above, neither is a child of the other — they are two independent cuts of the same Blockworks Research data, so they are two sibling collections with a dataset each: | Collection | Grain | Example series key | Metrics | | :- | :- | :- | :- | | `/protocols/etfs` | Issuer | `blackrock` | 8 | | `/protocols/etfs/assets` | Underlying crypto asset | `bitcoin` | 25 | Both publish a single dataset slugged `overview` and serve `1d` only. Because both use the same dataset slug, the combined metrics endpoint carries a `grain` on each entry (`providers` or `assets`) to tell them apart. Every route exists in a one-entity and an all-entities form, so a full sweep of either grain is a single request rather than one call per issuer or asset. ETF issuers are asset managers, not DeFi protocols. Their placement under `/protocols` is pragmatic — it keeps them beside the other Blockworks Research collections — but an ETF provider is not a protocol and carries no protocol metrics. ### Identifiers An issuer's `id` is its **Blockworks Research provider slug** (`blackrock`), and an underlying asset's `id` is its **asset symbol** (`bitcoin`). Both per-entity routes also accept the Messari slug mapped onto the entity, so either resolves to the same series: ``` GET /metrics/v2/protocols/etfs/bitwise/metrics/overview/time-series/1d GET /metrics/v2/protocols/etfs/bitwise-asset-management/metrics/overview/time-series/1d ``` Not every entity maps to a Messari record. Where none exists, `slug` is an empty string and only the `id` resolves — the entity is still returned with full data. ### Reading a point A point is a timestamp followed by one value per metric, in the order `metadata.pointSchemas` declares. The metric slugs are the same kebab-case slugs the metrics catalog publishes, so a `pointSchemas` entry names the column beside it: ```json theme={null} { "metadata": { "granularity": "1d", "pointSchemas": [ { "slug": "time", "name": "Timestamp", "is_timestamp": true }, { "slug": "aum-usd", "name": "AUM (USD)" }, { "slug": "flow-usd", "name": "Flow (USD)" } ] } } ``` On the two all-entities endpoints `pointSchemas` sits **once** in `metadata`, not per entity: every series in the response reads the same dataset. ### Latest values on the listings Both listings report each entity's most recent point from the last 30 days. An entity that reported nothing in that window returns `null` values and a `null` `asOf`, rather than a stale figure presented as current. Always read `asOf` to see which you got. Sorting on a metric orders on that latest value. A row with no value for the sort metric always sorts **last**, in either direction — a missing AUM is not an AUM of zero, so it never leads an ascending sort. Every ETF metric is sourced from Blockworks Research. ## Trading card platforms Trading-card and collectibles (TCG) platforms sell and trade digital collectibles, often backed by graded physical cards. They are covered at a single grain — **one series per platform and chain** — and publish one dataset, slugged `overview`, at `1d` only. A platform that runs on more than one chain reports separately on each, so it has one series per chain rather than one series overall. Nothing is aggregated across a platform's chains, and you should not aggregate it yourself. `dauNew`, `dauRecurring`, `dauTotal` and `uniqueBuyers` are distinct counts of users, and a user active on two chains is counted on both — so summing them across chains overstates the total. `topSaleUsd` is a maximum, not a sum, so adding it across chains is meaningless too. ### Identifiers Two identifiers appear, and they are not interchangeable: | Field | Where | Example | What it is | | :- | :- | :- | :- | | `id` on a listing row | `/protocols/tcg` | `courtyard` | The platform. This is the `platformIdentifier` the platform time series route takes. | | `id` on a `chains` entry, and on a series | both | `courtyard_polygon` | The platform-chain pair. This is the series key. | The series key is a composite of the two, but **never split it yourself** — either half may itself contain an underscore. Every series carries `platform` and `chain` as their own fields for exactly this reason: ```json theme={null} { "id": "courtyard_polygon", "platform": "courtyard", "chain": "polygon", "points": [] } ``` That is also how the listing and the series join: a `chains[].id` from the listing matches the `id` of a series one-for-one. A platform slug the listing does not serve returns **404**, rather than an empty series list. ### The chains array Every listing row carries a `chains` array, whether the platform runs on one chain or several. Read it rather than assuming a single chain — the array is the shape in both cases, so no consumer needs to special-case the multi-chain platforms. Paging is over **platforms**, not over platform-chain pairs, so a multi-chain platform is never split across two pages. ### Messari mappings `projectSlug` on a platform and `networkSlug` on a chain are the Messari mappings. Both are `null` where no Messari record maps to the entity. They are `null`, never an empty string, so a missing mapping is never mistaken for a real but blank slug. ### Reading a point A point is a timestamp followed by one value per metric, in the order `metadata.pointSchemas` declares. `pointSchemas` sits **once** in `metadata`, not per series: every series in the response reads the same dataset. Both time series routes return the same multi-series shape. The per-platform route is only a narrowing of the all-platforms one, so a consumer can read either with the same code. Every TCG metric is sourced from Blockworks Research. ## Key Features * **Multi-Chain Aggregation**: Protocol data aggregates all deployments across multiple blockchain networks (e.g., Uniswap includes V3, V2, and V1) * **Comprehensive Metrics**: Access volume, TVL, fees, and other key protocol metrics * **Flexible Time Ranges**: Query data with various granularities from 1-minute to 1-year intervals * **Historical Data**: Access historical protocol performance data for analysis and tracking ## Use Cases The Protocols API enables developers to: * Build DeFi analytics dashboards tracking protocol performance * Compare metrics across different protocols and protocol types * Monitor DEX trading volumes and liquidity trends * Track lending protocol utilization and interest rates * Create alerts based on protocol metric thresholds * Analyze protocol growth and adoption over time # Get All TCG Platforms Time Series Source: https://docs.messari.io/api-reference/endpoints/protocols/tcg/all-tcg-platforms-timeseries GET /metrics/v2/protocols/tcg/time-series/{granularity} Returns one time series per platform and chain, across every TCG platform, in a single response. Nothing is aggregated across a platform's chains: the daily-active-user and unique-buyer counts overlap between chains, so a cross-chain total would overstate them. Every series carries its platform and chain alongside the composite id, so no consumer has to split the id. Only the 1d granularity is available. The response is small enough to serve the full history by default; narrow it with start and end. # List TCG Metrics Source: https://docs.messari.io/api-reference/endpoints/protocols/tcg/list-tcg-metrics GET /metrics/v2/protocols/tcg/metrics Returns the metric catalog for the TCG overview dataset: one entry per column of a point, in point order, with the timestamp first. The slugs here are the keys of a point row, and the order is the order of the values in every points array the TCG time series endpoints return. Sourced from Blockworks Research. # List TCG Platforms Source: https://docs.messari.io/api-reference/endpoints/protocols/tcg/list-tcg-platforms GET /metrics/v2/protocols/tcg Returns one row per Blockworks Research trading-card and collectibles platform, each with the chains it runs on. The id is the platform's Blockworks Research slug and can be passed straight back as the platformIdentifier of the platform time series route; each chain carries the series key of its platform-chain pair, which is the id the time series endpoints return. projectSlug and networkSlug are the Messari mappings and are null where the platform or chain maps to no Messari record. Paging is over platforms, so a multi-chain platform is never split across two pages. Sourced from Blockworks Research. # Get TCG Platform Time Series Source: https://docs.messari.io/api-reference/endpoints/protocols/tcg/tcg-platform-timeseries GET /metrics/v2/protocols/tcg/{platformIdentifier}/metrics/overview/time-series/{granularity} Returns one TCG platform's history, one series per chain it runs on. Nothing is aggregated across a platform's chains: the daily-active-user and unique-buyer counts overlap between chains, so a cross-chain total would overstate them. Every series carries its platform and chain alongside the composite id, so no consumer has to split the id. Only the 1d granularity is available. A platform slug the TCG listing does not serve returns 404. # Get basic research reports Source: https://docs.messari.io/api-reference/endpoints/research-basic/get-v1-basic-reports GET /research-basic/v1/basic/reports Returns a list of basic research reports based on filters like asset ID and tags # Get a basic research report by report ID Source: https://docs.messari.io/api-reference/endpoints/research-basic/get-v1-basic-reports-reportId GET /research-basic/v1/basic/reports/{reportId} Returns a basic research report by its report ID. # Get research reports Source: https://docs.messari.io/api-reference/endpoints/research/get-v1-reports GET /research/v1/reports Returns a list of research reports based on filters like asset ID and tags # Get a research report by report ID Source: https://docs.messari.io/api-reference/endpoints/research/get-v1-reports-reportId GET /research/v1/reports/{reportId} Returns a research report by its report ID # Get list of tags for research report Source: https://docs.messari.io/api-reference/endpoints/research/get-v1-reports-tags GET /research/v1/reports/tags Returns a list of research report tags # Research API Source: https://docs.messari.io/api-reference/endpoints/research/research-api Access Messari's professional research reports covering in-depth analysis of crypto assets, sectors, and market trends to inform your investment decisions and market understanding. ## Available Endpoints The Research API consists of three main endpoints: * [**Get Reports**](/api-reference/endpoints/research/get-v1-reports) - Returns a paginated list of research reports, with filtering options by date, tag, and other parameters. * [**Get Report Details**](/api-reference/endpoints/research/get-v1-reports-reportId) - Returns the complete content and metadata for a specific research report. * [**Get Report Tags**](/api-reference/endpoints/research/get-v1-reports-tags) - Returns all available tags used to categorize research reports, enabling targeted searches. ## Use Cases The Research API enables developers to: * Integrate professional crypto research directly into investment platforms * Build custom research libraries organized by asset, sector, or theme * Create notification systems for new research on specific assets or topics * Power knowledge bases with expert analysis on market developments * Enhance trading platforms with fundamental research context * Provide users with educational content on emerging crypto trends * Complement quantitative data with qualitative expert analysis # Assets Source: https://docs.messari.io/api-reference/endpoints/signal/assets/get-v1-assets GET /signal/v1/assets Retrieve a list of Assets **x402 Support:** Supported. See the [x402 guide](/api-reference/x402-payments#supported-endpoints). # Asset by ID Source: https://docs.messari.io/api-reference/endpoints/signal/assets/get-v1-assets-assetID GET /signal/v1/assets/{assetID} Retrieve a specific asset **x402 Support:** Supported. See the [x402 guide](/api-reference/x402-payments#supported-endpoints). # Mindshare Gainers 24H Source: https://docs.messari.io/api-reference/endpoints/signal/assets/get-v1-assets-mindshare-gainers-24h GET /signal/v1/assets/mindshare-gainers-24h Retrieve assets with the biggest mindshare gains in the last 24 hours **x402 Support:** Supported. See the [x402 guide](/api-reference/x402-payments#supported-endpoints). # Mindshare Gainers 7D Source: https://docs.messari.io/api-reference/endpoints/signal/assets/get-v1-assets-mindshare-gainers-7d GET /signal/v1/assets/mindshare-gainers-7d Retrieve a list of Assets **x402 Support:** Supported. See the [x402 guide](/api-reference/x402-payments#supported-endpoints). # Mindshare Losers 24H Source: https://docs.messari.io/api-reference/endpoints/signal/assets/get-v1-assets-mindshare-losers-24h GET /signal/v1/assets/mindshare-losers-24h Retrieve a list of Assets **x402 Support:** Supported. See the [x402 guide](/api-reference/x402-payments#supported-endpoints). # Mindshare Losers 7D Source: https://docs.messari.io/api-reference/endpoints/signal/assets/get-v1-assets-mindshare-losers-7d GET /signal/v1/assets/mindshare-losers-7d Retrieve a list of Assets **x402 Support:** Supported. See the [x402 guide](/api-reference/x402-payments#supported-endpoints). # Assets Time Series with Granularity Source: https://docs.messari.io/api-reference/endpoints/signal/assets/get-v1-assets-time-series-granularity GET /signal/v1/assets/time-series/{granularity} Retrieve assets timeseries data **x402 Support:** Supported (conditions apply). **Conditions:** x402 is available only when `granularity` is one of `1h`, `1d`. See the [x402 guide](/api-reference/x402-payments#supported-endpoints). # Signals API Source: https://docs.messari.io/api-reference/endpoints/signal/overview Track which crypto assets are capturing attention from influential voices in real-time ## Asset Mindshare: Quantifying Crypto Asset Attention In the competitive landscape of cryptocurrencies, attention is a scarce resource. Assets that capture mindshare from influential voices often enjoy increased visibility, trading volume, and potentially price action. The Signals API provides programmatic access to data showing which assets are being discussed by key opinion leaders in the crypto space. ## Methodology Posts, replies, and retweets from high-mindshare users are routinely captured. All crypto-relevant assets, projects, persons, and organizations are extracted from these posts. Entity mindshare is calculated using the aggregate engagement metrics of the posts mentioning each entity. ## Available Endpoints The Signals API provides several endpoints to track asset attention: * **List Assets** - Retrieve a comprehensive list of tracked crypto assets with their basic information * **Asset Details** - Get detailed information about a specific asset, including its current mindshare metrics * **Assets Time Series** - Track how assets' mindshare has changed over time * **Assets Time Series with Granularity** - Analyze asset mindshare with custom time granularity (from minutes to years) * **Mindshare Gainers 24H** - View top assets with the biggest mindshare gains in the last 24 hours * **Mindshare Losers 24H** - View assets with the biggest mindshare losses in the last 24 hours * **Mindshare Gainers 7D** - View top assets with the biggest mindshare gains over the last 7 days * **Mindshare Losers 7D** - View assets with the biggest mindshare losses over the last 7 days ## What You Can Build ### Asset Attention Monitoring The Signals API lets you track which assets are capturing the most attention from influential voices. With this data, you can: * Identify which assets are gaining or losing attention in real-time * Track mindshare shifts across different asset categories (DeFi, Layer 1s, NFTs, etc.) * Measure the impact of project announcements, partnerships, or market events on an asset's social visibility ### Comparative Analysis By comparing mindshare data across different assets, you can: * Benchmark assets against their competitors within the same sector * Identify emerging assets that are gaining disproportionate attention relative to their market cap * Correlate mindshare metrics with price action to identify potential trading signals ### Trend Detection The time series data enables you to: * Spot early signals of growing interest in specific assets * Identify patterns in how social attention correlates with market movements * Recognize when influential voices begin to shift focus to new narratives or assets ## Demos Check out our interactive demo to see the Signals API in action. Track cryptocurrency asset rankings and performance over time based on social mindshare # List Stablecoin Metrics Source: https://docs.messari.io/api-reference/endpoints/stablecoins/list-stablecoin-metrics GET /metrics/v2/stablecoins/metrics Get metric catalog of datasets for stablecoins. **x402 Support:** Supported. See the [x402 guide](/api-reference/x402-payments#supported-endpoints). # List Stablecoins Source: https://docs.messari.io/api-reference/endpoints/stablecoins/list-stablecoins GET /metrics/v2/stablecoins Retrieve a list of stablecoins **x402 Support:** Supported. See the [x402 guide](/api-reference/x402-payments#supported-endpoints). # Stablecoin Timeseries Metric Source: https://docs.messari.io/api-reference/endpoints/stablecoins/stablecoin-timeseries-metric GET /metrics/v2/stablecoins/{entityIdentifier}/metrics/{datasetSlug}/time-series Retrieve a specific stablecoin's timeseries data **x402 Support:** Supported. See the [x402 guide](/api-reference/x402-payments#supported-endpoints). # Stablecoins API Source: https://docs.messari.io/api-reference/endpoints/stablecoins/stablecoins-api Messari's Stablecoin API provides fundamental stablecoin data to measure the growth, usage and activity of stablecoins across different stablecoins and blockchain networks # Available Endpoints * [**List Stablecoins**](/api-reference/endpoints/stablecoins/list-stablecoins): Returns all available stablecoins and their coverage within Messari. * [**List Stablecoin Metrics**](/api-reference/endpoints/stablecoins/list-stablecoin-metrics): Returns a list of all the available timeseries metrics for stablecoins. * [**Stablecoin Timeseries Metric**](/api-reference/endpoints/stablecoins/stablecoin-timeseries-metric): Returns data points for a chosen timeseries metric set (either core or breakdown by network). Typically used for export of complete data series or graphical visualizations. # Available Endpoints The Stablecoins API allows developers to: * Measure stablecoin marketcap and stablecoin marketcap changes * Identify usage of stablecoins across active addresses,, transfer volume and transactions * Determine inflows and outflows of stablecoins across different networks # Get Allocations Source: https://docs.messari.io/api-reference/endpoints/token-unlocks/get-v1-allocations GET /token-unlocks/v1/allocations Returns allocation information given a set of asset IDs and optional filters **x402 Support:** Supported. See the [x402 guide](/api-reference/x402-payments#supported-endpoints). # Get Assets Source: https://docs.messari.io/api-reference/endpoints/token-unlocks/get-v1-assets GET /token-unlocks/v1/assets Returns assets with allocation information given a set of filters **x402 Support:** Supported. See the [x402 guide](/api-reference/x402-payments#supported-endpoints). # Get Asset Events Source: https://docs.messari.io/api-reference/endpoints/token-unlocks/get-v1-assets-assetId-events GET /token-unlocks/v1/assets/{assetId}/events Returns unlock events for a given asset **x402 Support:** Supported. See the [x402 guide](/api-reference/x402-payments#supported-endpoints). # Get Asset Unlocks Source: https://docs.messari.io/api-reference/endpoints/token-unlocks/get-v1-assets-assetId-unlocks GET /token-unlocks/v1/assets/{assetId}/unlocks Returns interval-based unlock timeseries data for a given asset and interval **x402 Support:** Supported. See the [x402 guide](/api-reference/x402-payments#supported-endpoints). # Get Asset Vesting Schedule Source: https://docs.messari.io/api-reference/endpoints/token-unlocks/get-v1-assets-assetId-vesting-schedule GET /token-unlocks/v1/assets/{assetId}/vesting-schedule Returns vesting schedule timeseries data for a given asset **x402 Support:** Supported. See the [x402 guide](/api-reference/x402-payments#supported-endpoints). # Token Unlocks API Source: https://docs.messari.io/api-reference/endpoints/token-unlocks/token-unlocks-api Monitor token vesting schedules, upcoming unlock events, and token allocation details across crypto projects to stay ahead of potential market impacts. ## Available Endpoints The Token Unlocks API consists of five main endpoints: * [**Get Allocations**](/api-reference/endpoints/token-unlocks/get-v1-allocations) - Returns a comprehensive list of token allocations across various projects, including investor details and allocation sizes. * [**Get Assets**](/api-reference/endpoints/token-unlocks/get-v1-assets) - Returns a list of assets with token unlock data available in the system. * [**Get Asset Events**](/api-reference/endpoints/token-unlocks/get-v1-assets-assetId-events) - Returns specific unlock events for a given asset, including dates and token amounts. * [**Get Asset Unlocks**](/api-reference/endpoints/token-unlocks/get-v1-assets-assetId-unlocks) - Returns aggregated unlock data for a specific asset over time. * [**Get Asset Vesting Schedule**](/api-reference/endpoints/token-unlocks/get-v1-assets-assetId-vesting-schedule) - Returns the complete vesting schedule for a specific asset, showing how tokens will be released over time. ## Use Cases The Token Unlocks API enables developers to: * Build dashboards that monitor upcoming token unlocks for potential market impact * Create alerts for significant unlock events that may affect token prices * Analyze vesting schedules to understand long-term token supply dynamics * Compare token allocation structures across different projects * Identify patterns between unlock events and historical price movements * Integrate unlock data into trading strategies or risk management systems * Track insider and investor token release schedules for sentiment analysis # Get Topic Classes Source: https://docs.messari.io/api-reference/endpoints/topics/get-v1-classes GET /topics/v1/classes Retrieve a list of all available topic classes. Topic classes categorize topics into themes like 'Partnership', 'Security and Hacks', 'Token Listing', etc. ## Overview This endpoint returns all available topic classification categories. Topic classes help organize and filter topics into meaningful themes like partnerships, security events, token listings, and more. ## Response Structure The response includes an array of topic class names as strings. Each class represents a category that topics can be classified into. ## Topic Class Categories Topics are classified into the following main categories: ### Project Development * **Partnership**: Collaborations and strategic partnerships * **Feature Release**: New feature launches and product updates * **Network Upgrade**: Protocol upgrades and improvements * **Network Launch**: New blockchain or network launches * **Network Deployment**: Deployment to new networks or chains * **Project Announcements**: General project updates and announcements * **Project Strategy**: Strategic direction and planning announcements ### Token & Tokenomics * **Token Listing**: New exchange listings * **Airdrop**: Token airdrops and distributions * **Token Swap or Migration**: Token migrations and swaps * **Treasury Management**: Treasury operations and management * **Treasury Expense**: Treasury spending and allocations * **Project Team Funding**: Team funding rounds and allocations ### Security & Operations * **Security and Hacks**: General security concerns * **Protocol Exploit**: Smart contract exploits and hacks * **Vulnerability Disclosure**: Security vulnerability announcements * **Centralized Exchange Loss of Funds**: Exchange-related security incidents * **Bug Disclosure**: Bug reports and disclosures * **Network Congestion**: Network performance issues * **Blockchain Halt**: Chain halts and downtime * **Node Outage**: Node and infrastructure outages * **Chain Split**: Blockchain forks and splits ### Business & Governance * **Funding**: Fundraising rounds and investments * **Legal and Regulatory**: Regulatory news and legal developments * **Governance Update**: DAO and governance proposals * **Incentives Program**: Reward programs and incentive structures * **Community Update**: Community-driven updates and news ### Operations & Events * **Discontinued Product**: Product sunsets and deprecations ### Noise/Informational (typically filtered by default) * **Macro Commentary**: General market commentary * **Price Analysis**: Price predictions and technical analysis * **Irrelevant Content**: Off-topic or non-substantive content ## Usage Example ```bash theme={null} curl -X GET "https://api.messari.io/topics/v1/classes" \ -H "x-messari-api-key: YOUR_API_KEY" ``` ## Use Cases 1. **Build Filter UIs**: Create topic class selectors in your application 2. **Understand Classification**: Learn what categories are available for filtering 3. **Dynamic Query Building**: Programmatically construct filtered topic queries 4. **Documentation**: Reference available classes when using other Topics API endpoints ## Next Steps After retrieving the topic classes, use them to filter results in the [Get Current Topics](/api-reference/endpoints/topics/get-v1-current) endpoint by passing them via the `classes` query parameter. # Get Current Topics Source: https://docs.messari.io/api-reference/endpoints/topics/get-v1-current GET /topics/v1/current Retrieve today's trending topics. Returns a snapshot of topics that are actively trending right now, refreshed throughout the day. Topics can be filtered by class and sorted by different criteria. Each topic includes a title, summary, detailed content, rank, associated assets, and top source documents. ## Overview Retrieve today's trending topics in the crypto ecosystem. This endpoint returns a snapshot of topics that are actively trending right now, refreshed throughout the day. Each topic includes a title, AI-generated summary, detailed content with bullet points, associated assets, source documents, and classification tags. For historical topic data, use the [Get Topics Timeseries](/api-reference/endpoints/topics/get-v1-daily) endpoint. ## Query Parameters ### classes Filter topics by classification categories. Provide a comma-separated list of topic classes. **Example**: `?classes=Partnership,Token Listing,Airdrop` By default, the following classes are excluded to reduce noise: * Macro Commentary * Price Analysis * Irrelevant Content Use the [Get Topic Classes](/api-reference/endpoints/topics/get-v1-classes) endpoint to see all available classes. ### sort Control the order of returned topics: * **trending** (default): Topics ranked by momentum and recent activity * **new**: Most recently detected topics first * **top**: Topics with the most source documents and engagement **Example**: `?sort=new` ### assetIDs Filter topics by associated assets. Provide a comma-separated list of asset identifiers. Accepts any combination of UUIDs, slugs, or symbols. **Examples**: * By slug: `?assetIDs=bitcoin,ethereum,solana` * By symbol: `?assetIDs=BTC,ETH,SOL` * By UUID: `?assetIDs=21c795f5-1bfd-40c3-858e-e9d7e820c6d0` * Mixed: `?assetIDs=bitcoin,ETH,21c795f5-1bfd-40c3-858e-e9d7e820c6d0` ### page Page number for paginated results (1-indexed). Defaults to `1`. **Example**: `?page=2` ### limit Number of topics per page. Defaults to `1000`. **Example**: `?limit=25` ## Response Structure Each topic in the response includes: * **title**: Concise topic title * **summary**: 1-2 paragraph summary of the topic * **content**: Detailed bullet-point breakdown of key information * **rank**: Numerical ranking of the topic * **classes**: Array of classification tags * **topDocuments**: Links to the most influential source documents * **url**: Link to the source (X post, article, etc.) * **type**: Document type (x\_post, article, etc.) * **documentCount**: Total number of source documents analyzed * **avgDocumentTimestamp**: Average timestamp of source documents * **assets**: Array of related crypto assets * **id**: Asset UUID * **name**: Asset full name * **symbol**: Asset ticker symbol * **slug**: Asset URL slug ## Usage Examples ### Get Today's Trending Topics ```bash theme={null} curl -X GET "https://api.messari.io/topics/v1/current" \ -H "x-messari-api-key: YOUR_API_KEY" ``` ### Filter by Topic Classes ```bash theme={null} curl -X GET "https://api.messari.io/topics/v1/current?classes=Partnership,Security%20and%20Hacks" \ -H "x-messari-api-key: YOUR_API_KEY" ``` ### Get Topics for Specific Assets (by slug) ```bash theme={null} curl -X GET "https://api.messari.io/topics/v1/current?assetIDs=bitcoin,ethereum" \ -H "x-messari-api-key: YOUR_API_KEY" ``` ### Get Topics for Specific Assets (by symbol) ```bash theme={null} curl -X GET "https://api.messari.io/topics/v1/current?assetIDs=BTC,ETH" \ -H "x-messari-api-key: YOUR_API_KEY" ``` ### Sort by Newest Topics ```bash theme={null} curl -X GET "https://api.messari.io/topics/v1/current?sort=new" \ -H "x-messari-api-key: YOUR_API_KEY" ``` ### Paginate Results ```bash theme={null} curl -X GET "https://api.messari.io/topics/v1/current?limit=25&page=1" \ -H "x-messari-api-key: YOUR_API_KEY" ``` ## Response Metadata The response includes metadata about the results: * **snapshotTime**: When the topics snapshot was generated * **includedClasses**: Which topic classes were included in the results * **page**: Current page number * **pageSize**: Number of topics per page * **totalRows**: Total number of matching topics * **totalPages**: Total number of pages available ## Best Practices 1. **Use Class Filters**: Reduce response size and noise by filtering to relevant classes 2. **Check Source Documents**: Verify topic accuracy by reviewing topDocuments 3. **Monitor Asset Activity**: Track topics for your portfolio assets using assetIDs filter 4. **Rate Limit Considerations**: Topics refresh regularly, avoid polling more than once per minute 5. **Paginate Large Responses**: Use `page` and `limit` to reduce response size and improve performance 6. **Combine Filters**: Use multiple filters together for precise results ## Common Use Cases * **Build a Crypto News Feed**: Display trending topics as a news dashboard * **Asset Monitoring**: Track all developments for specific assets in your portfolio * **Security Alerts**: Monitor for "Protocol Exploit" and "Security and Hacks" classes * **Partnership Tracking**: Discover new collaborations and strategic moves * **Market Intelligence**: Analyze which topics are gaining traction # Get Topics Timeseries Source: https://docs.messari.io/api-reference/endpoints/topics/get-v1-daily GET /topics/v1/daily Retrieve a timeseries of global topics over a specified time range. Returns historical topic data with rankings and associated metadata. Maximum range is 90 days. ## Overview Retrieve historical timeseries data for trending topics. This endpoint allows you to analyze how topics evolved over time, track when topics first appeared, and understand historical narrative trends in the crypto ecosystem. ## Query Parameters ### start (required) Start of the time range in ISO 8601 format. **Example**: `?start=2025-01-01T00:00:00Z` ### end (required) End of the time range in ISO 8601 format. **Example**: `?end=2025-01-07T23:59:59Z` ### granularity Time interval for data points: * **1d** (default): Daily data points * **1h**: Hourly data points **Example**: `?granularity=1d` ### assetIDs Filter topics by associated assets. Provide a comma-separated list of asset identifiers. Accepts any combination of UUIDs, slugs, or symbols. **Examples**: * By slug: `?assetIDs=bitcoin,ethereum,solana` * By symbol: `?assetIDs=BTC,ETH,SOL` * By UUID: `?assetIDs=21c795f5-1bfd-40c3-858e-e9d7e820c6d0` * Mixed: `?assetIDs=bitcoin,ETH,21c795f5-1bfd-40c3-858e-e9d7e820c6d0` ## Time Range Limits * **Maximum range**: 90 days * **Default range**: 7 days (if not specified) * Ranges are automatically truncated to granularity boundaries for better caching ## Response Structure Each data point in the timeseries includes: * **time**: Unix timestamp of the data point * **title**: Topic title * **summary**: Topic summary * **content**: Detailed content with bullet points * **classes**: Array of classification tags * **rank**: Ranking of the topic at this timestamp (1 = most trending) * **topDocuments**: Links to source documents * **url**: Document URL * **type**: Document type (x\_post, article, etc.) * **documentCount**: Number of source documents * **assets**: Array of related crypto assets * **id**: Asset UUID * **name**: Asset name * **symbol**: Asset symbol * **slug**: Asset slug ## Usage Examples ### Get Daily Topics for a Week ```bash theme={null} curl -X GET "https://api.messari.io/topics/v1/daily?start=2025-01-01T00:00:00Z&end=2025-01-07T23:59:59Z&granularity=1d" \ -H "x-messari-api-key: YOUR_API_KEY" ``` ### Get Hourly Topics for 24 Hours ```bash theme={null} curl -X GET "https://api.messari.io/topics/v1/daily?start=2025-01-01T00:00:00Z&end=2025-01-02T00:00:00Z&granularity=1h" \ -H "x-messari-api-key: YOUR_API_KEY" ``` ### Get Daily Topics for Specific Assets ```bash theme={null} curl -X GET "https://api.messari.io/topics/v1/daily?start=2025-01-01T00:00:00Z&end=2025-01-07T23:59:59Z&assetIDs=bitcoin,ethereum" \ -H "x-messari-api-key: YOUR_API_KEY" ``` ### Filter by Asset Symbol ```bash theme={null} curl -X GET "https://api.messari.io/topics/v1/daily?start=2025-01-01T00:00:00Z&end=2025-01-07T23:59:59Z&assetIDs=BTC,ETH" \ -H "x-messari-api-key: YOUR_API_KEY" ``` ## Analysis Use Cases ### Track Topic Persistence Identify which topics stay relevant over extended periods vs. flash-in-the-pan news. ### Analyze Topic Classes Over Time See how different types of topics (security, partnerships, etc.) trend seasonally. ### Monitor Asset Narratives Track how often specific assets appear in trending topics over time. Use the `assetIDs` filter to focus on assets in your portfolio. ### Detect Narrative Shifts Identify when new topics emerge or old topics fade from attention. ### Compare Time Periods Analyze how topic landscape differs between bull and bear markets. ## Best Practices 1. **Use Appropriate Granularity**: Daily for long-term trends, hourly for real-time analysis 2. **Respect Time Limits**: Don't request more than 90 days at once 3. **Handle Empty Results**: Some time periods may have no trending topics 4. **Cache Historical Data**: Past data doesn't change, cache it locally 5. **Batch Requests**: For large date ranges, break into multiple smaller requests ## Response Format Topics are sorted by: 1. Timestamp (ascending) 2. Trending score (descending - higher ranks first) This means for each timestamp, you'll see the most important topics first. ## Error Handling Common errors: * **400 Bad Request**: Invalid date format or time range exceeds 90 days * **403 Forbidden**: Insufficient API permissions * **500 Internal Server Error**: Temporary service issue, retry with backoff # Topics API Source: https://docs.messari.io/api-reference/endpoints/topics/topics-api The Topics API provides access to AI-analyzed trending topics in the crypto ecosystem. Discover what's trending, track topic evolution over time, and understand the narrative landscape through automated topic classification and summarization. ## Overview The Topics API uses advanced AI models to analyze millions of social media posts, articles, and other content sources to identify and track emerging topics in crypto. Each topic is automatically classified, summarized, and linked to relevant assets, providing a comprehensive view of the crypto narrative landscape. ## Available Endpoints The Topics API consists of three main endpoints: * [**Get Topic Classes**](/api-reference/endpoints/topics/get-v1-classes) - Returns all available topic classification categories (e.g., "Partnership", "Token Listing", "Security and Hacks") * [**Get Current Topics**](/api-reference/endpoints/topics/get-v1-current) - Returns today's trending topics with full details including summaries, source documents, and associated assets * [**Get Topics Timeseries**](/api-reference/endpoints/topics/get-v1-daily) - Returns historical topic data over time for trend analysis ## Key Features ### AI-Powered Topic Detection Topics are automatically identified and analyzed from millions of data sources including: * Social media posts (X/Twitter, Reddit, etc.) * News articles and blog posts * Project announcements * Community discussions ### Intelligent Classification Each topic is automatically classified into one or more categories: * **Project Updates**: Partnership, Feature Release, Network Upgrade, Governance Update * **Security**: Protocol Exploit, Vulnerability Disclosure, Security and Hacks * **Market Activity**: Token Listing, Airdrop, Funding * **Operations**: Treasury Management, Incentives Program, Network Congestion * **Regulatory**: Legal and Regulatory, Community Update ### Asset Association Topics are automatically linked to relevant crypto assets, making it easy to: * Track all topics related to a specific asset * Discover which assets are involved in trending narratives * Monitor project-specific news and developments ### Source Attribution Every topic includes links to top source documents: * View the most influential posts and articles * Verify topic accuracy with primary sources * Understand community sentiment through direct links ## Use Cases The Topics API enables developers to: * **Build Topic Monitoring Dashboards**: Track trending topics in real-time and identify emerging narratives * **Create Asset-Specific News Feeds**: Show all topics related to specific assets or portfolios * **Analyze Market Sentiment**: Study topic evolution over time to understand market dynamics * **Power Research Tools**: Enable analysts to discover and investigate important crypto developments * **Automate Alert Systems**: Trigger notifications when specific topic classes emerge for monitored assets ## Demo Check out our interactive demo to see the Topics API in action. Explore today's trending topics and narratives in the crypto conversation ## Topic Lifecycle Topics progress through different stages: 1. **Detection**: AI identifies emerging clusters of related content 2. **Classification**: Topics are categorized into relevant classes 3. **Summarization**: AI generates comprehensive summaries with key bullet points 4. **Ranking**: Topics are ranked by trending score, recency, or popularity 5. **Evolution**: Topics are tracked over time as narratives develop ## Filtering and Sorting ### Topic Classes Filter Control which types of topics you receive by specifying classes: ``` ?classes=Partnership,Token Listing,Airdrop ``` By default, promotional and noise categories like "Macro Commentary", "Price Analysis", and "Irrelevant Content" are excluded to focus on substantive developments. ### Sort Options * **trending**: Topics sorted by momentum and recent activity (default) * **new**: Latest topics first * **top**: Topics with most source documents and engagement ### Asset Filter Focus on specific assets using any combination of UUIDs, slugs, or symbols: ``` ?assetIDs=bitcoin,ETH,solana ``` ## Rate Limits & Best Practices * Current topics refresh regularly - no need to poll more frequently than once per minute * Historical timeseries supports up to 90 days per request * Use topic classes filter to reduce payload size and focus on relevant categories * Cache results appropriately as historical data doesn't change ## Authentication All Topics API requests require authentication via the `x-messari-api-key` header. Visit [messari.io/account/api](https://messari.io/account/api) to obtain your API key. # Delete Watchlist Source: https://docs.messari.io/api-reference/endpoints/user-management/delete-v1-watchlists-id DELETE /user-management/v1/watchlists/{id} Delete a specific watchlist by ID for the authenticated user ## Overview Permanently deletes a watchlist. This action cannot be undone. A successful deletion returns a `200` status code with an empty response body. # Get Watchlists Source: https://docs.messari.io/api-reference/endpoints/user-management/get-v1-watchlists GET /user-management/v1/watchlists Get all watchlists for the authenticated user ## Overview Returns all watchlists accessible to the authenticated user, including both personally created watchlists and team-shared watchlists. Each watchlist in the response includes its metadata and the list of asset IDs it contains. # Get Watchlist Details Source: https://docs.messari.io/api-reference/endpoints/user-management/get-v1-watchlists-id GET /user-management/v1/watchlists/{id} Get a specific watchlist by ID for the authenticated user ## Overview Returns the full details of a specific watchlist, including its metadata and all asset IDs. Use this endpoint to fetch the current state of a single watchlist by its ID. # Update Watchlist Source: https://docs.messari.io/api-reference/endpoints/user-management/patch-v1-watchlists-id PATCH /user-management/v1/watchlists/{id} Update a specific watchlist by ID for the authenticated user ## Overview Updates a watchlist's metadata such as its title. Only the fields provided in the request body will be updated — omitted fields remain unchanged. If `assetIds` is provided, it replaces the entire asset list. If omitted, assets remain unchanged. If an empty array is provided, all assets are removed. To add or remove individual assets without replacing the full list, use the [Update Watchlist Assets](/api-reference/endpoints/user-management/patch-v1-watchlists-id-assets) endpoint instead. # Update Watchlist Assets Source: https://docs.messari.io/api-reference/endpoints/user-management/patch-v1-watchlists-id-assets PATCH /user-management/v1/watchlists/{id}/assets Modify the assets in a specific watchlist by ID for the authenticated user ## Overview Add or remove individual assets from a watchlist without replacing the entire asset list. This is useful for incrementally managing watchlist contents. The `action` field must be either `add` or `remove`, and `assetIds` specifies which asset UUIDs to add or remove. To replace the entire asset list at once, use the [Update Watchlist](/api-reference/endpoints/user-management/patch-v1-watchlists-id) endpoint with the `assetIds` field instead. # Create Watchlist Source: https://docs.messari.io/api-reference/endpoints/user-management/post-v1-watchlists POST /user-management/v1/watchlists Create a new watchlist for the authenticated user ## Overview Creates a new watchlist for the authenticated user. A watchlist groups assets together for tracking and monitoring. You must provide a title and a list of asset IDs (UUIDs). Asset IDs must be Messari UUIDs (e.g., `1e31218a-e44e-4285-820c-8282ee222035` for Bitcoin). Slugs and symbols are not accepted. Use the [Asset API](/api-reference/endpoints/asset) to look up asset UUIDs. # Watchlists API Source: https://docs.messari.io/api-reference/endpoints/user-management/user-management-api Create and manage custom watchlists to organize and track groups of assets via the Messari API. ## Available Endpoints * [**Get Watchlists**](/api-reference/endpoints/user-management/get-v1-watchlists) - Returns all watchlists created by the authenticated user. * [**Get Watchlist Details**](/api-reference/endpoints/user-management/get-v1-watchlists-id) - Returns details for a specific watchlist, including assets. * [**Create Watchlist**](/api-reference/endpoints/user-management/post-v1-watchlists) - Creates a new watchlist with specified assets and configuration. * [**Update Watchlist**](/api-reference/endpoints/user-management/patch-v1-watchlists-id) - Updates a watchlist's name, description, or other metadata. * [**Update Watchlist Assets**](/api-reference/endpoints/user-management/patch-v1-watchlists-id-assets) - Modifies the assets included in a specific watchlist. * [**Delete Watchlist**](/api-reference/endpoints/user-management/delete-v1-watchlists-id) - Removes a specified watchlist. ## Use Cases * Create personalized asset tracking experiences with custom watchlists * Build portfolio monitoring applications with user-specific asset groupings * Enable users to organize assets by categories, sectors, or personal preferences * Sync watchlists across multiple clients or applications # Errors Source: https://docs.messari.io/api-reference/errors Messari uses conventional HTTP response codes to indicate the success or failure of an API request. In general: * Codes in the 2xx range indicate success * Codes in the 4xx range indicate an error that failed given the information provided (e.g., a required parameter was omitted, an entity was not found, etc.) * Codes in the 5xx range indicate an error with Messari's servers (these are rare) ## HTTP Status Codes | HTTP Status Code | Status Text | Description | | - | - | - | | 200 | OK | Everything worked as expected. | | 400 | Bad Request | The request was unacceptable, often due to missing a required parameter. | | 401 | Unauthorized | No valid API key provided. | | 402 | Request Failed | The parameters were valid but the request failed. | | 403 | Forbidden | The API key doesn't have permissions to perform the request. | | 404 | Not Found | The requested resource doesn't exist. | | 429 | Too Many Requests | Too many requests hit the API too quickly and were rate limited. We recommend an exponential backoff of your requests. | | 500 | Internal Server Error | Something went wrong on Messari's end. (These are rare.) | ## Common Issues ### Permissions Issues (403) If you are receiving unexpected 403 errors for a service you believe you have access to, it is best to reach out to our customer support team. They should be able to help resolve your issue quickly. ### Server Errors (500) If you are receiving unexpected 500 errors then you might have found an issue with our system. Although we monitor for these, we appreciate reporting such errors so we can look into it and resolve the issue for you and others! Note: to expedite the resolution process, provide the request identifier when you contact us about a specific request. # API Tiers & Limits Source: https://docs.messari.io/api-reference/permissions API access is structured according to your Messari subscription level. * **Enterprise Users:** Enjoy unlimited access to the Market Data API endpoints. For access to additional API services such as News, Token Unlocks, Fundraising data or more, please [get in touch](https://blockworks.com/contact) to discuss Enterprise options. * **All Users with an API Key:** Have access to the MessariAI API (AI) chat completion endpoints ## **Rate Limit Structure** The Messari API employs a two-tiered rate limiting system (see below). ### **Global Rate Limit** Global rate limits apply to your overall API usage across all Messari services. These limits restrict the total number of requests you can make to our API within a specified time window, regardless of which specific endpoints you're accessing. Global limits help us manage overall system load and ensure equitable resource distribution among all users. | **Subscription Level** | **Rate Limit** | **Note** | | :- | :- | :- | | Unpaid / Lite / Pro | 200 requests / min | Assuming the endpoint to not be Enterprise-gated (small subset) | | Enterprise | 600 requests / min | Assuming Enterprise team to have access to underlying service endpoints | Note: It should be rare that you encounter these as they as established to prevent abuse. ### **Service-Level Rate Limits** In addition to global limits, we implement service-specific rate limits that apply to individual API services or endpoint groups. These more granular limits are tailored to the computational intensity and resource requirements of the service. These rate limits and their underlying subscription access tier are documented within each endpoint's documentation! ## MessariAI API Rate Limits The MessariAI API has different rate limits based on your subscription tier. The table below shows the maximum number of requests allowed per day for each tier: | Subscription Tier | Request Limit | | - | - | | Free | 10 per day | | Enterprise | 600 per minute | These limits apply to the AI chat completion endpoints. If you need higher limits, please [get in touch](https://blockworks.com/contact) to discuss buying a credit pack or see our [AI Credits System](#ai-credits-system) section below for more details. ## AI Credits System The MessariAI API uses a credit system to track usage for Enterprise users who buy a credit pack. Each request consumes a certain number of credits, which are deducted from your account balance. # Response Source: https://docs.messari.io/api-reference/responses A typical response from the Messari Crypto API will be in JSON format and will look like the following: ```json theme={null} { "error": null, "data": { // Data specific to the API endpoint }, "metadata": { // Additional contextual information (optional). } } ``` ## Fields Explained | Field | Type | Description | Usage | | - | - | - | - | | error | string or null | This field indicates whether an error occurred during the API request. If the request was successful, this field will be ⁠null. If there was an error, it will contain a descriptive error message explaining what went wrong. | Always check this field first to determine if your API call was successful before attempting to access the ⁠data | | data | object (varies based on the endpoint) | This field contains the actual response data returned by the API. The structure of this object will vary depending on the specific endpoint being called. | After confirming there is no error, you can access this field to retrieve the requested information | | metadata | object or ⁠null (optional) | This optional field may include additional contextual information related to the API response, such as pagination details, request duration, or trace information. If there are no additional details to provide, the ⁠metadata field may be omitted entirely from the response. | If present, this field can provide useful insights for managing and optimizing your API usage. | When working with the Messari Crypto API, always check the `error` field in the JSON response to determine if your request was successful. If `error` is `null`, proceed to access the `data` field for the necessary information. Additionally, review the `metadata` field, if available, for extra context regarding your API call. This standardized response structure helps ensure that developers can consistently handle and interpret API responses effectively across all endpoints. ## Example JSON Response ### Successful Response In a successful response, the API returns the requested data along with any relevant metadata: ```json theme={null} { "error": null, "data": { "messages": [ { "role": "assistant", "content": "### Overview of Hyperliquid HyperEVM\n\n**Hyperliquid HyperEVM** is an innovative integration of the Ethereum Virtual Machine (EVM) into Hyperliquid's Layer 1 blockchain, announced on February 18, 2025. \n\n#### Key Features and Highlights:\n1. **EVM Integration**: HyperEVM allows for enhanced programmability and performance for Ethereum-compatible smart contracts within the Hyperliquid ecosystem.\n2. **Spot Transfers**: The initial release supports spot transfers between native HYPE and HyperEVM HYPE.\n3. **DeFi Enhancement**: The HyperEVM includes elements such as a canonical WHYPE system contract to support decentralized financial applications.\n4. **Security and Consensus**: It maintains robust security through HyperBFT consensus, ensuring reliable operation within the network.\n5. **Performance Improvements**: The integration aims to provide high transaction capacity and low fees, leveraging Hyperliquid's highly optimized trading infrastructure.\n\n#### Additional Developments:\n- **Bug Bounty Program**: To enhance security, a bug bounty program was launched offering substantial rewards for identifying vulnerabilities in the system.\n- **Future Upgrades**: Plans include enabling ERC-20 native transfers and additional precompiles to expand functionality.\n\nThis new integration positions Hyperliquid as a comprehensive DeFi ecosystem, aiming to leverage the strengths of EVM with the robust infrastructure of its native blockchain." } ] }, "metadata": { "status": "Completed", "trace_id": "df89a737-b988-4643-97ba-08645ef8bd77" } } ``` ### Error Response If an error occurs, the response will provide information about the error: ```json theme={null} { "error": "Invalid API key", "data": null } ``` For more information on handling errors and the status codes that accompany unsuccessful requests, see the errors page. ## Pagination Many Messari API endpoints that return multiple items support pagination to help you navigate through large result sets. Pagination information is included in the `metadata` field of the response. The pagination structure contains the following attributes: ```json theme={null} { "limit": 10, "page": 1, "totalRows": 100, "totalPages": 10 } ``` ## Request ID Each API request has an associated request identifier. You can find this value in the response headers, under `x-request-id`. To expedite the resolution process, provide the request identifier when you contact us about a specific request. # Versioning Source: https://docs.messari.io/api-reference/versioning Messari's API follows a versioning scheme to ensure stability and backward compatibility while allowing for continuous improvements. ## Base URL and Versioning Format All API endpoints follow the structure -- `https://api.messari.io//v1/` * `` represents the specific service being accessed (e.g., `marketdata`, `ai`, `news`, etc.) * `/v1/` denotes the API version * `` refers to the specific resource or operation being requested ## Versioning Strategy Messari adheres to a semantic versioning approach for API updates: * Breaking Changes: Any changes that alter existing functionality in a non-backward-compatible way will result in a version bump (e.g., from `v1` to `v2`). * Non-Breaking Changes: Additions such as new endpoints, optional parameters, or enhancements to existing functionality will be introduced within the current version (`v1`). ## Deprecation and Change Management * Older versions of the API will remain accessible for a defined period after a new version is introduced. * Deprecation notices will be provided in advance, along with migration guides. * All changes, including enhancements and deprecations, will be documented in the API Changelog. # Pay-Per-Request with x402 Source: https://docs.messari.io/api-reference/x402-payments Access Messari APIs without an account using USDC micropayments on Base or Solana via x402. ## Overview x402 is an HTTP-native payment protocol that enables pay-per-request API access using USDC on Base Mainnet or Solana Mainnet. With x402, you can access Messari endpoints without a Messari account or API key — simply pay per request with crypto. **When to use x402:** Autonomous agents that need to query Messari data without managing API keys or subscriptions Data pipelines that require one-off or sporadic queries billed directly on-chain Quick queries without signing up for an account or committing to a subscription ## Supported Endpoints Endpoint support and pricing can change over time.
Endpoint Route Method Price
MessariAI
Chat Completion - Messari v2 /ai/v2/chat/completions POST \$0.25 per request
Assets & Market Data
List Assets /metrics/v2/assets GET \$0.00 per request
Get All-Time Highs /metrics/v2/assets/ath GET \$0.10 per request
Get Asset Details /metrics/v2/assets/details GET \$0.10 per request
List Metrics /metrics/v2/assets/metrics GET \$0.00 per request
Get ROIs /metrics/v2/assets/roi GET \$0.10 per request
Asset Timeseries /metrics/v2/assets/\{assetID}/metrics/\{datasetSlug}/time-series/\{granularity} GET
1h: \$0.18
1d: \$0.15
Markets
Get Markets /metrics/v1/markets GET \$0.00 per request
Get Market Timeseries Metrics /metrics/v1/markets/metrics GET \$0.35 per request
Get Market Timeseries /metrics/v1/markets/\{entityIdentifier}/metrics/\{datasetSlug}/time-series GET \$0.75 per request
Get Market Timeseries /metrics/v1/markets/\{entityIdentifier}/metrics/\{datasetSlug}/time-series/\{granularity} GET
1h: \$1.00
1d: \$0.75
Get Market /metrics/v1/markets/\{marketIdentifier} GET \$0.35 per request
Exchanges
List Exchanges /metrics/v1/exchanges GET \$0.00 per request
List Exchanges Metrics /metrics/v1/exchanges/metrics GET \$0.35 per request
Get Exchange Timeseries /metrics/v1/exchanges/\{entityIdentifier}/metrics/\{datasetSlug}/time-series GET \$0.45 per request
Exchange Time Series Metric /metrics/v1/exchanges/\{entityIdentifier}/metrics/\{datasetSlug}/time-series/\{granularity} GET
1h: \$0.55
1d: \$0.45
Get Exchange /metrics/v1/exchanges/\{exchangeIdentifier} GET \$0.35 per request
Networks
Networks /metrics/v2/networks GET \$0.00 per request
Network Metrics /metrics/v2/networks/metrics GET \$0.00 per request
Network Time Series /metrics/v2/networks/\{entityIdentifier}/metrics/\{datasetSlug}/time-series GET \$0.15 per request
Network Time Series with Granularity /metrics/v2/networks/\{entityIdentifier}/metrics/\{datasetSlug}/time-series/\{granularity} GET
5m: \$0.25
15m: \$0.23
1h: \$0.18
1d: \$0.15
Stablecoins
List Stablecoins /metrics/v2/stablecoins GET \$0.00 per request
List Stablecoin Metrics /metrics/v2/stablecoins/metrics GET \$0.00 per request
Stablecoin Timeseries Metric /metrics/v2/stablecoins/\{entityIdentifier}/metrics/\{datasetSlug}/time-series GET \$0.25 per request
Fundraising
Funds /funding/v1/funds GET \$0.35 per request
Funds Managers /funding/v1/funds/managers GET \$0.25 per request
Mergers and Acquisitions /funding/v1/mergers-and-acquisitions GET \$0.25 per request
Organizations /funding/v1/organizations GET \$0.25 per request
Projects /funding/v1/projects GET \$0.15 per request
Rounds /funding/v1/rounds GET \$0.15 per request
Rounds Investors /funding/v1/rounds/investors GET \$0.25 per request
News
News Feed /news/v1/news/feed GET \$0.55 per request
Get News Sources /news/v1/news/sources GET \$0.00 per request
Signals
Assets /signal/v1/assets GET \$0.55 per request
Mindshare Gainers 24H /signal/v1/assets/mindshare-gainers-24h GET \$0.35 per request
Mindshare Gainers 7D /signal/v1/assets/mindshare-gainers-7d GET \$0.35 per request
Mindshare Losers 24H /signal/v1/assets/mindshare-losers-24h GET \$0.35 per request
Mindshare Losers 7D /signal/v1/assets/mindshare-losers-7d GET \$0.35 per request
Assets Time Series with Granularity /signal/v1/assets/time-series/\{granularity} GET \$0.75 per request
Asset by ID /signal/v1/assets/\{assetID} GET \$0.35 per request
Token Unlocks
Get Allocations /token-unlocks/v1/allocations GET \$0.25 per request
Get Assets /token-unlocks/v1/assets GET \$0.00 per request
Get Asset Events /token-unlocks/v1/assets/\{assetId}/events GET \$0.15 per request
Get Asset Unlocks /token-unlocks/v1/assets/\{assetId}/unlocks GET \$0.75 per request
Get Asset Vesting Schedule /token-unlocks/v1/assets/\{assetId}/vesting-schedule GET \$0.75 per request
For machine-readable discovery, call `GET https://api.messari.io/.well-known/x402`. ## Prerequisites Before making a payment, ensure you have: * An EVM-compatible wallet (e.g. MetaMask, Coinbase Wallet) * **USDC on Base Mainnet** — a minimum of \~\$1 is recommended to start * A small amount of **ETH on Base Mainnet** for gas fees Use bridge.base.org to move USDC from Ethereum or another chain onto Base Mainnet. * A Solana wallet (e.g. Phantom, Solflare) * **USDC on Solana Mainnet** — a minimum of \~\$1 is recommended to start * A small amount of **SOL** for transaction fees (typically under \$0.001 per transaction) ## How It Works x402 follows a simple 3-step flow: **Step 1: Make a request** Send your request to the Messari API without an API key. The gateway responds with `HTTP 402 Payment Required` along with payment options for each supported chain (Base and Solana), including amount, currency, recipient address, and network. **Step 2: Sign & pay** Your x402-enabled client selects the chain it's configured for and creates a payment: * **Base:** Signs a USDC `TransferWithAuthorization` (EIP-3009) message — no gas required for the authorization itself. * **Solana:** Builds and partially signs a USDC transfer transaction — gas fees are near-zero (\~\$0.001). The gateway submits the on-chain transaction on your behalf. **Step 3: Request fulfilled** The gateway verifies the signed authorization, collects the USDC payment, and proxies your original request. The API response is returned as normal. ## Quick Start (TypeScript) ```bash theme={null} npm install @x402/fetch @x402/evm viem ``` ```typescript theme={null} import { wrapFetchWithPaymentFromConfig } from '@x402/fetch'; import { ExactEvmScheme } from '@x402/evm'; import { privateKeyToAccount } from 'viem/accounts'; const account = privateKeyToAccount(process.env.PRIVATE_KEY as `0x${string}`); const fetchWithPayment = wrapFetchWithPaymentFromConfig(fetch, { schemes: [{ network: 'eip155:8453', client: new ExactEvmScheme(account) }], }); const response = await fetchWithPayment('https://api.messari.io/ai/v2/chat/completions', { method: 'POST', headers: { 'Content-Type': 'application/json' }, body: JSON.stringify({ messages: [{ role: 'user', content: 'What is the latest on Bitcoin?' }], verbosity: 'succinct', response_format: 'markdown', stream: false, }), }); const data = await response.json(); console.log(data); ``` ```bash theme={null} npm install @x402/fetch @x402/svm @solana/kit ``` ```typescript theme={null} import { wrapFetchWithPaymentFromConfig } from '@x402/fetch'; import { ExactSvmScheme } from '@x402/svm'; import { createKeyPairSignerFromBytes, getBase58Codec } from '@solana/kit'; const codec = getBase58Codec(); const keyBytes = codec.encode(process.env.SOLANA_PRIVATE_KEY!); const signer = await createKeyPairSignerFromBytes(keyBytes); const fetchWithPayment = wrapFetchWithPaymentFromConfig(fetch, { schemes: [{ network: 'solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp', client: new ExactSvmScheme(signer) }], }); const response = await fetchWithPayment('https://api.messari.io/ai/v2/chat/completions', { method: 'POST', headers: { 'Content-Type': 'application/json' }, body: JSON.stringify({ messages: [{ role: 'user', content: 'What is the latest on Bitcoin?' }], verbosity: 'succinct', response_format: 'markdown', stream: false, }), }); const data = await response.json(); console.log(data); ``` Never hardcode your private key in source code. Use environment variables for both EVM (`process.env.PRIVATE_KEY`) and Solana (`process.env.SOLANA_PRIVATE_KEY`) keys. ## Troubleshooting **"Payment verification failed"** Your wallet does not have sufficient USDC on Base Mainnet. Check your balance and ensure you have enough USDC plus a small amount of ETH for gas. **"Unsupported network"** Supported networks are `eip155:8453` (Base Mainnet) and `solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp` (Solana Mainnet). **Payment sent but no response received** On-chain confirmation can take \~30 seconds. If you do not receive a response after 60 seconds, check the transaction status on [Basescan](https://basescan.org). If the transaction is confirmed but you still received no response, contact [api@messari.io](mailto:api@messari.io). **"Transaction simulation failed" (Solana)** The recipient wallet may not have a USDC token account on Solana. Ensure the payTo address has an Associated Token Account for USDC. You can create one by sending a small amount of USDC to that address. **Payment sent but no response received (Solana)** Solana transactions typically confirm in under a second. If you do not receive a response after 60 seconds, check the transaction on [Solana Explorer](https://explorer.solana.com). If the transaction is confirmed but you still received no response, contact [api@messari.io](mailto:api@messari.io). # SDK Code Examples Source: https://docs.messari.io/examples/overview Learn how to use the Messari SDK through practical code examples # Messari SDK Examples These examples demonstrate how to use the Messari SDK to build applications that leverage Messari's powerful APIs. The examples are designed to show you common use cases and best practices for integrating Messari data into your applications. ## Available Examples Build a conversational AI assistant powered by Messari's MessariAI API Extract crypto entities from text using Messari's AI capabilities ## GitHub Examples Repository For more comprehensive examples, including full TypeScript source code, check out our [MessariKit repository on GitHub](https://github.com/messari/MessariKit). The repository contains numerous examples showing how to use different aspects of the Messari SDK. ### MessariAI API Examples Our [MessariAI API examples](https://github.com/messari/MessariKit/blob/master/packages/examples/src/ai.ts) demonstrate how to use Messari's AI capabilities, including: * Setting up the SDK for AI API calls * Creating AI chat completions with domain-specific knowledge * Extracting entities from text * Customizing AI behavior with system prompts ```typescript theme={null} // Example: Basic AI chat completion with the Messari SDK import { MessariClient } from "@messari/client"; const client = new MessariClient({ apiKey: "YOUR_API_KEY" }); async function getChatResponse() { const response = await client.ai.chat.create({ messages: [ { role: "system", content: "You are a helpful assistant." }, { role: "user", content: "What is the current state of DeFi?" }, ], model: "messari-1", }); console.log(response.choices[0].message.content); } ``` ## Getting Started Before running these examples, make sure you have: 1. [Signed up for a Messari API key](https://messari.io/pricing) 2. Installed the Messari SDK in your project: ```bash theme={null} npm install @messari/client ``` For full documentation on the SDK, refer to the [Quickstart guide](/quickstart). ## External Resources For additional examples and source code, check out our [SDK Examples Repository on GitHub](https://github.com/messari/sdk-ts/tree/main/examples). # Methodology and Glossary Source: https://docs.messari.io/glossary/classification-system Detailed descriptions of Messari's classification system and methodologies # Messari Classification System The Messari Classification System is a global standard for categorizing participants in the crypto industry, similar to how GICS functions in traditional finance. It provides a unified taxonomy that groups crypto entities into common sectors, sub-sectors, and tags. ## Overview The Messari Classification System is composed of 4 layers of classifications. ### 1. Entity Type A Messari entity refers to any identifiable participant in the crypto ecosystem. Entity types include: * **Project** (e.g Solana) * **Asset** (e.g. ETH) * **Organization** (e.g. Solana Foundation Labs or Solana Ventures) * **Network** (e.g. Ethereum Network) * **Governing** **Body** (e.g. Uniswap DAO) * **Exchange** (e.g. Binance) * **Person** (e.g. Brian Armstrong) A single project may include multiple entity types. Binance for example has an asset (BNB), multiple organizations linked to it (Binance US, Binance NFT, Binance  Holdings), a network (BSC), an exchange (Binance), a person (Changpeng Zhao). Current classification efforts focus mainly on Projects, Assets, and Organizations, with others to be included over time. ### 2. Sectors Sectors are broad categories used to group entities across all types. * There are 13 sectors total. * An entity can belong to multiple sectors if applicable. * Each sector is divided into sub-sectors. ### 3. Sub-sectors Sub-sectors offer more specific classification within sectors. * There are 124 sub-sectors. * A sub-sector may belong to multiple sectors. Example: “AI Meme” may fall under both AI and Meme sectors. Entities can be assigned to multiple sub-sectors. ### 4. Tags Tags are flexible, descriptive labels for finer classification. * Tags are free-form and not tied to any specific sector. * If an entity only has orphaned tags (not linked to any sector), it will default to the Other sector. Example: An entity with only the tag "Agriculture" will roll up to the Others sector. * If it also has a tag like “Decentralized Lending,” it will roll up to DeFi instead. ## Sectors | **Sectors** | **Sub-sectors** | **Definition** | | :- | :- | :- | | **AI** | AI Infrastructure, AI Agents, Agent Frameworks, AI Consumer, AI Compute, AI Tooling, AI Meme, DeFAI, Other AI | AI in crypto uses artificial intelligence to improve blockchain systems. Includes AI agents for decision-making, apps for trading or analytics, frameworks for building AI tools, launchpads for AI projects, and DeFAI (AI-powered DeFi). Combines AI and blockchain for smarter, automated crypto solutions. | | **Cefi** | Banking, Centralized Custody, ETFs, Hedge Funds, Centralized Insurance, Market Making, On/Off Ramp, OTC, Centralized Payments, Private Equity, Venture Capital, Centralized Asset Managers, Centralized Yield Services, Centralized Incubators and Accelerators, Centralized Exchange, Centralized Lending, Centralized Liquid Staking, Centralized Issuer, Other Centralized Finance | Financial services for cryptocurrencies managed by centralized companies, like banks but for digital assets. Includes exchanges (e.g., Coinbase, Binance), custody, lending, and payments. Offers user-friendly interfaces, customer support, and regulatory compliance, but controls user funds unlike DeFi. | | **DeFi** | Decentralized Lending, Decentralized Exchange, Derivatives, Decentralized Payments, Decentralized Custody, Prediction Markets, Decentralized Insurance, Decentralized Incubators & Accelerators, Decentralized Liquid Staking, Restaking, Decentralized Yield Services, Aggregator, Launchpad and Crowdfunding, Real World Assets, Synthetic Assets, Decentralized Asset Managers, Decentralized Issuer | Financial services on blockchains without middlemen, using smart contracts. Includes decentralized exchanges, lending, staking, derivatives, and new ideas like AI-driven DeFi or tokenized real-world assets. Offers transparent, permissionless finance. | | **Networks** | Layer-0, Layer-1, Layer-2, Layer-3, Interoperability | The infrastructure powering blockchains. Includes Layer-0 (base hardware), Layer-1 (e.g., Bitcoin, Ethereum), and scaling solutions like Layer-2 (rollups, sidechains). Supports faster, secure, and specialized blockchains for various apps, addressing scalability and interoperability. | | **Blockchain Infrastructure** | Client, Hosting, Indexing, Oracles, Validator Operations and Support, Wallets, Mining Operations and Support | Core tech and services that keep blockchains running. Includes node hosting, wallet solutions, oracles (real-world data feeds), and indexing tools. Simplifies development and enhances security, scalability, and usability. | | **DePIN** | DePIN Compute, Wireless Networks, Energy Networks, Robotics, Content Delivery Platform, File Storage, Mobility Networks, Geospatial Networks, Other DePIN | Blockchain-based systems for physical resources like storage, computing, or energy. Users contribute resources (e.g., internet bandwidth) and earn crypto rewards. Creates decentralized, community-driven alternatives to centralized infrastructure. | | **Gaming** | Gaming Platform, Game, Game Tooling, Gaming Infrastructure, Gambling, Gaming Studio, Metaverse, Other Gaming | Blockchain-based gaming projects that bring fun, rewards, and ownership to players. Includes Gaming Platforms for hosting games, individual Games, Game Tooling for development tools, Gambling apps, Gaming Infrastructure for tech support, Gaming Studios for game creation, Metaverse for virtual worlds, Other Gaming for miscellaneous projects. | | **NFTs** | NFT Derivatives, NFT Exchange, NFT Fragmentation, NFT Launchpad, NFT Lending, NFT Oracle, Art, Collectibles and Digital Goods, Fashion, Music, Sports, Other NFT | Digital assets on blockchains representing unique items or collectibles. Includes NFT Derivatives for financial products tied to NFTs, NFT Exchanges for trading, NFT Fragmentation for splitting ownership, NFT Launchpads for new projects, NFT Lending for borrowing against NFTs, NFT Oracles for price data, Art for creative works, Collectibles and Digital Goods for virtual items, Fashion for wearable NFTs, Music for audio NFTs, Sports for fan collectibles, and Other NFT for niche uses. Enables ownership, trading, and creativity in the digital space. | | **Meme** | Frog-Themed Coins, Cat-Themed Coins, Celebrity-Themed Coins, Country-Themed Coin, Dog-Themed Coins, Duck-Themed Coins, Elon Musk-Inspired Coins, Parody Coins, Other Meme | Crypto tokens driven by internet culture, humor, and community trends. Focuses on speculative, fun, and community-driven value. | | **Stablecoins** | Algorithmic Stablecoin, Commodity-Backed Stablecoins, Crypto-Backed Stablecoins, Fiat-backed Stablecoin, Hybrid Stablecoins | Cryptocurrencies pegged to stable assets (e.g., USD, gold) to avoid price swings. Types include fiat-backed, crypto-backed, and algorithmic. Used for trading, payments, and DeFi, offering stability and bridging crypto with traditional finance. | | **Blockchain Services** | Design Services, Security, Legal Services, Marketing Services, Protocol and Governance Services, Software Development Services, Tax Services | Professional support for blockchain projects. Includes design, legal, marketing, software development, and governance services. Helps businesses and startups adopt blockchain by addressing technical and regulatory challenges. | | **Tools** | Block Explorer, Access Control, Analytics, Communication and Messaging, Contribution and Compensation, Developer Tooling, Education, Identity, Reputation, and Credentialing, Domain Name System (DNS), Moderation, News, Onboarding, Market Data, Trading Bots, Research | Services and apps that make blockchains easier to use or build on. Includes block explorers, analytics, trading bots, and identity solutions. Supports the crypto ecosystem by improving access, transparency, and functionality. | | **Others** | | Diverse blockchain projects focused on niches. Includes account abstraction (simpler blockchain interactions), industry applications (e.g., healthcare, real estate), privacy tools, and sustainability projects. | ## Sub-Sectors | **Sub-sector** | **Parent Sector** | **Definition** | | - | - | - | | **Access Control** | Tools | A service or tool developed to facilitate subscription or credential-based participation in a group or community. | | **Agent Frameworks** | AI | Platforms enabling the creation and deployment of autonomous AI agents. They provide tools for developers to build agents that interact with blockchains. | | **Aggregator** | DeFi | A platform that routes optimal financial transactions including trades and yields across external platforms including exchanges. | | **AI Agents** | AI | Autonomous programs leveraging AI to perform tasks like trading or data analysis on blockchain networks. They operate independently, executing smart contracts or optimizing DeFi strategies. | | **AI Compute** | AI | Decentralized networks offering computational power for AI model training and inference. Users share or rent GPU resources, rewarded via tokens. | | **AI Consumer** | AI | Platforms leveraging AI to deliver user-friendly applications, such as intelligent wallets, predictive trading tools, or personalized DeFi dashboards. These solutions enhance accessibility and decision-making for retail users through intuitive interfaces and real-time insights. | | **AI Infrastructure** | AI | Foundational blockchain systems supporting AI operations, like data oracles or scalable compute layers. They ensure secure data feeds and processing for AI applications. | | **AI Meme** | AI | Crypto tokens or projects combining AI themes with meme-driven marketing. They leverage community hype and AI narratives. | | **AI Tooling** | AI | Developer tools and platforms for integrating AI into blockchain ecosystems. These include SDKs, APIs, or model marketplaces for building AI-driven dApps. | | **Algorithmic Stablecoin** | Stablecoins | Stablecoins maintaining pegs through algorithms that adjust supply based on market demand, without direct asset backing. They rely on smart contracts to stabilize value, often with high risk. | | **Analytics** | Tools | Protocols or services which provide insights and analysis on data from networks and applications. | | **Art** | NFTs | Physical or digital creations that are interpreted as creative or convey a sense of meaning. | | **Banking** | CeFi | An aggregator of financial services offered by a banking institution. | | **Block Explorer** | Tools | Web-based tools for querying and visualizing blockchain data, such as transactions, addresses, and blocks. They provide transparent access to network activity and smart contract details. | | **Cat-Themed Coins** | Meme | Meme tokens with cat-inspired themes, tapping into internet cat culture. | | **Celebrity-Themed Coins** | Meme | Tokens tied to celebrities or public figures. | | **Centralized Asset Managers** | CeFi | Firms managing portfolios or funds for clients, offering professional investment strategies. They handle asset allocation, trading, and risk management centrally. | | **Centralized Custody** | CeFi | Services securely storing crypto assets on behalf of users, typically for institutions or high-value accounts. They use security measures like cold storage and multisig. | | **Centralized Exchange** | CeFi | A platform operated by a central authority that facilitates the trading of cryptoassets custodied on the platform. | | **Centralized Incubators and Accelerators** | CeFi | Programs run by centralized entities to fund, mentor, and launch crypto startups or projects. They provide capital, resources, and networks to drive growth. | | **Centralized Insurance** | CeFi | Services providing coverage for assets against hacks, fraud, or platform failures, managed by centralized entities. They offer policies to protect user funds, often integrated with exchanges. | | **Centralized Issuer** | CeFi | A centralized issuer is an entity that has control over the creation and distribution of a particular cryptoasset. | | **Centralized Lending** | CeFi | Platforms where users borrow or lend crypto assets, with the platform managing terms, collateral, and risk. They provide accessible loans or interest-earning opportunities. | | **Centralized Liquid Staking** | CeFi | Services offered by centralized platforms where users stake crypto assets to earn rewards while receiving liquid tokens. The platform manages staking operations, ensuring security and returns. | | **Centralized Payments** | CeFi | Platforms enabling crypto-based or not payments for goods, services, or remittances, processed through centralized systems. | | **Centralized Yield Services** | CeFi | Platforms offering interest or yield on deposits through centralized management, often via lending or investment pools. Users earn passive income without managing complex DeFi protocols. | | **Client** | Blockchain Infrastructure | A software implementation of a specific blockchain and every node on the network runs client software. Public blockchains can have one or many clients that interface with one another to create a distributed, peer-to-peer network. | | **Collectibles and Digital Goods** | NFTs | Physical or non-physical items or tokens that provide the holder unique ownership of digital or real-world items. | | **Commodity-Backed Stablecoins** | Stablecoins | Stablecoins pegged to the value of physical commodities like gold or silver, managed by centralized or decentralized entities. They aim to combine crypto efficiency with tangible asset stability. | | **Communication and Messaging** | Tools | A platform that allows members to share, discuss, and communicate. It can be a forum, messaging application, or social network focused on discussion. | | **Content Delivery Platform** | DePIN | Decentralized systems for streaming or delivering digital content efficiently. Nodes cache and distribute content, reducing latency and costs. | | **Contribution and Compensation** | Tools | A service or tool that allows for the accounting of work or effort done by community members and the facilitation of compensation of community members. | | **Country-Themed Coin** | Meme | Memecoins themed around a specific country, often created as a playful tribute to national identity, culture, or a viral trend associated with a nation. | | **Crypto-Backed Stablecoins** | Stablecoins | Stablecoins overcollateralized by cryptocurrencies like ETH or BTC, typically managed by decentralized protocols. Users lock crypto in smart contracts to mint stable tokens. | | **Decentralized Asset Managers** | DeFi | DAOs or protocols managing crypto portfolios, optimizing yield, or trading via community governance or algorithms. They offer transparent, user-controlled investment strategies. | | **Decentralized Custody** | DeFi | Blockchain-based solutions for secure asset storage without centralized intermediaries, using smart contracts or multisig. They ensure user control and transparency for institutional or retail funds. | | **Decentralized Exchange** | DeFi | A platform for the trading of cryptoassets without a centralized intermediary. | | **Decentralized Incubators & Accelerators** | DeFi | Community-driven programs funding and mentoring DeFi or blockchain startups via DAOs or token incentives. They democratize access to capital and resources. | | **Decentralized Insurance** | DeFi | Protocols offering coverage for smart contract failures, hacks, or DeFi risks using pooled funds and decentralized governance. Users stake tokens to underwrite or purchase policies. | | **Decentralized Issuer** | DeFi | A protocol that autonomously manages the issuance of a cryptocurrency without a centralized entity. | | **Decentralized Lending** | DeFi | Peer-to-peer lending platforms on blockchain, using smart contracts to manage loans and collateral without intermediaries. Users borrow or lend crypto with transparent terms. | | **Decentralized Liquid Staking** | DeFi | DeFi protocols allowing users to stake assets in PoS networks while receiving liquid tokens for use elsewhere. They enhance capital efficiency via decentralized governance. | | **Decentralized Payments** | DeFi | Blockchain-based systems enabling fast, low-cost crypto transactions for remittances or commerce without centralized processors. They prioritize user control and global access. | | **Decentralized Yield Services** | DeFi | DeFi platforms aggregating opportunities for earning yield on crypto assets through staking, lending, or liquidity provision. They optimize returns via automated strategies. | | **DeFAI** | AI | Decentralized finance protocols enhanced by AI for yield optimization, risk management, or automated trading. AI algorithms improve efficiency and decision-making in DeFi. | | **DePIN Compute** | DePIN | Decentralized networks providing computational resources for tasks like AI training or data processing. Users share or rent processing power via blockchain-based platforms. | | **Derivatives** | DeFi | A financial instrument which is created from an underlying asset and derives its value from it. | | **Design Services** | Blockchain Services | Services focused on design elements of a website or protocol, including but not limited to product design, graphic design, web design, and iconography. | | **Developer Tooling** | Tools | Tooling developed to support and aid developers or the development cycle of applications, protocols, and networks | | **Dog-Themed Coins** | Meme | Memecoins that revolve around dog-based themes, often inspired by popular internet memes, typically created as jokes or community-focused tokens. | | **Domain Name System (DNS)** | Tools | A naming system that translates domain names into Internet Protocol (IP) addresses that are used to communicate over the Internet. | | **Duck-Themed Coins** | Meme | Meme tokens centered around duck-related imagery or humor. | | **Education** | Tools | Entities and Services that provide resources and instruction on knowledge-based subjects. | | **Elon Musk-Inspired Coins** | Meme | Meme tokens inspired by Elon Musk’s persona, tweets, or ventures. | | **Energy Networks** | DePIN | Networks that aggregate distributed energy resources, including energy generation and storage units, to create a more resilient and efficient energy grid. | | **ETFs** | CeFi | Exchange Traded Fund. | | **Fashion** | NFTs | Physical or digital clothing designed to have some sort of artistic quality. | | **Fiat-backed Stablecoin** | Stablecoins | Stablecoins pegged to fiat currencies like USD, backed by reserves held by centralized custodians. They offer stability through direct 1:1 collateralization and audits. | | **File Storage** | DePIN | A platform or protocol designed for long-term, immutable file storage, such as Arweave and Filecoin. | | **Frog-Themed Coins** | Meme | Meme coins featuring frog mascots, popularized by Pepe the Frog, with strong community and meme culture ties. | | **Gambling** | Gaming | Refers to platforms and companies focused on online or blockchain-based gambling activities. This includes casinos, betting, slot machines, poker, blackjack, roulette, bingo, lottery, odds-making, and bookmaker services. It also covers a range of wagering activities such as horse racing, dice games, and jackpot systems. | | **Game** | Gaming | A single gaming title developed and released as an individual product. This refers to a standalone game rather than a broader platform or series | | **Game Tooling** | Gaming | Developer tools and platforms for creating blockchain games, including SDKs, APIs, or asset marketplaces. They simplify integration of crypto, NFTs, and DeFi into games. | | **Gaming Infrastructure** | Gaming | Blockchain networks or layer-2 solutions optimized for gaming, offering scalability, low-cost transactions, and NFT support. They power game economies and player interactions. | | **Gaming NFTs** | Gaming | Non-fungible tokens representing in-game assets like characters, items, or land in blockchain games. They enable true ownership, interoperability, and trading across platforms. | | **Gaming Platform** | Gaming | Companies that develop gaming-related products and services that are not games themselves. This includes infrastructure, aggregators, marketplaces, trackers, tools, and services with a focus on gaming. Examples include platforms that showcase or aggregate Web3 games, game development platforms, marketplaces for gaming assets, gaming-focused blockchain layers, and services related to e-sports and competitive gaming. | | **Gaming Studio** | Gaming | Companies that focus on the development or publishing of video games. This category includes entities that design, build, and release games, as well as those that manage the distribution and promotion of games. Companies classified under this tag typically have multiple games in their portfolio or present themselves as dedicated to producing a range of games, even if they are currently working on a single title. | | **Geospatial Networks** | DePIN | Decentralized systems collecting and sharing location-based data. Nodes contribute geospatial insights, rewarded via tokens. | | **Hedge Funds** | CeFi | A private alternative investment vehicle that pools funds from accredited investors to invest in complex trading strategies to generate outsized returns. | | **Hosting** | Blockchain Infrastructure | A protocol that facilitates and executes remote client requests on networks. Transactions from users on blockchains are routed through RPC nodes, and RPC calls allow for blockchain data to be queried. | | **Hybrid Stablecoins** | Stablecoins | Stablecoins combining multiple backing mechanisms, such as fiat, crypto, or algorithmic methods, to enhance stability and flexibility. They balance risk and liquidity through diversified reserves or dynamic protocols. | | **Identity, Reputation, and Credentialing** | Tools | Protocols that provide unique digital identities or link immutable records of identification to the digital world. | | **Indexing** | Blockchain Infrastructure | Protocols and services that extract data from blockchains for generalized or specific use cases. | | **Interoperability** | Networks | Protocols enabling communication and asset transfer between different blockchains, enhancing ecosystem connectivity. They bridge disparate networks via cross-chain messaging or token swaps. | | **Launchpad and Crowdfunding** | DeFi | A platform that facilitates the collection of capital to fund a business or initiative, which may result in shareholders receiving equity, crypto assets, or some other financial instrument. | | **Layer-0** | Networks | Cosmos and Polkadot are the go-to examples of Layer 0 blockchains. Layer 0 blockchains are meant to provide the underlying infrastructure to facilitate the creation of blockchains and also allow cross-chain interoperability. | | **Layer-1** | Networks | A Layer-1 blockchain refers to generalized smart contract networks that provide security for applications and scaling solutions built on top of the network. | | **Layer-2** | Networks | Scaling solutions operating atop layer-1 blockchains, designed to increase the transaction throughput of a blockchain while inheriting security properties of the underlying network. | | **Layer-3** | Networks | Protocols built atop layer-2 solutions, often for specialized applications like privacy, gaming, or cross-chain interactions. They aim to further optimize scalability or functionality. | | **Legal Services** | Blockchain Services | Services focused on legal or legal advisory. | | **Market Data** | Tools | Services aggregating real-time and historical data on crypto prices, volumes, and market metrics across blockchains and exchanges. They enable traders and analysts to monitor trends and make informed decisions. | | **Market Making** | CeFi | An entity that provides liquidity to financial markets through buying and selling assets. | | **Marketing Services** | Blockchain Services | Services provided by an external agent to support the creation of a brand, create marketing collateral, or act on behalf of an entity to promote an application, protocol, or entity. | | **Metaverse** | Gaming | Refers to immersive and virtual 2D or 3D worlds where users can congregate and interact with one other online. | | **Mining Operations and Support** | Blockchain Infrastructure | Onchain and offchain entities that facilitate or support miners and mining operations of a cryptocurrency network. | | **Mobility Networks** | DePIN | Decentralized platforms for managing transportation or logistics data. They enable peer-to-peer ride-sharing or vehicle coordination. | | **Moderation** | Tools | A tool or service which allows for the enforcement of standards and rules in communication channels. | | **News** | Tools | The reporting or announcement of recent information that is deemed relevant or important. | | **NFT Derivatives** | NFTs | Financial instruments tied to NFT values, such as options or futures, enabling speculation or hedging. They rely on oracles for accurate pricing and are emerging in DeFi. Projects. | | **NFT Exchange** | NFTs | A marketplace where users can buy, sell, or trade non-fungible tokens (NFTs). | | **NFT Fragmentation** | NFTs | Platforms consolidating NFT listings from multiple marketplaces for easier browsing, comparison, and trading. | | **NFT Launchpad** | NFTs | Platforms facilitating the creation, minting, and initial sale of NFT projects, often with marketing and community support. They help creators launch collections while attracting early investors. | | **NFT Lending** | NFTs | DeFi protocols allowing users to borrow against NFTs as collateral or lend to earn interest. They unlock liquidity for NFT holders while managing valuation risks via oracles. | | **NFT Oracle** | NFTs | Mechanisms delivering external data, like price valuations, to blockchain networks for NFT-based applications. They address the challenge of accurate pricing for illiquid NFTs in DeFi, lending, or derivatives. | | **On/Off Ramp** | CeFi | Refers to platforms and services that facilitate the conversion between fiat currency and cryptocurrencies. This includes fiat solutions, credit card and payment system integrations, and other tools that allow users to seamlessly move funds in and out of the crypto ecosystem. | | **Onboarding** | Tools | A platform or tool designed to induct new users or employees into groups or communities. | | **Oracles** | Blockchain Infrastructure | Protocols that verify claims regarding external, on-chain, or off-chain data and information for smart contracts to obtain the inputs needed to execute their instructions. | | **OTC** | CeFi | Centralized platforms facilitating large crypto trades directly between parties, bypassing public exchanges. They offer privacy, price stability, and high liquidity for institutional or high-net-worth clients. | | **Other AI** | AI | Niche or emerging AI-crypto projects not fitting standard subsectors. | | **Other Centralized Finance** | CeFi | Niche centralized financial services in crypto, such as bespoke wealth management or specialized trading tools. Includes emerging platforms not fitting standard categories. | | **Other DePIN** | DePIN | Emerging or niche decentralized physical infrastructure networks. | | **Other Gaming** | Gaming | Niche or emerging blockchain gaming categories, such as puzzle games, simulations, or experimental formats. They explore unique mechanics or crypto integrations. | | **Other Meme** | Meme | Meme coins not fitting specific themes, encompassing a wide range of humorous, absurd, or niche cultural references. | | **Other NFT** | NFTs | Niche or experimental NFT applications, such as virtual real estate, music royalties, or tokenized identities. They explore diverse use cases beyond art or collectibles. | | **Parody Coins** | Meme | Memecoins created as a humorous or satirical imitation of an existing person or entity. | | **Prediction Markets** | DeFi | Decentralized platforms for betting on real-world outcomes (elections, sports) using crypto, with prices reflecting probabilities. They incentivize accurate forecasting via token rewards. | | **Private Equity** | CeFi | An investment management firm that invests in the equity of private companies. In addition to funding, a private equity firm provides operational and industry guidance to improve the performance of the company it invested in. | | **Protocol and Governance Services** | Blockchain Services | Advisory or technical services provided to a protocol or DAO including governance recommendations, risk analysis, and monitoring. | | **Real World Assets** | DeFi | Physical assets that are tokenized onchain to denote virtual ownership. | | **Research** | Tools | Platforms or services offering in-depth analysis, reports, and insights on blockchain projects, markets, and trends. | | **Restaking** | DeFi | Platforms or protocols that enable users to stake their already staked tokens across multiple networks or protocols. These services enhance the utility of staked tokens by allowing them to earn rewards or participate in governance across different protocols, optimizing the efficiency of capital deployment. | | **Robotics** | DePIN | Decentralized networks coordinating autonomous robots for tasks like delivery, agriculture, or industrial automation. Blockchain-based protocols enable secure data sharing, task allocation, and incentivization through tokens. | | **Security** | Blockchain Services | Services, Protocols, and applications developed to secure assets and protocols. | | **Software Development Services** | Blockchain Services | Services provided by an external agent to support the development of software for an application, protocol, or network. | | **Sports** | NFTs | Includes sports games, events, merchandise, and equipment of professional and amateur sports leagues. | | **Synthetic Assets** | DeFi | DeFi protocols creating tokens that track the value of real-world assets (stocks, commodities) without direct ownership. They enable exposure to diverse markets via blockchain. | | **Tax Services** | Blockchain Services | Services provided by an external agent to provide analysis and recommendations on activities in regard to their tax implications or mitigations. | | **Trading Bots** | Tools | Automated software executing crypto trades based on predefined strategies, market signals, or algorithms. They operate on exchanges via APIs, aiming to optimize profits or reduce manual effort. | | **Validator Operations and Support** | Blockchain Infrastructure | Onchain and offchain entities that facilitate or support validators and validator operations of cryptocurrency networks | | **Venture Capital** | CeFi | An investment firm that invests in early-stage startups and entrepreneurs with high growth potential. | | **Wallets** | Blockchain Infrastructure | An application that controls access to their funds by managing keys and addresses, tracking balances, and creating and signing transactions | | **Wireless Networks** | DePIN | Peer-to-peer wireless connectivity solutions bypassing traditional telecom providers. Nodes share Wi-Fi or cellular signals, rewarded via tokens. | ## Tags | **Tag** | **Defintion** | | - | - | | **Advertising** | Companies and platforms focused on advertising, promotion, and public relations, utilizing blockchain technology. This includes ad technology, video ads, influencer marketing, in-game ads, mobile advertising, and services provided by ad publishers. | | **Agriculture** | Blockchain-based platforms and companies focused on the agriculture industry. This includes agriculture management platforms, agri-tech solutions, agriculture marketplaces, weather information services, verification systems, and agricultural supply chain tracking. | | **AI Launchpad** | Platform that integrates AI technologies into the process of launching new blockchain projects and tokens. | | **Application Specific Chain** | A blockchain built for a specific use case or application. Application-specific chains are not intended for general-purpose use and instead are tailored to a specific application to optimize performance, improve security, and create a better user experience for the intended use case. | | **Automated Market Maker (AMM)** | An Automated Market Maker (AMM) is a type of decentralized exchange protocol that pools user funds and utilizes mathematical formulas to price assets without an order book. | | **Bitcoin Layer-2** | Refers to protocols or solutions built on top of the Bitcoin network to enhance scalability, speed, and efficiency. Often called Layer 2 or L2, these solutions (such as the Lightning Network) allow transactions to occur off-chain while maintaining the security and decentralization of Bitcoin. | | **Blockchain API** | Interfaces allowing developers to interact with blockchain networks for building dApps or integrating crypto features. They provide access to data, transactions, and smart contracts. | | **BRC20** | Token standard on the Bitcoin blockchain enabling fungible and non-fungible tokens via the Ordinals protocol. It attaches JSON data to satoshis for NFT creation, supporting use cases like collectibles. | | **BTCfi** | DeFi ecosystems built on Bitcoin or its layers (e.g., Lightning, Stacks) for lending, trading, or yield generation. They bring DeFi functionality to BTC without wrapping it. | | **Carbon Credits** | Platforms and companies involved in the carbon market and carbon offset ecosystem. This includes carbon offset trading, carbon finance, carbon-free energy matching, carbon NFTs, climate actions aimed at neutralizing carbon emissions, carbon removal, decarbonization services, and education or events related to carbon credits. | | **Card Games** | Blockchain-powered card games where cards are NFTs, enabling ownership, trading, or staking for rewards. They combine strategy with decentralized economies. | | **Centralized Liquid Staking Tokens** | Tokens issued by centralized platforms representing staked assets, allowing users to trade or use them while earning staking rewards. These tokens provide liquidity without unstaking, managed by centralized custodians. | | **Charity** | Blockchain-based platforms that facilitate donations, aid, or other charitable contributions. These platforms leverage blockchain technology to provide transparency, traceability, and efficiency in charitable giving or aid distribution. | | **Cosmos SDK** | A blockchain built with the Cosmos SDK that is compatible with the IBC protocol. | | **Data Availability** | Data availability in blockchain networks refers to ensuring all transaction data is accessible to nodes for validation and verification. It prevents data withholding, supports network security, and enables scalability solutions like rollups by confirming data is publicly available, maintaining decentralization and trustlessness within the ecosystem. | | **Decentralized Liquid Staking Tokens** | Tokens representing staked assets in DeFi protocols, tradable for liquidity while earning staking rewards. They’re managed by decentralized networks, not custodians. | | **DeSci** | DeSci, or Decentralized Science, is a movement that leverages blockchain technology and related tools-such as tokens, NFTs, smart contracts, and DAOs to make scientific research more open, transparent, and community-driven. The goal is to address the limitations of traditional scientific research, which is often hampered by centralization, restricted access, slow funding, and limited collaboration. | | **Ethereum Layer-2** | A secondary architecture or protocol specifically designed to increase transaction speed and scalability while deriving some or all of its security or decentralization properties of Ethereum. Rollups, validiums, and volitions can all be considered Layer-2 projects. | | **Euro Stablecoin** | A cryptoasset designed to trade at the same price as the Euro. | | **Exchange Token** | An Exchange Token is a token issued by an exchange, primarily designed to provide utility within that exchange’s ecosystem. These tokens are typically used to reduce trading fees for users who hold or use them. | | **Fan Token** | A cryptoasset that provides benefits to fans of a sports team, music artist, or other entity with exclusive content or merchandise. | | **Hardware Wallet** | Physical devices designed to securely store private keys offline, protecting crypto assets from hacks. They support signing transactions in a secure environment. | | **Healthcare** | Blockchain-based platforms and companies focused on healthcare-related solutions. This includes areas such as longevity, medicine, clinical trials, pharmaceuticals, telemedicine, health and patient data management, genetic testing, and prescription services. These platforms aim to improve healthcare delivery, data security, and patient outcomes through decentralized technologies. | | **Indexes** | An entity or platform that facilitates the creation of baskets of assets grouped together by a predefined composition and methodology. | | **InfoFi** | InfoFi refers to a category of applications that create tradable markets for exotic, non price signals, such as mindshare, reputation, and quantitative metrics. These platforms enable users to speculate on intangible information, supporting discovery and valuation of new data types through financial market activity rather than traditional price movements. | | **Intent** | DeFi systems using intent-based architectures where users specify desired outcomes (e.g., trades) and solvers execute optimal paths. They improve efficiency and reduce user complexity in transactions. | | **Logistics** | Blockchain-based protocols and platforms that aim to improve supply chain management and logistics by providing transparency, immutability, and real-time tracking of goods and services. | | **LRTfi** | DeFi platforms leveraging liquid restaking tokens to enable yield farming, lending, or trading of restaked assets. Users gain liquidity while earning staking rewards from protocols. | | **LST-Fi** | An application that integrates liquid staking tokens with financial services such as lending, stablecoin protocols, decentralized exchanges, interest rate swaps, and other platforms, to unlock additional value and enhance the utility of liquid staking tokens. | | **MEV** | Platforms, services, or tools that focus on mitigating, providing research, data or capitalizing on Miner Extractable Value. These include protocols that help reduce the potential for front-running or other manipulative practices by validators, as well as those that enable users to capture MEV through arbitrage opportunities. | | **Multiparty Computation** | Cryptographic protocols enabling secure, private computations across multiple parties without revealing sensitive data. In blockchain, they enhance wallet security and private transactions. | | **Multisig Wallet** | Wallets requiring multiple private key signatures to authorize transactions, enhancing security for shared accounts. They’re used by DAOs, teams, or high-value accounts. | | **Music** | Entities or protocols that facilitate the creation, distribution, or sale of music. | | **NFTFI** | DeFi protocols integrating NFTs as collateral for loans, liquidity pools, or yield generation. Users can borrow against or fractionalize NFTs to unlock value. | | **Optimistic (Fraud Proofs)** | A network or protocol that leverages fraud proofs for scaling. | | **Options** | Refers to cryptocurrency option protocols and exchanges that offer options trading. These platforms allow users to trade options contracts, providing the flexibility to speculate, hedge, or manage risk by purchasing or selling the right to buy or sell cryptocurrencies at a predetermined price within a specified timeframe. | | **Ordinals** | Refers to the BRC-20 token standard on the Bitcoin network, enabling the creation and management of fungible tokens using Bitcoin’s ordinal inscriptions. This category also includes ordinal-focused projects, such as ordinal marketplaces and tools that facilitate the trading, creation, or management of ordinal inscriptions. | | **Parachain** | A blockchain built with the Substrate framework that leases security from the Polkadot or Kusama relay chains. | | **Perpetuals** | Refers to platforms and services that facilitate perpetual trading, including perpetual swaps and aggregators. These platforms enable users to trade perpetual contracts without expiration dates, allowing for continuous positions in cryptocurrency markets. | | **Privacy** | A protocol that obscures transaction details such as sender, receiver, or amount, to protect user data and ensure anonymity on a blockchain-based network. | | **Racing Games** | Blockchain-based games centered on competitive racing, often integrating crypto rewards or NFT-based vehicles. Players earn tokens through races or trade unique in-game assets. | | **Real Estate** | Companies and protocols focused on tokenizing real estate assets, providing users with the ability to buy, sell, or invest in fractional shares of properties via blockchain technology. | | **Rollup** | Layer-2 scaling solutions that bundle (or “roll up”) transactions off-chain and settle them on a layer-1 blockchain. They reduce costs and congestion while inheriting mainnet security. | | **Runes** | A Bitcoin-based protocol for creating fungible and non-fungible tokens, simplifying token issuance compared to BRC-20. It leverages Bitcoin’s UTXO model for token management. | | **SEC Alleged Securities** | A cryptoasset that the Securities and Exchange Commission (SEC) of the United States alleges is a security. | | **Settlement Layer** | Blockchain networks serving as the final ledger for transaction settlement, ensuring security and immutability. They anchor other layers or chains, processing high-value or batched transactions. | | **Shared Sequencer** | A shared sequencer is a decentralized network of nodes that provides transaction ordering and block creation services for multiple layer-2 rollups or blockchains simultaneously. Unlike a centralized sequencer, which is a single entity controlling transaction order for a specific rollup, a shared sequencer allows different rollups to outsource their sequencing needs to a common, permissionless network. | | **Shooting Games** | Decentralized shooter games leveraging blockchain for tokenized weapons, skins, or rewards. Players engage in PvP or PvE modes, earning crypto or NFTs. | | **SideChain** | A sidechain is a separate, independent blockchain that is connected to a main blockchain (often called the "mainchain" or "parent blockchain") enabling faster or specialized transactions with periodic settlement to the mainnet. This setup allows digital assets (such as tokens or coins) to be transferred back and forth between the mainchain and the sidechain without changing the underlying value of the assets. | | **Social Media** | Protocols and applications that facilitate the exchange of information and creation of and distribution of content between users through the internet or blockchain-based technology. | | **Social Tokens** | Tokens issued by individuals, communities, or platforms that provide the token holder unique benefits or access to holders, including status, potential financial reward, or Governance rights of a DAO. | | **Social Trading** | Social trading is an investment approach where individuals use online platforms to observe, interact with, and often directly copy the trading strategies of more experienced or successful cryptocurrency traders. | | **Stableswap** | An exchange designed to efficiently swap between stablecoins with low slippage and minimal price impact. | | **Ticketing** | NFTs used as secure, verifiable digital tickets for events, preventing fraud and enabling secondary markets. They can include perks like VIP access or collectible metadata. | | **Travel and Hospitality** | Blockchain-based platforms and services within the travel and hospitality industry. This includes travel agencies, hotel services, travel identity solutions, travel infrastructure, services for digital/Web3 nomads, and platforms for bookings such as flights and accommodations. | | **U.S. Dollar Stablecoin** | A cryptoasset designed to trade at the same price as the U.S. Dollar. | | **Undercollateralized Lending** | DeFi protocols offering loans with minimal or no collateral, relying on credit scoring, reputation, or off-chain data. They expand access to borrowing but carry higher risk for lenders. | | **Validium** | A validium is a layer 2 scaling solution for blockchains like Ethereum that processes transactions off-chain to increase throughput and reduce costs. It uses validity proofs, such as zero-knowledge proofs (ZK-SNARKs or ZK-STARKs) to ensure the correctness of off-chain transactions, but unlike ZK-rollups, validiums store transaction data off-chain rather than on the main blockchain. | | **Web Wallets** | Browser-based or cloud-hosted wallets for storing and managing crypto assets. They offer user-friendly interfaces for transactions and DeFi interactions, often custodial or non-custodial. | | **X-to-Earn (Play, Move, Drive, Tap, etc)** | Games rewarding players with tokens for actions like playing, exercising, driving, or tapping, often tied to real-world activities. They incentivize engagement through crypto economies. | | **Yield Aggregator** | A protocol or service that automatically optimizes funds in DeFi on behalf of users to maximize potential returns. | | **Zero Knowledge (Validity Proofs)** | A network or protocol that leverages zero-knowledge cryptography, such as validity proofs, for scaling or privacy. | # Asset Metrics and Definitions Source: https://docs.messari.io/glossary/data-metrics/asset-metrics-definitions Explanations of the available metrics and definitions for assets listed on Messari. The metrics below are available on [Project Pages](https://messari.io/project/ethereum/charts/market) in the Messari Terminal. # Markets | Metric Category | Definition | | :- | :- | | Price | The price metrics refer to the asset's recent trading price. The price is calculated using a VWAP across the exchanges included in the Messari Real Volume Methodology. The 1H & 24H ranges refer to the low and high price of the asset over those timeframes. | | Volume | Real Volume is the trading volume of the asset over the selected timeframe from the exchanges Messari includes in its Real Volume methodology. Reported Volume is the trading volume of the asset over the selected timeframe from all exchanges covered by Messari. | | ROI By Year | The ROI By Year metrics provide the raw percentage return on the asset from the beginning of the year to the end. | | Risk Metrics | The Sharpe ratio (also known as the Sharpe index) measures the performance of an investment compared to a risk-free asset, after adjusting for its risk. Volatility is measured by calculating the standard deviation of the daily returns over a given period of time. Both are available on different timeframes (30 days, 90 days, 1 year, 3 years). | | Market Cap | There exist different ways to calculate Marketcap for cryptoassets. Reported Marketcap is calculated using the circulating supply commonly reported in the industry. Liquid Marketcap is calculated using the supply that exists on-chain, and which is not known to be encumbered by any contracts (programmatic or legal). Outstanding Marketcap is calculated using the entirety of the supply that exists on-chain. Realized Marketcap is defined as the sum of USD value based on the USD closing price on the day that a native unit last moved. Projected Marketcaps (Y+10, Y2050) is defined as the Marketcap accounting for known issuance X years into the future. Altogether, these metrics allow us to have a precise picture of the asset capitalization. | | Return on Investment | ROI metrics refer to the price performance (ROI) of the asset over different timeframes, against the selected currency, sector, or tag. This allows us to compare the performance of the asset against USD, but also against the average DeFi ecosystem for example. | | All-time Highs & Cycle Lows | The All-Time-High ('ATH') trading price for an asset, in USD is computed using the highest hourly open. Cycle Low is the lowest trading price (in USD) of the asset since its All-Time-High | # Supply | Metric Category | Definition | | :- | :- | | Current Supply | There exist different ways to measure Supply for cryptoassets. Reported Supply refers to the circulating supply commonly reported in the industry. Liquid Supply refers to the supply that exists onchain, and which is not known to be encumbered by any contracts (programmatic or legal). Outstanding Supply refers to the entirety of the supply that exists on-chain. Altogether, these metrics allow us to have a precise picture of the Supply of an asset | | Active Supply | Active supply is defined as the sum of unique native units that transacted at least once in the trailing X years/months/days. Native units that transacted more than once are only counted once. | | Issuance & Inflation | Issuance and Inflation metrics both measure how the supply of an asset will evolve in the future. Issuance metrics are calculated based on the current outstanding supply and the number of coins that will be issued onchain. The Annual Inflation Rate, when available, is calculated by taking the projected 12-month increase in Liquid Supply and dividing it by the Liquid Supply today. Projected Supply metrics (Y+10, Y2050), when available, represent the liquid supply of an asset accounting for known issuance X years into the future. Altogether, these metrics give a good estimate of dilution that an investor will likely suffer in the future. | | Supply Distribution | Supply distribution is defined as the distribution of total supply across wallets grouped by amount held. | # Mining | Metric Category | Definition | | :- | :- | | Miner Hashrate | Hashrate is the mean rate at which miners are solving hashes. The miner revenue per hash metric refers to the miner reward per estimated hash unit performed during the period, also known as hash price. | | Miner Difficulty | The average difficulty of finding a hash that meets the protocol-designated requirement (i.e., the difficulty of finding a new block) that interval. The requirement is unique to each applicable cryptocurrency protocol. | # Addresses | Metric Category | Definition | | :- | :- | | Address Distribution | This is the sum of all native units being held in addresses whose balance was at least one in X of the current supply, or greater than X USD / Native units, or in the Top X addresses, at the end of the day. Only native units are considered (e.g., an address with less than X ETH but with more than X in ERC-20 tokens would not be considered). Data sourced from coinmetrics.io. | | Active Addresses | The sum count of unique addresses that were active in the network (either as a destination or source of a ledger change) that day. All parties in a ledger change action (source and destination) are counted. Individual addresses are not double-counted if previously active. Data Provided by Coinmetrics. | # Exchange Flows | Metric Category | Definition | | :- | :- | | Exchange Net Flows | This is the net flow (supply received minus supply sent) for a given exchange in a given timeframe. It can be denominated in USD or Native Units. Data sourced from Coinmetrics. | | Exchange Withdrawals | This is the sum withdrawn from exchanges that day, including or excluding exchange-to-exchange activity. It can be denominated in USD or Native Units. Data sourced from Coinmetrics. | | Exchange Deposits | This is the sum deposited to exchanges that day, including or excluding exchange-to-exchange activity. It can be denominated in USD or Native Units. Data sourced from Coinmetrics. | | Exchange Supplies | The sum of all native units held in hot or cold exchange wallets that day. It can be denominated in USD or Native Units. Data sourced from Coinmetrics. | # Fees and Revenue | Metric Category | Definition | | :- | :- | | Fees | Various metrics about fees paid to miners, transaction validators, stakers, and/or block producers over the selected timeframe. They can be denominated in USD or Native Units. Data sourced from Coinmetrics. | | Revenue | This is the value of all miner revenue, which constitutes fees plus newly issued native units, represented either as the US dollar amount earned if all native units were sold at the closing price on the same day, or in native units. Data sourced from coimetrics.io. | | Gas | Gas refers to the unit that measures the amount of computational effort required to execute specific operations on the network. Data sourced from coinmetrics.io. | # Network Activity | Metric Category | Definition | | :- | :- | | Transactions | Transaction data sourced from coinmetrics.io. | | Blocks | Various metrics on blocks sourced from coinmetrics.io | | Contracts | Various metrics on contracts sourced from coinmetrics.io. | # Miscellaneous | Metric Category | Definition | | :- | :- | | Developer Activity | Developer Activity Metrics are sourced from Github. Note that there are often many repositories associated with a given asset or project, but Github stats shown here are pulled from what we consider the 'primary' repository for an asset. Occasionally it's not straightforward to determine which repository should be considered the primary one (or the project/asset is such that there just isn't a primary repo). In such cases, we select the repo that most closely defines the unique aspects of the project. This is usually a repo that defines the core node client for the asset, or a set of smart contracts. | # Messari Market Data Service Source: https://docs.messari.io/glossary/data-metrics/market-data-service # Goals Messari’s Market Data Service has three main goals. In order of importance, they are: 1. **Provide the most accurate price and volume data.** Market data is an essential piece of understanding this industry, and we want to provide the best and most reliable tools for users to do so. 2. **Ensure wide coverage across the breadth of assets in the industry.** If there’s an asset of interest in crypto, we want to have price and volume data on it - preferably from genesis. 3. **Minimize latencies.** In addition to an extremely deep set of historical market data, Messari also offers live prices and price alerts. Timely updates to our pricing data is essential to keep these features useful. # Coverage: Spot and Derivatives Messari’s Market Data considers Spot price and volume data across major Centralized, as well as Decentralized, Exchanges. Our methodology for creating prices is detailed below. We also support the following Derivatives datasets: 1. **Open Interest** 1. Aggregated by Asset or Exchange 2. **Volume** 1. Aggregated by Asset or Exchange 3. **Funding Rates** (weighted by Open Interest as well as by Volume) 1. Aggregated by Asset These metrics are grouped at either the asset level and/or the exchange level and are served as a timeseries with hourly or daily granularity. For example, Open Interest can be queried for Bitcoin or for Binance and would return the total OI for BTC across all exchanges or the total OI for Binance across all assets. Our Derivatives coverage considers the following exchanges: * Binance * Bitget * Bullish * Bybit * Coinbase * CrossTower * Crypto.com * FTX * OKX # Definitions **OHLCV object:** A data structure that is comprised of five datapoints (Open, High, Low, Close, Volume) for a specific asset over a given timeframe, all of which are stored as floating point numbers. **DEX:** A Decentralized Exchange operated autonomously on a blockchain, typically via smart contracts and liquidity pools. Examples: Uniswap, Raydium, Curve, etc. **CEX:** Exchanges operated as centralized entities, such as corporations. Typically traded through traditional order books. Examples: Coinbase, Binance, etc. **Market Level:** A price based on particular quote pair at a specific exchange. For example, BTC/USD on Binance would be a separate market from BTC/USD on Kraken. **Asset Level:** An aggregated price for an asset that is inclusive of all the markets that it is traded in. At Messari, all Asset Level prices are denominated in USD. In the example above, the BTC price would be an Asset Level price and would be comprised of many Market Level prices. **Graph Structure:** A non-linear data structure consisting of a set of vertices and a set of edges (also called nodes and lines). Vertices are the fundamental units of a graph, and edges are drawn to connect nodes. **VWAP:** Volume Weighted Average Price. At Messari, the VWAP calculation process is a simple weighted arithmetic mean calculated once each for the Open, High, Low, and Close values. **Market Cap (Market Capitalization):** Total value of all tokens in circulation, calculated by multiplying the current token price by its circulating supply. It provides a snapshot of current valuation and is widely used to perform relative analysis. **FDV (Fully Diluted Value):** The theoretical market cap if all tokens were in circulation at the current token price. Calculated by multiplying the price by its total supply. In cases of missing total supply, max supply is used instead. **Circulating Supply:** Number of tokens currently available and actively circulating in the market. This number excludes locked tokens, tokens held by teams on vesting schedules, or tokens that have been burned. It reflects the tradable supply and provides an accurate picture of a token’s current availability. **Max Supply:** The maximum number of tokens that will ever exist for a token, typically set at launch. Many tokens do not have a maximum supply. **Total Supply:** The total number of tokens that currently exist, including both circulating and non-circulating tokens. This number excludes burned tokens. It reflects the total supply and provides a view into a token’s future availability. # Spot Datasets and Outputs Messari produces three price and volume datasets as OHLCV timeseries that are continuously updated to live instances of [https://messari.io](https://messari.io/), as well as over the [API](https://docs.messari.io/reference/authentication). These are: 1. Market Level denominated in the quote asset (ex: AAVE/WETH on Uniswap v2 on ETH L1) 2. Market Level denominated in USD (ex: AAVE/WETH → AAVE/USD on Uniswap v2 on ETH L1) 3. Asset Level denominated in USD (ex: AAVE/USD) All three datasets are computed and stored in 1-minute granularity, and are also stored at downsampled 5-minute, 15-minute, 30-minute, 60-minute, 6-hour, 24-hour, and 7-day granularities. Data at the 5-minute granularity and above is made available to customers over the API. # Methodology At a high level, Messari gives one volume-weighted price denominated in USD for every token that we support. This price is inclusive of every trusted market that it trades in, regardless of the quoted asset for the pair. For example, to calculate the price for ETH, we consider the price of ETH on markets where it is the Base Asset (ex. ETH/USD, ETH/BTC), as well as markets where it is the quote (ex: RPL/ETH). In order to do this in a useful way, we ingest raw trade data from a variety of sources on a continuous (24/7) basis. We then transform this raw data into time-series data sets that accurately reflect the USD-denominated value of each asset at any given time. The full methodology is explained below. There are many challenges to doing this accurately: 1. **Preponderance of non-fiat pairs.** One fundamental problem in denominating crypto markets in USD is that many markets do not trade directly with USD or any fiat currency, particularly on decentralized exchanges. Since the volume and price data from these pairs must still be part of the final price emission, we need a way to convert these to USD on-the-fly in an accurate and reliable way. 2. **Multiple venue types.** Decentralized exchanges can trade differently and pose a unique set of challenges compared to traditional order book exchanges. For example, the same exchange can exist on different chains (Ethereum, Optimism, Arbitrum, etc.) and must be handled and mapped separately. Swaps from DEXes are also different from trades in the traditional sense as there is no concept of ‘side’ upon trade ingestion. Combining all of these markets into one price that represents all of these pairs is a uniquely difficult task without a playbook from the TradFi world. 3. **Data correctness and outliers.** Due to the decentralized nature of crypto, anyone can spin up liquidity for a token on any multitude of decentralized exchanges. The liquidity for any given asset could be splintered into very small amounts (sometimes sub \$1000) that must either be part of the final price, or filtered out. Every market that any asset trades on requires mapping and curation. 4. **Bad data.** Messari often has overlap of coverage between our sources. This means we get duplicated raw trades from the same venues from different sources, and in some cases these sources might disagree with each other. At other times, we might only have one source for a particular market, but have reason to believe that the data is incorrect. As a result, we need a comprehensive method of detecting and excluding bad data. 5. **Duplicated tickers, redenominated tokens, migrated contracts.** The large number of assets and exchanges in the space necessitates an accurate map with unique IDs. Because each provider maintains their own map, work must also be done to relate multiple maps to each other. In order to solve for the above challenges, Messari maintains extensive mapping of all our assets and venues. We also check for price and volume outliers at several steps in our process, and employ a comprehensive graph structure with confidence scoring to denominate assets correctly. The full methodology is explained below. # Data Ingestion Messari maintains relationships with partners that provide us with continuous feeds of trade data. All of these feeds are converted into 1-minute OHLCV objects, and are then transformed/downsampled into the datasets described above. Messari strives to have both adequate breadth of coverage as well as accuracy in its market data service. We solve for each in the following way: 1. **Breadth of coverage** 1. To ensure that we have as broad coverage as possible, Messari ingests raw trades and swaps from a variety of venues in the space. To supplement this coverage, we also contract with several third-party providers to supply us with trade data from venues we don’t support internally. 2. **Correctness and mapping** 1. We ingest raw trade data that we turn into candle objects. This allows us to employ outlier detection at the trade level and more carefully examine our data. 2. Because we aggregate our market data from various providers as well as internal sources, Messari maintains extensive mapping to ensure that we are connecting the right markets. # Pair Pricing As new and updated OHLCV objects are computed, we construct a graph structure to traverse the best path back to USD. Each graph edge contains the set of observed prices of one asset in terms of the other, such that traversing the graph allows the system to price any asset in terms of any other asset to which there is a valid path. To account for the possibility of receiving inaccurate source data or dislocated markets, we use a confidence score on each graph edge computed based on a combination of the number of observed markets, as well as the variability of the set of observed markets. When traversing the graph data structure, an extremely high number of paths are possible. The system chooses the path with the most liquidity and least variance. # Asset Pricing After the graph data structure is updated and traversed to update the estimated USD value of each crypto asset, the market data system performs a volume-weighted average price computation for each asset that was traded since the last update. All asset pairs in which an asset trades, irrespective of whether the relevant asset appears as the base or quote of each pair, are incorporated into that asset’s VWAP. If the relevant asset appears as the quote in a given market, that associated OHLCV is transformed, or “flipped,” such that the numerical OHLCV values are like terms with those OHLCVs where the relevant asset appears as the base. The VWAP calculation process is a simple weighted arithmetic mean calculated once each for the open, high, low, and close values. Detailed outlier detection and rejection is performed using a variety of proprietary techniques. # Latencies Messari typically receives a trade within a few minutes after it occurs. This can be variable for different markets - CEX markets are typically received much faster, while DEX markets might be more delayed to account for block times and potential chain re-orgs. Due to different chains having different frequencies of re-orgs and block times, our DEX latency can differ by network. OHLCVs are continually updated with up to a five minute delay. For example, the 9:00 UTC hourly OHLCV will be continually updated from approximately 9:05 UTC to 10:05 UTC. 1-minute granularity time series data points are continuously recomputed during and for up to 10 minutes after the interval they represent, and are not made available by API. This also means that data at all granularities may change for up to 10-15 minutes after it becomes initially available via API. Candles are finalized after 15 minutes of their end-time. # Corrections We employ several corrective measures upon discovering inaccurate data. ## Market Exclusions Messari strives to show VWAP data that represents the “true” market price as closely as possible for all our assets. To do this, there are instances when one or more markets for an asset have to be excluded from the final price. This can be due to suspected bad source data, incorrect mappings, or large price/volume differentials. These exclusions can be for certain time periods, or for entire markets. We maintain a list of markets that we exclude in order to more properly represent the assets. Entries to this list are on a case-by-case basis and are driven by real-time outlier detection methods as well as manual checks. ## Exchange Exclusions Messari maintains a list of exchanges that we consider accurate sources of data. We exclude exchanges that might be going through hacks, locked withdrawals, or generally have frequent price dislocations and inaccurate pricing. This list of exchanges can change as events occur, and can be given to customers upon request. ## Discrete Backfills As we find bad data and update our exclusion lists, we periodically backfill our database with the new exclusions and recalculate historical prices. Although this can have minimal effect overall, the effects can be more acute in specific assets or time periods. ## Nightly Backfills To ensure completeness and accuracy of our market data, we do a nightly backfill that can re-write the previous 3 days of data with more accurate data. This is generally used to fill gaps that we might have missed during live ingestion. In cases of bad data ingestion, this also serves as an additional check on accuracy. # Supply Information Supply data is a critical component when evaluating this market, allowing users to understand token scarcity, potential for growth, and gauge relative value by looking at market capitalization and fully diluted values. To provide reliable supply metrics for each token, we record the circulating, total, and max supplies (when existing) for each token. We use these in combination with our internal pricing to calculate market cap, fully diluted valuation (FDV), and market dominance. Although total supply can often be fetched from a node, circulating supply and max supply are generally not as readily available. Many tokens such as ETH do not have a fixed cap or max supply, and circulating supply must often be calculated by deducting locked tokens, which requires understanding team wallets and vesting schedules. Messari contracts with two third-party vendors that supply circulating, total, and max supply data for supported tokens. Because of the difficulties of calculating circulating supply as described above, these numbers can often differ among sources. When the values differ, we pick the more accurate source according to our research and data. The calculations for each derived metric is shown below: MCAP = \[Circulating Supply x Messari VWAP Asset Price] FDV = \[Total Supply x Messari VWAP Asset Price]\*\* MCAP Dominance = \[Token MCAP / Total Crypto MCAP] \*\* When assets don’t have a Total Supply, we fall back to Max Supply. # Volume Discrepancies Due to the fragmentation of liquidity found in crypto, where assets are able to trade on hundreds of Decentralized and Centralized Exchanges, reported volumes at the Asset level can differ greatly between different providers. Messari considers volumes from all the exchanges our providers have available that we consider trustworthy, but it is possible that our reported volumes can differ from other sites due to a combination of differing exchange coverage as well different methodologies when dealing with suspected bad volumes from certain exchanges. # Fundraising Taxonomy Source: https://docs.messari.io/glossary/fundraising-taxonomy A taxonomy of fundraising events and their associated metrics # Messari Fundraising Data The foundation for our database was strengthened with the acquisition of Dove Metrics in July 2022. Our dedicated team of analysts then dove deep into manual research to enrich, backfill, and complete fundraising data where public information is available. Our process involves meticulous analysis of leading news outlets, company documentation, and collaboration with blockchain teams and investment firms. As the dynamic crypto fundraising world evolves, we will continually refine our dataset, updating and incorporating new information as it surfaces. ## Which companies are included? The database encompasses a broad spectrum of companies including crypto and NFT projects, metaverse platforms, and gaming entities. Also featured are service-focused firms and key infrastructure entities ranging from mining services to exchanges, wallets, and market makers. It's important to note that the database omits companies with only a tangential link to blockchain or those where crypto is not a core aspect of their business. All companies are listed by their most recent names to stay current, ensuring any rebrands or evolutions are accurately captured. ## Classification Projects, organizations, and investors are classified via the [Messari Classification System](https://docs.messari.io/docs/messari-classification-system). # Definitions ## Funding Rounds ### Dates We determine the announcement date mainly from the date associated with a fundraising round announcement. It is worth noting that the announcement date differs from when the funding round closed, as this information is often private. Additionally, in the database, some announcements may refer to previous fundraising rounds for the company. To ensure that we maintain a consistent and comprehensive dataset and to support accurate historical comparisons, we follow these guidelines when approximating dates: * If we have the day, month, and year, list the date * If we have the month and year, use the first day of the month (for example, November 2017 would be 11/1/2017) * If we have only a year, use the first day of the year (for example, “in 2016” would be 1/1/2016) ### Announcement URL This is a direct link to an announcement related to the fundraising round. We prioritize announcements directly from the funded team or an investor involved in the round. If such primary sources are unavailable, we rely on reputable news outlets like Coindesk, Techcrunch, and others for this information. ### Type We categorize the "type" based on the funding stage specified in the announcement article. For non-standard investment types, we use the following guidelines: * *Unknown*: This category is used when the round's stage is not detailed in the announcement or doesn't align with a typical investment category. * *Strategic*: These investments, typically highlighted in announcements, involve either one firm's investment in another or occur at intervals between recognized stages, like Series A, Series B, etc. * *Private Token Sale*: Represents token investments that are exclusively accessible to certain individuals or entities and not to the general public. * *Public Token Sale*: This includes a range of public fundraising techniques such as ICOs, IDOs, IEOs, and other similar crowdfunding mechanisms. Messari aims to accurately classify funding rounds into as many relevant stages as possible. ### Stage A classification that indicates the specific phase or period of financial investment a company is in. The nature and purpose of the capital raised typically identifies this stage. * *Seed*: Encompasses both Seed and Pre-seed investment phases. * *Early Stage Venture*: Covers all equity investments that occur post-Seed but before reaching Series C. * *Late Stage Venture*: Represents equity investments starting from Series C up to, but not including, the IPO. * *Public Equity Offering*: Refers to an Initial Public Offering (IPO) or similar events. * *Post-Public Equity*: Investments made following the completion of an IPO. * *Miscellaneous*: Pertains to fundraising rounds that don't align with the above categories. This includes but is not limited to, strategic investments, token sales, and others. ### Amount The recorded amount is in USD for each fundraising round as of the date linked to that round. If the initial announcement is in a different currency, we convert that amount to USD using the exchange rate for the currency pair on the date associated with the funding round. Please note amounts in an announcement labeled as "expected to raise" or "seeks to raise" aren't included. These figures are logged in the database as zero since we can't verify the amount received. ### Valuation Messari uses the post-money valuation when the information is available. ### Investors Messari aims to provide a thorough list of investment firms and individual angel investors for each funding round to offer comprehensive investment portfolios. Our displayed information results from analyzing various sources, including multiple announcements, official company documents, reviews of investment firm portfolios, and more. It's important to highlight that the linked announcement for a round may not list every investor mentioned, but this information was verified elsewhere. Often, complete details emerge gradually and might not be available during the initial announcement. Messari will consistently update and enhance the database as new data surfaces. # Data Challenges Due to the private nature of venture fundraising deals, the dataset is constrained by what is publicly available. As such, the database reflects the information available in public announcements. This methodology injects inherent biases in the data, reflected below: ## Availability of Deal Data The process for sourcing and aggregating crypto fundraising deals is a manual process that requires many broad data sources. Public information is most available for prominent and bigger investment firms and companies. As such, the data is inherently skewed towards these larger entities. Smaller investment firms and projects will be less represented in the dataset, but this information has been logged where available. Additionally, it is common for all sizes of companies to have their initial fundraising activities unannounced to the public. As a result, when examining the database from a perspective of complete information for a company’s fundraising activities, especially in terms of the total amount raised, these preliminary and typically smaller fundraising rounds might be absent. ## Data Latency Fundraising rounds close well before being announced to the public. The fundraising close date is often not available to the public. When aggregating data based on publicly available information, there is an inherent bias representing a lag between the closed date and the announced date. ## Investors Some investment firms or angel investors may invest in a company but ask to be left off the announcement of the fundraising round. Additionally, fundraising announcements include some iteration of “with additional investors.” Messari aims to present complete investor information for fundraising rounds and investor portfolios, but this is not always possible. # Corrections Messari actively seeks to present the most complete and accurate data for crypto fundraising. We will continually monitor, backfill, and correct incomplete or incorrect data. If you want to see your investment firm or company’s data in the database, please contact [fundraising@messari.io](mailto:fundraising@messari.io). # Funding Rounds Screener You'll find below the complete list of metrics and definitions available in our Funding Rounds screener. | Metric Name | Definition | | :- | :- | | Type | Funding Round Types are granular classifications of rounds that include Pre Seed, Seed, Series A, Series B, Series C and 25 others types. | | Stage | Funding Round Stages are high-level classifications of rounds that include Seed, Early Stage Venture, Late Stage Venture, Public Equity Offering, Post Public Equity, Miscellaneous. For a more detailed classification, refer to our Type field | | Date | The date at which the funding round was announced. Note that this is different to the date at which the funding round was closed. | | Amount Raised | Total amount raised in USD during the funding round, when available. Note that for rounds that were not denominated in US dollars, we apply the currency conversion rate at the date of the announcement. | | Funded Entity | The entity that received funding through the funding round. | | Investors | Investors that have invested in the funding round, according to available data. Note that this may be a subset of the real list of investors, as some investors may not be disclosed publicly. If you notice any data inaccuracy, or want to disclose information about missing investors, you can contact us at [fundraising@messari.io](mailto:fundraising@messari.io) . | | Investor Count | The total number of investors that invested in the funding round, according to available data. Note that this may be a subset of the real total number of investors, as some investors may not be disclosed publicly. | | Lead Investors | Lead investors that have invested in the funding round, according to available data. Note that this may be a subset of the real list of investors, as some investors may not be disclosed publicly. If you notice any data inaccuracy, or want to disclose information about missing investors, you can contact us at [fundraising@messari.io](mailto:fundraising@messari.io) . | | Post Money Valuation | Post-money Valuation is a way of expressing the value of the funded entity after the funding round. This value is equal to the sum of the pre-money valuation and the amount of new equity. Note that most often, Post Money Valuation is undisclosed and not available. | | Funded Entity Sector | The Messari Category Classification of the entity that received funding. Categories are high-level groups used to classify crypto market participants. Each category is composed of multiple sectors. Each entity can only belong to a single category. Categories include Networks, Markeplaces, Consumer Infrastructure, Metaverse & Gaming and 20 others. | | Funded Entity Category | .The Messari Tag Classification of the entity that received funding. Tags are free form ways to classify crypto market participants. An entity may have multiple tags, although it can only have a single sector and category. Tags include DeFi, DePin, DAO, Multisig Wallet and 50+ others. | | Funded Entity Networks | Networks of the native asset / protocol(s) launched by the entity that received funding. We aggregate all unique networks across the native assets and all underlying protocol. For example, in the case of AAVE, we will list all networks where the AAVE token is deployed, and where the different protocol versions (V3, V2 etc...) have been deployed as well. | | Has native asset? | Specifies whether the entity that received funding is part of a project that has a native asset that is currently tracked by Messari. For example, in the case of AAVE, this field will be TRUE, where in the case of Messari, this field will be FALSE. | | Native Asset MarketCap | The current marketcap of the native asset of the entity that has received funding, if it is part of a project that has a native asset that is currently tracked by Messari. | | Funded Entity City | The city where the funded entity is located. Note that at the moment we do not support multiple cities per entity. As a result the city specified will be the primary location of the funded entity. Also note that in some cases this datapoint may be unavailable. | | Funded Entity Country | The country where the funded entity is located. Note that at the moment we do not support multiple countries per entity. As a result the country specified will be the primary location of the funded entity. Also note that in some cases this datapoint may be unavailable. | | Funded Entity Region | The region where the funded entity is located. Note that at the moment we do not support multiple regions per entity. As a result the region specified will be the primary location of the funded entity. Also note that in some cases this datapoint may be unavailable. | | Funded Entity State | The state where the funded entity is located. Note that at the moment we do not support multiple states per entity. As a result the state specified will be the primary location of the funded entity. Also note that in some cases this datapoint may be unavailable. | | Funded Entity Subregion | The subregion where the funded entity is located. Note that at the moment we do not support multiple subregion per entity. As a result the subregion specified will be the primary location of the funded entity. Also note that in some cases this datapoint may be unavailable. | *** # Investor Screener You'll find below the complete list of metrics and definitions available in our Investor Screener. | Metric Name | Category | Definition | | :- | :- | :- | | Type | General | High-level classification system used for investors. Types include Investment Firms, Angel Investors, DAOs, Corporates, Foundations, Incubators & Accelerators as well as whether the investor is Crypto Native or Non-Crypto Native. | | City | General | The city where the investor is located. Note that at the moment we do not support multiple cities per investor. As a result the city specified will be the primary location of the investor. Also note that in some cases this datapoint may be unavailable. | | State | General | The state where the investor is located. Note that at the moment we do not support multiple states per investor. As a result the state specified will be the primary location of the investor. Also note that in some cases this datapoint may be unavailable. | | Country | General | The country where the investor is located. Note that at the moment we do not support multiple countries per investor. As a result the country specified will be the primary location of the investor. Also note that in some cases this datapoint may be unavailable. | | Subregion | General | The subregion where the investor is located. Note that at the moment we do not support multiple subregions per investor. As a result the subregion specified will be the primary location of the investor. Also note that in some cases this datapoint may be unavailable. | | Region | General | The region where the investor is located. Note that at the moment we do not support multiple regions per investor. As a result the region specified will be the primary location of the investor. Also note that in some cases this datapoint may be unavailable | | Founded on | General | The date when the investment firm was founded, based on publicly disclosed data. | | Funded Rounds | Investments | The list of publicly disclosed rounds funded by an investor. Note that this only reflects publicly disclosed rounds, for which the funded entity has a crypto component. As such this may be not include all the rounds a given investor has partitipated in across all industries, and in crypto, given not all rounds are publicly disclosed and the investor list is not always fully disclosed. We are continuously working to improve our coverage. If you notice any data inaccuracy, or want to disclose information about missing investors, you can contact us at [fundraising@messari.io](mailto:fundraising@messari.io) . | | Funded Entities | Investments | The list of unique entities funded by an investor based on its participation in funding rounds. If an investor participated in multiple rounds for the same entity, this entity will only be listed once. | | Funded Funds | Investments | The list of publicly disclosed funds funded by an investor. Note that this only reflects publicly disclosed funds that have a total or partial crypto focus, and have disclosed their Limited Partners. As such this may be lower than the total number of funds a given investor has funded. We are continously working to improve our coverage. If you notice any data innacuracy, or want to disclose information about missing investors, you can contact us at [fundraising@messari.io](mailto:fundraising@messari.io) . | | Funded Rounds Count | Investments | The total number of publicly disclosed rounds funded by an investor. Note that this only reflects publicly disclosed rounds, for which the funded entity has a crypto component. As such this may be lower than the total number of rounds a given investor has participated in across all industries, and in crypto, given not all rounds are publicly disclosed and the investor list is not always fully disclosed. We are continuously working to improve our coverage. If you notice any data inaccuracy, or want to disclose information about missing investors, you can contact us at [fundraising@messari.io](mailto:fundraising@messari.io) . | | Funded Entities Count | Investments | The count of unique entities funded by an investor based on its participation in funding rounds. If an investor has participated in multiple rounds for the same entity, this entity will only be counted once. | | Funded Funds Count | Investments | The total number of publicly disclosed funds funded by an investor. Note that this only reflects publicly disclosed funds that have a total or partial crypto focus, and have disclosed their Limited Partners. As such this may be lower than the total number of funds a given investor has funded. We are continuously working to improve our coverage. If you notice any data inaccuracy, or want to disclose information about missing investors, you can contact us at [fundraising@messari.io](mailto:fundraising@messari.io) . | | Round Amount | Investments | The mean, median, min, max amount raised for funding rounds an investor participated in a given period. | | Co-Investors | Investments | Co-investors are investors which regularly invest in the same rounds as the given investor. In order to be considered a co-investor, the investor must have participated in at least 25% of the same rounds as the other investor and at least 3 rounds in total. Only the top 15 co-investors by the number of rounds shared are included. | | Last Investment | Investments | The last publicly disclosed funding round an investor participated in, as tracked by Messari. Note that this only reflects publicly disclosed rounds, for which the funded entity has a crypto component.. | | First Investment | Investments | The first publicly disclosed funding round an investor participated in, as tracked by Messari. Note that this only reflects publicly disclosed rounds, for which the funded entity has a crypto component. | | First Investment Date | Investments | The date of the last publicly disclosed funding round an investor participated in, as tracked by Messari. Note that this only reflects publicly disclosed rounds, for which the funded entity has a crypto component. | | Last Investment Date | Investments | The date of the first publicly disclosed funding round an investor participated in, as tracked by Messari. Note that this only reflects publicly disclosed rounds, for which the funded entity has a crypto component. | | Investment Count by Deal Stage | Investment Behavior | The number of funding rounds an investor participated in with specified stage over the specified time period. Funding round stages are high-level classifications of rounds that include Seed, Early Stage Venture, Late Stage Venture, Public Equity Offering, Post Public Equity, Miscellaneous. For a more detailed classification, refer to our Type field. | | Investment Count by Deal Type | Investment Behavior | :The number of funding rounds an investor participated in with the specified type over the specified time period. Funding round types are granular classifications of rounds that include Pre Seed, Seed, Series A, Series B, Series C and 25 other types. | | Investment Count by Sector | Investment Behavior | The number of times an investor invested in the specified sector, derived from the entity funded, over the specified time period. Sectors are granular groups used to classify crypto market participants. Each sector has a unique parent category. Each entity can only belong to a single sector. For entities that may fit into multiple sectors, we apply the sector that is best suited based on the primary business model, revenue source or application. Sectors include Smart Contract Platform, Exchange, Analytics, Gaming and 80 others. | | Investment Count by Category | Investment Behavior | The number of times an investor invested in the specified category, derived from the entity funded, over the specified time period. The Messari Category Classification of the entity that received funding. Categories are high-level groups used to classify crypto market participants. Each category is composed of multiple sectors. Each entity can only belong to a single category. Categories include Networks, Marketplaces, Consumer Infrastructure, Metaverse & Gaming and 20 others | | Investment Count by Tag | Investment Behavior | The number of times an investor invested in an entity with the specified tag over the specified time period. Tags are free form ways to classify crypto market participants. An entity may have multiple tags, although it can only have a single sector and category. Tags include DeFi, DePin, DAO, Multisig Wallet and 50+ others. | | Most Common Investment Type | Investment Behavior | The most common funding round type that an investor invested in. Funding round types are granular classifications of rounds that include Pre Seed, Seed, Series A, Series B, Series C and 25 others types. | | Most Common Investment Stage | Investment Behavior | The most common funding round stage that an investor invested in. Funding round stages are high-level classifications of rounds that include Seed, Early Stage Venture, Late Stage Venture, Public Equity Offering, Post Public Equity, Miscellaneous. For a more detailed classification, refer to our funding round Type field. | | Most Common Investment Sector | Investment Behavior | The most common sector among the entities that an investor invested in. Sectors are granular groups used to classify crypto market participants. Each sector has a unique parent category. Each entity can only belong to a single sector. For entities that may fit into multiple sectors, we apply the sector that is best suited based on the primary business model, revenue source or application. Sectors include Smart Contract Platform, Exchange, Analytics, Gaming and 80 others | | Most Common Investment Category | Investment Behavior | The most common category among the entities that an investor invested in. Categories are high-level groups used to classify crypto market participants. Each category is composed of multiple sectors. Each entity can only belong to a single category. Categories include Networks, Markeplaces, Consumer Infrastructure, Metaverse & Gaming and 20 others. | | Limited Partners | Funding | The Limited Partners (LPs) that have invested in funds where the investor is the Fund Manager. LPs are investors in a fund like shareholders in a corporation. Note that the detailed list of LPs is not always available. Also note that the Messari Funds dataset focused on funds that invest in crypto projects and companies. As such, for non-crypto native investors that have raised funds targeted entirely or partialy toward crypto, we will only track those funds and associated LPs. | | Limited Partners Count | Funding | The number of unique Limited Partners (LPs) that have invested in funds where the investor is the Fund Manager. LPs are investors into a fund like shareholders in a corporation. Note that the detailed list of LPs is not always available. Also note that the Messari Funds dataset focused on funds that invest in crypto projects and companies. As such, for non-crypto native investors that have raised funds targeted entirely or partially toward crypto, we will only track those funds and associated LPs | *** # Funds Screener You'll find below the complete list of metrics and definitions available in our Funds screener. | Metric Name | Definition | | :- | :- | | Date | Date at which the fund was announced, or at which the last amendment was signed in the case of a Form D. | | Amount Raised | Total amount raised by the fund from Limited Partners (LPs), when available. Data is sourced from press releases, blog posts, news and fillings (Form D). Note that this data may change as Form D filing amendments occur. | | Fund Managers | Firm managing the fund that has been raised. Note that some funds may have multiple fund managers. | | Limited Partners | Limited Partners (LPs) are the investors into the fund like shareholders in a corporation. Note that the detailed list of LPs is not always available. | | Limited Partners Count | Total number of Limited Partners that have invested in the fund. Limited Partners (LPs) are the investors into the fund like shareholders in a corporation. Note that the detailed list of LPs is not always available. | *** # M\&A Screener You'll find below the complete list of metrics and definitions available in our M\&A screener. | Metric Name | Definition | | :- | :- | | Date | Announcement date of the merger or acquisition. | | Price | The settlement price of the acquisition or merger, when available. Note that most often, this price is undisclosed and not available. | | Acquired Company | The entity that was acquired through the deal. | | Acquiring Company | The entity that performed an acquisition through the deal. | | Acquired Company Sector | The Messari Sector Classification of the entity that was acquired through the deal. Sectors are granular groups used to classify crypto market participants. Each sector has a unique parent category. Each entity can only belong to a single sector. For entities that may fit into multiple sectors, we apply the sector that is best suited based on the primary business model, revenue source or application. Sectors include Smart Contract Platform, Exchange, Analytics, Gaming and 80 others. | | Acquired Company Category | The Messari Category Classification of the entity that was acquired through the deal. Categories are high-level groups used to classify crypto market participants. Each category is composed of multiple sectors. Each entity can only belong to a single category. Categories include Networks, Marketplaces, Consumer Infrastructure, Metaverse & Gaming and 20 others. | | Acquired Company Tags | The Messari Tag Classification of the entity that was acquired through the deal. Tags are free form ways to classify crypto market participants. An entity may have multiple tags, although it can only have a single sector and category. Tags include DeFi, DePin, DAO, Multisig Wallet and 50+ others. | # Governance Taxonomy Source: https://docs.messari.io/glossary/governance-taxonomy A taxonomy of governance events and their associated metrics # Status To track proposals, every proposal in Messari Governor has an attached status to it. Below are the definitions of each status: | Status | Definition | | :- | :- | | Preliminary Discussion | The proposal is currently being discussed by the community but has not been submitted for a vote. | | Upcoming Vote | The proposal has been submitted by a vote (off-chain or on-chain) that has not started yet. | | Active Vote | The proposal is currently being voted on (off-chain or on-chain). | | Succeeded | The proposal has succeeded. For some proposals, this will be the terminal state, as they don't require any form of execution. For others, the proposal will then be queued for execution. | | Queued | The proposal has been queued for execution and will be executed on-chain. | | Failed | The proposal has failed. This can happen if the quorum hasn't been reached or if the choice for the proposal to succeed hasn't gathered enough votes. | | Canceled | The proposal has been canceled. This can happen at all stages of the proposal life-cycle. | | Executed | The proposal has been executed on-chain. | | Pending Analysis | This happens when a proposal has been voted on Snapshot and the snapshot vote is now closed. This requires human intervention to know if the proposal has succeeded or failed, if there will be another vote, an on-chain execution, or not. | # Categories and Subcategories Each proposal in Governor has one assigned category and sub-category. After selecting a category, the connected sub-categories will only be available. | Category Name | Available Subcategories | Examples | | :- | :- | :- | | Funding | Equity Funding, Debt Funding, Public Token Sale, Private Token Sale | Project closes equity funding round, Project closes debt funding round, Project sells token to public/ICO/IDO, Project sells token not available to public | | Governance | Governance Update, Other Network Change | Project governance process is changed, DAO/voting council election/elected, Polkadot parachain auctions | | Integration | Scaling Solution Integration, Cross-Chain Bridge Integration, Oracle Integration | A project integrates a scaling solution, a bridge, or an oracle | | Parameter Change | Fee Parameter Change, Collateral Parameter Change | Fee parameter is changed on application, Collateral parameters are changed | | Release | Core Client Release, SDK Release, On-Chain Upgrade, Contract Deployment, On-Chain Upgrade, Other Network Change | Application releases upgraded contracts, Governance Vote to enable chain upgrade, Vulnerability is patched in Core client | | Security | Report, Fork, Mining and validation, Treasury Funded Expense, Bug Bounty Program | A security audit of a protocol has been published, A protocol is forked to patch a vulnerability, Bounty Bounty Program is launched | | Team and Operations | Treasury Funded Expense, Project Team, Grant Program, Report, New Brand or Rebrand, Call or Meeting, Other Project Change | Projects spend treasury funds, team funding | | Token Supply | Airdrop, Treasury Funded Expense, Liquidity Mining Program, Treasury Funded Expense, Mining and Validation, Grant Program, Supply Unlock, Supply Lock | A portion of the token supply has been allocated for a grant program, A portion of the protocol's native token supply is locked and no longer freely transferable, Tokens vest/tokens are unlocked | | Token Type | New Supported Asset, New Collateral Asset, New Token, Airdrop, Token Swap, Other Token Change | The application adds new asset support, Lending app adds new collateral asset, Project launches new native token | # Importance The importance level is set based on the impact a certain proposal may have on the protocol, or the token holders of the native asset of the protocol. The available importance levels are listed below: | Importance | Definition | | :- | :- | | Low | Includes proposals where no action is needed, no strong impact on stakeholders or the DAO itself, or the day-to-day DAO operations recurring proposals. Some examples are [team payroll changes](https://messari.io/governor/proposal/c7f4329d-fc2a-478a-a659-6267366563f1) and [small parameter updates](https://messari.io/governor/proposal/eceaeb72-2a54-4267-85c6-b7562d5894df) | | Medium | Includes proposals that engage substantial spending from a DAO, significant parameter changes, or uncommon decisions that are voted on but don't deeply impact the DAO or stakeholders. Some examples are [DAO budget approval](https://messari.io/governor/proposal/11f0e07d-0f66-416a-8065-4872fec9d0cd), small changes in [tokenomics](https://messari.io/governor/proposal/e7375d11-00bd-4e09-8f94-e23c1b1e5366), or the [governance process or structure](https://messari.io/governor/proposal/42a7ad55-a4c4-4ed1-9233-f717332f382e) | | High | Includes proposals that engage significant spending from a DAO, major changes in the DAO structure or smart contracts, or exceptional proposals stakeholders should be aware of. Some examples are [tokenomics revamp](https://messari.io/governor/proposal/39cf2045-f873-499a-82da-9704a7047904), [on-chain upgrades](https://messari.io/governor/proposal/b1fbe2b1-d97e-4316-a684-9868f5aa0ec1), and [important DAO expenses](https://messari.io/governor/proposal/5e289566-e770-4ebd-9048-d51a489ada7e) | | Very High | This is rarely used but should be used when an issue directly impacts stakeholders or the DAO, particularly if it is a time-sensitive proposal. Some examples are [hack-related proposals](https://messari.io/governor/proposal/04298921-9e4c-46f1-a79f-8a4c1f9a4a82) and [DAO mergers](https://messari.io/governor/proposal/e4532074-a3d8-4029-9552-77fbf3275f4f) | # Sentiment Levels Sentiment gauges interest in the proposal during the preliminary discussion phase. The sentiment level is based on the number of answers, the community members that participate in a given discussion, and their explicit support of the proposal. Listed below are the available 'Sentiment Levels': * **Negative** * **Neutral** * **Positive** * **Very Positive** # Monitoring Taxonomy Source: https://docs.messari.io/glossary/key-developments A taxonomy of monitoring developments, events, and their associated metrics. # Importance An importance level is assigned to every development to help classify how it affects the associated assets and protocols. Importance is derived based on the Category of the event. Below are general guidelines on what each Importance Level means. | Name | Description | | :- | :- | | High | Direct financial impact, security risk, or major change to how the asset/protocol functions or how users interact with it. | | Medium | Notable development that stakeholders should be aware of but does not fundamentally change how the asset/protocol operates or carry direct financial risk. | | Low | Routine or incremental update with limited immediate impact. | # Actionable An event is marked actionable when a specific group of users, such as node operators, token holders, validators, or developers, may need to take a concrete action in response, such as upgrading software, migrating tokens, or withdrawing funds. Purely informational events (announcements, personnel changes, completed upgrades) are not actionable. # Categories and Subcategories Monitoring uses 10 active categories and 56 subcategories. A Development can be tagged with more than one category or subcategory, and an Event rolls up all of its development categories. ## Categories | Name | Definition | | :- | :- | | **Component Management** | Covers changes to individual protocol components including onboarding new assets/markets, adjusting parameters, and upgrading specific components. | | **Launches and Releases** | Covers the release of new products, features, tokens, developer tools, and software updates. | | **Legal and Regulatory** | Covers regulatory actions, enforcement, legislation, and legal proceedings affecting crypto. | | **Performance** | Covers bugs, service disruptions, blockchain halts, node outages, and chain splits. | | **Protocol Management** | Covers network upgrades, governance, parameter changes, strategy, fees, migrations, discontinuations, integrations, and protocol upgrades. | | **Security and Hacks** | Covers exploits, hacks, vulnerability disclosures, and loss of funds incidents. | | **Team and Operations** | Covers branding, funding initiatives, organization changes, M\&A, personnel, and official reports. | | **Token Listing** | Covers spot listings, delistings, and other listing types on exchanges and platforms. | | **Tokenomics** | Covers airdrops, buybacks, token utility, revenue distribution, supply changes, and token allocations. | | **Treasury Management** | Covers strategic investments, treasury expenses, and other treasury operations. | ## Subcategories ### Component Management | Name | Definition | | :- | :- | | **Component Adjustment** | Parameter changes or offboardings for specific markets/assets (not protocol-wide). | | **Onboarding or Expansion** | Pre-existing infrastructure is expanded to support a new asset, market, or network. | | **Component Upgrade** | Meaningful improvements specific to individual protocol components. | ### Launches and Releases | Name | Definition | | :- | :- | | **Mainnet Launch** | New network launches. | | **New Product or Feature** | A project deploys an entirely new product or feature. | | **Testnet Launch** | Dedicated testnet launches. | | **New Token** | New token launches. | | **Developer Tooling** | Release of developer tooling, usually provided by a core team. | | **Software Release** | Formal deployment of updated code or client software by a project's core team. | | **Third-Party Tooling** | Release of notable tooling provided by an external party. | ### Legal and Regulatory | Name | Definition | | :- | :- | | **Approvals, Licenses, and Registrations** | Formal approvals, certifications, or recognitions granted by government authorities or regulatory bodies that allow an entity to operate within a given jurisdiction (e.g., money transmitter licenses, VASP registrations, trust charters, broker-dealer licenses). | | **Enforcement Actions** | Formal measures taken by regulatory or legal authorities against individuals, projects, or entities for alleged violations of laws or regulations (lawsuits, fines, penalties, cease-and-desist orders, license revocations, settlements). | | **Investigations and Inquiries** | Disclosure of preliminary proceedings by regulatory, legislative, or legal bodies into projects, companies, or market activities (subpoenas, RFIs, hearings, publicized probes, Wells Notices). | | **Financial Instruments** | Creation, filing, amendment, approval, or denial of investment vehicles that provide exposure to crypto assets through traditional financial structures (ETPs, ETFs, trusts, similar instruments). | | **Statutes and Executive Actions** | Legislative and executive actions by sovereign governments' primary constitutional bodies, including enacted laws and amendments, executive orders, presidential pardons, state-level policy declarations, and other binding decisions. | | **Agency Rulemaking, Guidance, or Policy** | Actions by regulatory or administrative agencies implementing, interpreting, or clarifying statutory authority. Includes binding rules, proposed regulations, interpretive guidance, policy statements, and no-action letters. | ### Performance | Name | Definition | | :- | :- | | **Bug Disclosure** | Acknowledgment of non-security bugs affecting protocol functionality, performance, or data integrity. | | **Service Disruption** | Degraded service resulting in unstable network conditions, maintenance, or other causes. | | **Blockchain Halt** | Network block production stops and external intervention may be required for block production to resume. | | **Node Outage** | Events involving nodes going offline. | | **Protocol or Smart Contract Halt** | One or more of a protocol's smart contracts are paused or disabled. | | **Chain Split** | A blockchain diverges into two or more separate chains, usually due to a contentious upgrade or governance dispute. | ### Protocol Management | Name | Definition | | :- | :- | | **Network Upgrade** | Coordinated upgrade to consensus-layer or base-layer infrastructure requiring node operator participation. Includes hard forks, soft forks, and client updates that affect block production, validation, or state structure. | | **Governance Update** | Changes to a project's governance contracts, structure, or processes. | | **Protocol Parameter Change** | Modifications to non-fee global parameters or system-wide settings, including risk parameters, collateralization ratios, debt ceilings, rate limits, and operational thresholds. | | **Project Strategy** | Updates related to a project's strategy or roadmap. | | **Protocol Fee Adjustment** | Changes to the fees a protocol charges or distributes. | | **Migration or Swap** | Token contract migration or swap to a different token. | | **Discontinuation** | Formal sunsetting of a product, service, or feature. | | **Integration or Partnership** | Formal partnership between key contributing entities, or the integration of external infrastructure often presented as new functionality. | | **Protocol Upgrade** | Deployment of significant improvements to application-layer smart contracts, including new versions, added functionality, or architectural changes. | ### Security and Hacks | Name | Definition | | :- | :- | | **Protocol Exploit** | Hacks or attacks targeting a protocol's core contracts. | | **Frontend Exploit** | Attacks targeting project frontends. | | **Vulnerability Disclosure** | Disclosure of security vulnerabilities that could have enabled unauthorized access, fund theft, or protocol manipulation. | | **Custodian Loss of Funds** | Attacks targeting centralized exchanges or other major custodians. | | **Consensus-Related Exploit** | 51% attack or similar attack in which a malicious actor gains control of a network. | | **Other Hack or Attack** | Other security-related incidents. | ### Team and Operations | Name | Definition | | :- | :- | | **New Brand or Rebrand** | Formal introduction of a new brand or the official rebranding of a project or key contributing entity. | | **Centralized Funding Initiatives** | Ecosystem programs funded by centralized entities (core team, foundation, labs) rather than a treasury. Includes grants, accelerators, retroactive funding, and developer incentives deployed at the discretion of the contributing entity rather than through on-chain governance. | | **Organization Change** | Significant changes to the structure or operational framework of a key contributing entity. | | **Mergers, Acquisitions, or Fundraising** | Notable mergers, acquisitions, and fundraising events. | | **Personnel Change** | Notable changes to personnel such as executives, advisors, or multisig signers. | | **Official Report or Update** | Official reports or updates from key contributing teams, including but not limited to custodian attestations, financial reports, code audits, and post-mortems. | ### Token Listing | Name | Definition | | :- | :- | | **Spot Listing** | A major exchange enables spot trading for an asset. | | **Delisting** | A major exchange removes support for a crypto asset. | | **Other Listing** | Addition of asset custody, transfer, or access support by centralized platforms that are not primarily trading venues. Includes institutional custodians, payment processors, banking platforms, and asset management services. | ### Tokenomics | Name | Definition | | :- | :- | | **Airdrop** | A discrete, retrospective distribution of tokens to users based on historical behavior or eligibility criteria, which often coincides with TGE. | | **Token Buybacks** | A DAO or key contributing entity repurchases its native token from the open market or through structured programs. Includes both discretionary and programmatic buyback mechanisms. | | **Token Utility** | Updates to a token's use case within its respective ecosystem. | | **Revenue Distribution** | Protocol-generated revenue (fees, yield, MEV, or other earnings) is distributed to token holders, stakers, or designated parties. May be in stablecoins, ETH, or other non-native assets. | | **Token Supply** | Changes to the circulating or total supply of a crypto asset that are usually not documented in the original token distribution, including significant locks, unlocks, emissions adjustments, and non-programmatic mints or burns. | | **Other Tokenomics Update** | Other notable tokenomics updates. | | **Native Token Allocation** | The establishment, modification, or rebalancing of native token distribution programs. Includes protocol emissions schedules, user incentive programs (seasons, points, liquidity mining), and governance-approved allocation adjustments. | ### Treasury Management | Name | Definition | | :- | :- | | **Strategic Investment** | Discretionary deployment of treasury capital for non-operational purposes, including (but not limited to) token swaps, OTC deals, equity investments, IP rights, and one-time strategic grants. | | **Treasury Expense** | Recurring or predictable operational costs paid by the DAO/Treasury that are necessary for protocol or foundation operations. Includes contributor compensation, infrastructure, audits, legal, and administrative overhead. | | **Other Treasury Operations** | Notable treasury management activities that don't constitute an expense or investment. | # Governance A Governance Tag is included for all Developments that involve the Governance process for an asset. This includes a Forum Discussion, offchain or onchain proposals. # Introduction Source: https://docs.messari.io/introduction **Looking for the latest API?** This documentation covers the legacy Messari API, which is in maintenance mode. It will continue to be supported for existing integrations, but no new endpoints, datasets, or features will be added here. New integrations should be built on the Blockworks API at [docs.blockworks.com](https://docs.blockworks.com). Messari’s collection of APIs provide a range of quantitative and qualitative data to support any use case including: market data, onchain data, news, fundraising and more. Our enterprise-grade APIs power global companies including: Coinbase, Robinhood, Chainlink, EY, BNY Mellon, PwC and hundreds of others. Everything shown in the user-interface on [messari.io](http://messari.io) is available for usage via the API. An overview of our APIs is below: | **Endpoints** | **Description** | **Explore the data on Messari UI** | | :- | :- | :- | | [**Asset & Market Data**](/api-reference/endpoints/metrics/metrics-api) | Market data such as price, trading volume and marketcap for over 40,000 assets. | [https://messari.io/assets](https://messari.io/assets) | | [**Exchanges**](/api-reference/endpoints/exchanges/exchanges-api) | Spot volumes, futures volume and futures open interest across cryptocurrency exchanges. | [https://messari.io/exchanges](https://messari.io/exchanges)
[https://messari.io/exchange/binance](https://messari.io/exchange/binance) | | [**News**](/api-reference/endpoints/news/news-api) & [**Topics**](/api-reference/endpoints/topics/topics-api) | Aggregated news from 500+ sources including headlines, links and summaries, with assets tagged per article. | [https://messari.io/news](https://messari.io/news)

[https://messari.io/signals](https://messari.io/signals) (Topics on right-side feed) | | [**Research**](/api-reference/endpoints/research/research-api) | Access to Messari’s Protocol Reporting Research. | [https://messari.io/research/protocol-reporting](https://messari.io/research/protocol-reporting) | | [**Stablecoins**](/api-reference/endpoints/stablecoins/stablecoins-api) | Onchain data for 30+ Stablecoins such as USDT, USDC and DAI, including stablecoin marketcap, stablecoin active addresses, transfers, transaction volume and more. | [https://messari.io/stablecoins](https://messari.io/stablecoins) | | [**Networks**](/api-reference/endpoints/metrics/v2/networks) | Onchain data for 25+ Layer-1s and Layer-2s such as Ethereum and Solana, including Transaction Fees, Active Addresses, and more. | [https://messari.io/networks](https://messari.io/networks) | | [**Protocols**](/api-reference/endpoints/protocols/protocols-api) | Onchain data for 200+ Protocols such as Uniswap and Aave, including as Total Value Locked, Active Addresses, Deposits/Borrows, Trading Volume, and more.

Protocols are split into various types:
- Core (all)
- DEX
- Lending

Additional Protocol Types such as Liquid Staking will be supported in the future. | Protocol Data is not currently available in the UI | | [**Token Unlocks**](/api-reference/endpoints/token-unlocks/token-unlocks-api) | Monitor token vesting schedules, upcoming unlock events, and token allocation details for over 200 crypto projects. | [https://messari.io/token-unlocks](https://messari.io/token-unlocks) | | [**Fundraising**](/api-reference/endpoints/funding/funding-api) | Crypto’s biggest fundraising database for funding rounds, M\&A deals, and investors. | [https://messari.io/fundraising](https://messari.io/fundraising) | | [**AI**](/api-reference/endpoints/ai/ai-api) | Integrate with Messari AI to unlock all of our AI capabilities. | [https://messari.io/copilot](https://messari.io/copilot) | | [**Signals**](/api-reference/endpoints/signal/overview) | Track social data and narratives including mindshare and sentiment across individual crypto projects, or at the sector/sub-sector level | [https://messari.io/signals](https://messari.io/signals) | | [**Intel**](/api-reference/endpoints/intel/intel-api) | Real-time onchain and offchain event monitoring with human curated summaries. | [https://messari.io/intel](https://messari.io/intel) | | [**Monitoring**](/api-reference/endpoints/monitoring/monitoring-api) | Next-gen replacement for Intel: categorized developments and events, plus saved monitoring views (simple filters or prompt-based agentic views). | [https://messari.io/intel](https://messari.io/intel) | | [**Watchlists**](/api-reference/endpoints/user-management/user-management-api) | Create and manage custom watchlists to organize and track groups of assets. | [https://messari.io/watchlists](https://messari.io/watchlists) | # MCP Server Source: https://docs.messari.io/mcp-server/hosted Fully hosted Model Context Protocol server for accessing Messari's AI-powered crypto intelligence through any MCP client # Messari MCP Server The hosted MCP server provides the simplest way to connect AI assistants like Claude Desktop, Cursor, and Claude Code to Messari's crypto intelligence platform. Unlike traditional MCP servers that require local installation, this server is fully hosted—just add a URL and authenticate. It provides tools for AI-powered document search, natural-language dataset queries, and direct timeseries data access. ## Key Benefits No npm, no npx, no local dependencies. Just add a URL to your MCP client. Browser-based authentication with your Messari API key. No keys in config files. Dedicated search and dataset agents, so the client picks the right one for the question. Hosted infrastructure means you always have the latest capabilities. ## Quick Setup Add the Messari MCP server to your AI assistant in seconds: **MCP Server URL:** ``` https://mcp.messari.io/mcp ``` When you first connect, you'll be redirected to authenticate with your Messari API key through a secure OAuth flow. ## Configuring MCP Clients ### Claude Connectors To add Messari as a custom connector in Claude: 1. Navigate to [claude.ai/settings/connectors](https://claude.ai/settings/connectors) 2. Click **Add custom connector** 3. Enter the MCP server URL: `https://mcp.messari.io/mcp` 4. Click **Connect** and enter your Messari API key when prompted ### OpenAI ChatGPT App To add Messari as a custom App in ChatGPT: 1. Navigate to [chatgpt.com/admin/ca#available](https://chatgpt.com/admin/ca#available) 2. Enable developer mode. 3. Click **Create** 4. Enter the MCP server URL: `https://mcp.messari.io/mcp` 5. Leave Authentication as OAuth. 6. Click **Create** and enter your Messari API key when prompted ### Claude Code Add to your Claude Code MCP settings: ```json theme={null} { "mcpServers": { "messari": { "url": "https://mcp.messari.io/mcp" } } } ``` ### Cursor Add to your Cursor MCP configuration: ```json theme={null} { "mcpServers": { "messari": { "url": "https://mcp.messari.io/mcp" } } } ``` ### Other MCP Clients Any MCP-compatible client that supports remote servers can connect using: * **URL**: `https://mcp.messari.io/mcp` * **Authentication**: OAuth 2.0 (handled automatically) ## Authentication Flow When you first connect: 1. Your MCP client will detect the server requires authentication 2. A browser window opens to the Messari OAuth page 3. Enter your Messari API key 4. You're authenticated and ready to query Your API key is securely stored and used to authenticate requests to Messari's services. You can obtain an API key from your [Messari account settings](https://messari.io/account/api). ## API Permissions Access to the MCP server requires a **Messari Enterprise subscription** with access to the **AI Toolkit**. Access to each tool and its underlying data depends on your API key's subscription tier. `search_messari_documents` and `query_messari_datasets` additionally require an authenticated Enterprise user whose team holds the `ai_toolkit_permission` API permission, shown as **Messari AI API** in team settings. A caller without it sees a `FORBIDDEN` error from the tool. For more information on API tiers, permissions, and rate limits, see our [API Permissions documentation](/api-reference/permissions). ### Rate Limits `search_messari_documents` and `query_messari_datasets` each allow **30 requests per minute per user**, counted in its own bucket — search traffic does not consume the dataset tool's allowance. Exceeding a bucket returns a `RATE_LIMITED` error from that tool. ### Credits The search and dataset tools do not consume AI credits. These two tools call the [Agents API](/api-reference/endpoints/ai/agents-api) under the hood, and inherit its permissions, rate limits, and response shapes. Use that reference when you need the full endpoint detail. ## Available Tools The hosted MCP server provides the following tools: | Tool | Purpose | | - | - | | `search_messari_documents` | Search Messari research, news, and curated sources, and return the matching documents | | `query_messari_datasets` | Answer quantitative questions by querying Messari's datasets | | `get_timeseries_catalog` | Discover available datasets, metrics, and granularities from the Messari Timeseries API | | `get_timeseries` | Query timeseries data for crypto assets, protocols, and networks from the Messari Timeseries API | ## The `search_messari_documents` Tool Searches Messari's research, news, and curated sources for documents relevant to a question, and returns the matching documents themselves. It retrieves; it does not write the answer. Your assistant reads the documents and answers from them. `sources` holds the retrieved documents. Each carries a `domain` (`research`, `news`, `external_news`, `diligence`, `governance`, `twitter`, `video_transcript` and others), a `title`, a `url`, the document `content`, and `published_at` where the domain carries a date. `error` is set only when a run finds no usable document, and explains why. The corpus spans years, and the Search agent reads the time window out of your wording. Name concrete dates whenever the question is time-sensitive — "in August 2026" or "since 2026-08-01", not "latest" or "recently". A query with no date returns the best matches from the whole corpus, most of which will be old. ### Example Queries * "What is EigenLayer restaking?" * "Latest news about Ethereum" * "Explain Uniswap v4's new features" * "What happened with FTX?" * "Recent DeFi funding rounds this month" ## The `query_messari_datasets` Tool Answers quantitative questions by translating them into SQL over Messari's datasets and running it. It computes; it does not write the answer. Your assistant reads the rows and answers from them. `results` holds each query the Compute agent ran. `dataset` is the dataset it selected, `query` is the executed SQL, `query_result` holds the rows JSON-encoded as an array of arrays, and `columns` names each position in those rows, which are otherwise unlabelled. `truncated` reports that the row cap was reached, so more rows may match. `query_error` explains why an individual query returned nothing. `error` is set only when a run produces no usable result. A run can take several minutes. The SQL and column names reflect Messari's internal schema, which may change without notice. Read them, do not parse them. ### Example Queries * "What is Bitcoin's current price and 24h volume?" * "Show me the top 10 assets by market cap" * "What is Aave's TVL?" * "When is the next ARB token unlock?" * "Solana daily active addresses this week" ## The `get_timeseries_catalog` Tool Discovers what timeseries data is available through Messari's Timeseries API, including dataset slugs, supported time granularities, available metrics, and entity types. Your assistant uses this to determine what can be queried before fetching data. The datasets returned depend on your subscription tier. ### Example Queries * "What are the available timeseries datasets for DeFi protocols?" * "Which metrics can I get for Ethereum, and at what granularity?" ## The `get_timeseries` Tool Queries timeseries data points for crypto assets, protocols, networks, and more through Messari's Timeseries API. Covers 80+ datasets with configurable time ranges and granularities. ### Example Queries * "What is Bitcoin's daily price over the last 90 days?" * "Show me Ethereum's weekly active addresses for the past year" * "Compare daily trading volumes for Bitcoin and Solana this quarter" * "Get Aave's TVL trend over the last 6 months" ## Data Coverage Real-time prices, volumes, and market caps for 40,000+ crypto assets TVL, active addresses, fees, and transactions for 25+ networks and 200+ protocols Funding rounds, M\&A deals, investors, and company valuations Vesting schedules, allocation breakdowns, and upcoming unlock events Aggregated from 500+ sources with AI summarization Messari's proprietary reports, diligence analyses, and quarterly reviews Social mindshare and sentiment data from X/Twitter Historical and real-time timeseries metrics across 80+ datasets via the Messari Timeseries API ## Best Practices For complex or multi-faceted questions, consider making multiple focused queries instead of one loaded question. Breaking down questions into specific, single-topic calls often yields better depth and accuracy. **Quantitative queries work best when you specify:** * The exact metric (e.g., "TVL", "market cap", "24h trading volume") * The asset or protocol name * Timeframe if relevant (e.g., "last 30 days", "YTD") * Comparison baseline if needed (e.g., "vs last month", "vs Ethereum") ## Troubleshooting ### Authentication Issues **OAuth window doesn't open:** * Ensure your MCP client supports OAuth 2.0 authentication * Check that popups aren't blocked in your browser * Try restarting your MCP client **Invalid API key error:** * Verify your API key at [messari.io/account/api](https://messari.io/account/api) * Ensure your API key has the necessary permissions * Check that your API key hasn't expired ### Connection Issues **Server unreachable:** * Verify your internet connection * Check if `https://mcp.messari.io` is accessible * Try again in a few minutes if there's a temporary outage ### Query Issues **Empty or unexpected responses:** * Try rephrasing your question more specifically * Break complex questions into multiple simpler queries * Ensure you're asking about supported data types **Results are older than expected:** * Name concrete dates in the question. `search_messari_documents` reads the time window out of your wording, and a query with no date searches the whole corpus. **`FORBIDDEN` from the search or dataset tool:** * Your team needs the `ai_toolkit_permission` API permission, shown as **Messari AI API** in team settings. **`RATE_LIMITED` from the search or dataset tool:** * Each tool allows 30 requests per minute per user. Wait for the next minute before retrying. The two tools have separate buckets, so one being limited does not affect the other. ## Support Need help? Contact us: * **Documentation**: [docs.messari.io](https://docs.messari.io) * **API Support**: [messari.io/contact](https://messari.io/contact) * **API Key Issues**: [messari.io/account/api](https://messari.io/account/api) # Quickstart Source: https://docs.messari.io/quickstart Get started with the Messari Typescript SDK in minutes The [Messari Typescript SDK](https://github.com/messari/sdk-ts) provides a type-safe interface for accessing Messari's crypto data and AI services. ## Key Features Full TypeScript support with auto-generated types from OpenAPI specs Built with modern TypeScript features and best practices Comprehensive documentation and examples Intuitive API design with built-in error handling ## Installation ```bash theme={null} # Using npm npm install @messari/sdk-ts # Using pnpm pnpm add @messari/sdk-ts # Using yarn yarn add @messari/sdk-ts ``` ## Authorization You'll need a Messari API key to use the SDK. See our [docs](/api-reference/authentication) for more information. ## API Services Each endpoint in the API has a corresponding method in the SDK. Here are some examples: | API Route | SDK Method | Description | | - | - | - | | `/ai/v1/chat/completions` | `client.ai.v1.chat.generateCompletion()` | AI chat completion using Messari's standard format | | `/ai/openai/chat/completions` | `client.ai.openai.chat.generateCompletion()` | AI chat completion in OpenAI-compatible format | | `/api/v1/assets` | `client.signal.v0.assets.list()` | List all tracked assets | | `/api/v1/assets/{assetId}` | `client.signal.v0.assets.retrieve()` | Get details for a specific asset | For the complete list of available endpoints and methods, please refer to the [API documentation](/api-reference/authentication). ## Example Usage ### AI Chat Completion ```typescript theme={null} import MessariSDK from "@messari/sdk-ts"; // Initialize the client const client = new MessariSDK({ apiKey: process.env["MESSARI_SDK_API_KEY"], }); // Use the AI service const response = await client.ai.openai.chat.generateCompletion({ messages: [ { role: "user", content: "What companies have both paradigm and a16z on their cap table?", MultiContent: [{}], }, ], inlineCitations: true, }); console.log(response.choices[0].message.content); ``` For full examples, see the [Examples section](/examples/overview). # x402 Skill for Claude Code Source: https://docs.messari.io/user-guides/agents/x402-skill-claude-code The official Messari x402 skill for Claude Code allows you to access Messari's data and insights directly from Claude Code authenticated with x402. Answer crypto questions using the Messari API: 34,000+ assets, 210+ exchanges, 14 data services covering market metrics, social sentiment, research, on-chain analytics, fundraising, governance, and more. ## Installation ### 1. Coinbase Payment MCP extension For the best user experience, we recommend installing the Coinbase's Payment MCP extension which provides easy to use hosted wallet with x402 support. Close any open Claude Code sessions and run the following command in your terminal: ```bash theme={null} npx @coinbase/payments-mcp@latest --client claude-code --auto-config ``` Install Command Run the command shown to you. **IMPORTANT:** Double check the quotes when copying the command, it should be ``` // Correct claude mcp add --transport stdio payments-mcp --scope user "COMMAND" "ARGS" // Incorrect claude mcp add --transport stdio payments-mcp --scope user "COMMAND ARGS" ``` Start a Claude Code session and check the status of the MCP server with `/mcp` command, you should see the `payments-mcp` server connected MCP Status ### 2. Authenticate with your x402 wallet Ask Claude Code to open the payments-mcp wallet ``` Open the payments-mcp wallet ``` Payment MCP Wallet Sign In You can then sign into your coinbase account and add USDC to the wallet with the “Fund” or “Receive” buttons. Payment MCP Wallet Fund ### 3. Get the Messari Skill Now that your wallet is ready, you can add the Messari Skill to your `~/.claude/skills/ directory` ```bash theme={null} mkdir -p ~/.claude/skills/messari && curl -o ~/.claude/skills/messari/SKILL.md https://raw.githubusercontent.com/messari/skills/refs/heads/master/SKILL.md ``` Claude Code should now have the Messari Skill available Payment MCP Wallet Sign In ## Usage And now you're ready to ask Messari anything about crypto Messari Skill Answer You'll be prompted to to confirm x402 payment, you can choose "don't ask again" to skip the prompt in the future. Messari Skill Answer Messari Skill Answer # x402 Skill for Claude Desktop Source: https://docs.messari.io/user-guides/agents/x402-skill-claude-desktop The official Messari x402 skill for Claude Desktop allows you to access Messari's data and insights directly from Claude Desktop authenticated with x402. Answer crypto questions using the Messari API: 34,000+ assets, 210+ exchanges, 14 data services covering market metrics, social sentiment, research, on-chain analytics, fundraising, governance, and more. ## Installation ### 1. Coinbase Payment MCP extension For the best user experience, we recommend installing the Coinbase's Payment MCP extension which provides easy to use hosted wallet with x402 support. Close Claude Desktop if it is open and run the following command in your terminal ```bash theme={null} npx @coinbase/payments-mcp@latest --client claude --auto-config ``` Install Command Reopen Claude Desktop and in `Settings -> Developer` you should see the `payments-mcp` listed under "Local MCP Servers" Claude Desktop Setting ### 2. Authenticate with your x402 wallet In a new chat, ask Claude ``` Open the payments-mcp wallet ``` Payment MCP Wallet Sign In Sign with your coinbase email and your wallet is ready to use. Add USDC to the wallet with the "Fund" or "Receive" buttons Payment MCP Wallet Fund ### 3. Get the Messari Skill Now you’re all set wallet wise, we need to install the Messari Skill * Download this [messari.skill](https://github.com/messari/skills/raw/refs/heads/master/claude/messari.skill) file * Click the file to open it with Claude Desktop * Click "Add to Library" Add to Library Messari Skill Answer ## Usage And you’re done! You can now ask Messari anything about crypto directly from Claude Messari Skill Answer Messari Skill Answer # x402 Skill for OpenClaw Source: https://docs.messari.io/user-guides/agents/x402-skill-openclaw The official Messari skill for OpenClaw allows you to access Messari's data and insights directly from OpenClaw authenticated with x402 or a Messari API key. Answer crypto questions using the Messari API: 34,000+ assets, 210+ exchanges, 14 data services covering market metrics, social sentiment, research, on-chain analytics, fundraising, governance, and more. ## Prerequisites For Authentication you'll need either a wallet with USDC on Base for x402 or a Messari API key. ## Installation ### 1. Install the Messari Skill Add the Messari Skill to your OpenClaw project. In the project directory, run the following command: ```bash theme={null} mkdir -p skills/messari && curl -o skills/messari/SKILL.md https://raw.githubusercontent.com/messari/skills/refs/heads/master/openclaw-skill/SKILL.md ``` Install Command ### 2. Add the environment variables Next in your openclaw\.json file, add the respective environment variables for your authentication method. X402\_PRIVATE\_KEY: The private key of your x402 wallet. MESSARI\_API\_KEY: The API key of your Messari account. ```bash theme={null} nano ~/.openclaw/openclaw.json ``` ```json theme={null} { "skills": { "install": { "nodeManager": "npm" }, "entries": { "messari": { "enabled": true, "env": { "X402_PRIVATE_KEY": "" // Add this for x402 authentication, add MESSARI_API_KEY instead for API key authentication } } } } } ``` Restart OpenClaw to apply the changes. And check that the skill is installed. OpenClaw Skill Installed ## Usage And now you're ready to ask Messari anything about crypto. Messari Skill Answer Messari Skill Answer # Assets Source: https://docs.messari.io/user-guides/datasets/assets # **Assets Dataset Overview** Messari's Assets Dataset provides quick and easy access to all of the assets Messari tracks. With filtering and grouping capabilities, custom views, and useful side bar preview panels, you can quickly explore and compare crypto assets. This page includes a step-by-step guide on getting the most from Messari's **Assets Dataset**. # **Access Assets** Access the full list of the assets tracked by Messari by navigating to the `Datasets` tab and selecting `Assets`. Screenshot 2025-09-19 at 12.33.58 PM.png # **Pre-Built Datasets & Views** ## **Datasets** Messari offers pre-built datasets that group assets sharing common themes. You can access these datasets using the left side navigation menu. By default, the Assets dataset opens with the **All** dataset which includes all tracked assets. **Additional curated datasets include:** DeFi, Network Tokens, Exchange Tokens, Stablecoins, Currencies, Metaverse and Gaming, Scaling Solutions, Interoperability, Lending Tokens, Privacy Coins, DePin, Governance Tokens, AppChains, Memecoins, Artificial Intelligence, and Derivatives. Screenshot 2025-09-19 at 1.39.12 PM.png ## **Views** There are 5 pre-built views to highlight specific information about a dataset. Screenshot 2025-09-19 at 1.39.34 PM.png These views cannot be customized directly, but they can be re-created using the [Asset Screener](https://docs.messari.io/user-guides/messari-features/asset-screener) tool for advanced filtering and customization. The **Overview** view, which opens by default, includes metrics such as: * Price performance over multiple time periods * 30-day price trendline * Marketcap * 24H real volume * Sector Other available views: * **Long-Term ROI**: Metrics such as ATH, price changes over 90 days to 5 years, and % down from ATH. * **Calendar Years ROI**: Price changes and performance metrics for the last 6 years. * **Volume**: Information on trading volume, exchanges, and markets. * **Classifications**: Data on networks, categories, sectors, and tags. # **Sort & Filter Assets** Users can sort and filter asset datasets to narrow down their search. The average or total sum for each metric is provided in the last row. Hover over each metric to learn more about it and how it was calculated. ## **Sort** The Assets dataset is, by default, sorted by Current Marketcap. There are several other sortable columns. Click the column's header to sort by that metric. ## **Filter** Use the dropdown filters at the top of the dataset to filter by category, sector, tag, exchange, network, marketcap, and/or 24H volume. Narrow your search further by using the search bar to look for specific assets. # **Group Assets** The Grouping feature allows users to easily compare the performance of sectors, networks, and other attributes that Messari has classified through tags to identify different trends across assets. [You can learn more about Messari's Classification System here.](/glossary/classification-system) Click the `Group` toggle to begin. Group assets by `Category`, `Sector`, `Networks`, or `Tags` and view aggregate quantitative metrics for the resulting groups. Click into each group to view its constituent assets. **Note:** Previously applied filters will affect the grouping results. Clear filters to include all tracked assets in the group metrics. Screenshot 2025-09-19 at 1.40.08 PM.png Once you've grouped your dataset, change the groupings by clicking the `⌵` icon next to `Grouped by [current group]` in the top right-hand corner. Turn off Groups using the toggle. Screenshot 2025-09-19 at 1.40.40 PM.png # **Learn More About an Asset** Click on an asset's name to open the side bar preview panel, which contains a price performance chart, project summary, and links to external resources. Scroll through assets using the `^` and `⌵` icons or click `View Asset Page` to open its [Project Page](https://docs.messari.io/user-guides/messari-features/project-page) in an adjacent tab. Enterprise users can overlay Notable Events to see the price reaction on the price chart. Click on the event link to learn more about it. [Learn more about Notable Events here.](https://docs.messari.io/user-guides/intel/key-developments) Screenshot 2025-09-19 at 1.41.02 PM.png # **Share & Download Asset Data** ## **Share** To share an asset's Project Page, click the `Share` icon in the preview panel. ## **Download** Enterprise users can export datasets by clicking the `Download` icon in the right-hand corner. * **Export ungrouped data**: Choose a pre-built view to export the dataset. * **Export grouped data**: Select how you want the data grouped and whether to export aggregate group metrics or data for specific groups and their constituent assets. Screenshot 2025-09-19 at 1.41.30 PM.png # **Hot Tips & Best Practices** * **Grouping filtered results**: Filters applied before grouping will impact the results, so make sure to clear filters for full dataset metrics. * Utilize the pre-built, curated datasets in the left-side navigation menu for a quick review of assets that share a particular theme. * The [Asset Screener](https://docs.messari.io/user-guides/messari-features/asset-screener) tool provides the most advanced filtering capabilities. * Reference the [Messari Classification System](/glossary/classification-system) to better understand how assets are categorized. * Keyboard Shortcuts in preview panel: * Previous asset `K` * Next asset `J` * Close preview panel `Esc` *** # **Datasets FAQs** ### **Can I save the filters and groups I've applied to an Asset dataset?** You cannot save customizations made to an Asset dataset. Use the [Asset Screener tool](https://docs.messari.io/user-guides/messari-features/asset-screener) to create and save custom filters and views. ### **How can I compare Network data across chains?** The [Networks Dataset](https://docs.messari.io/user-guides/datasets/networks) allows you to compare key metrics across supported networks in either the table or chart format and over various timespans. With the Network dataset, you can analyze performance differences and identify trends across the blockchain ecosystem. ### **Which exchanges does Messari track?** To view the full list of centralized (CEXes) and decentralized exchanges (DEXes) that Messari tracks, navigate to the `Datasets` tab in the top menu and select `Exchanges`. Learn more about Messari's Exchanges Dataset [here](https://docs.messari.io/user-guides/datasets/exchanges). ### **How up-to-date is the trading activity that Messari tracks?** Messari aims to provide users with accurate and up-to-date trading data. On an exchange's [Exchange page](https://docs.messari.io/user-guides/datasets/exchanges) or All Markets page, users can quickly determine whether a unique asset pair's data is live, stale, or inactive thanks to the `Liveness` icon adjacent to the pair's name. Trading data can be either live, stale or inactive: * **Live:** Messari has received trades from this market within the last 10 minutes * **Stale:** Messari has not received a trade from this market over the last 10 minutes, but it has traded over the last 24 hours * **Inactive:** Messari has not received a trade from this market in over 24 hours ### **How can I learn more about Messari's taxonomy and methodology?** Please visit the [Messari Classification System](/glossary/classification-system) page for mapping across Categories, Sectors, and Tags. For Fundraising-specific mapping, such as Type and Stage, please visit the [Fundraising Data Methodology](/glossary/fundraising-taxonomy) page. Market Data methodology and definitions can be found [here](/glossary/data-metrics/asset-metrics-definitions). # Ecosystems Source: https://docs.messari.io/user-guides/datasets/ecosystems # **Ecosystems Dataset Overview** Use Messari's Ecosystems Dataset to explore entities, assets, and investors across chains. With pre-built views, custom filtering, and useful preview panels, users can deep-dive into a network's projects and investors to learn more about what's being built and who's funding what. This page includes a step-by-step guide on getting the most from Messari's **Ecosystems Dataset**. # **Access Ecosystems** Access the Ecosystems Dataset by going to the `Datasets` tab and selecting `Ecosystems`. Screenshot 2025-09-19 at 12.51.37 PM.png # **Datasets & Views** ## **Choose an Ecosystem** The Ecosystems Dataset is categorized by network and opens, by default, in the Ethereum Ecosystem. Additional networks are located in the left-side navigation menu. Screenshot 2025-09-19 at 12.51.56 PM.png ## **Choose a Dataset** Each ecosystem features 3 datasets that cover: * Assets * Investors * Funded Entities Each dataset covers a variety of related metrics. Learn more about Messari's [Fundraising Methodology](/glossary/fundraising-taxonomy) and [Classification System](/glossary/classification-system) here. Screenshot 2025-09-19 at 12.52.14 PM.png ### **Assets** Each ecosystem's Assets dataset includes 5 pre-built views that highlight specific information. These views cannot be customized directly, but you can re-create them using the [Asset Screener](https://docs.messari.io/user-guides/messari-features/asset-screener) tool for more flexibility. The Assets dataset opens in the **Overview** view by default, which contains metrics such as: * Price performance over multiple time periods * 30D price trendline * Marketcap * 24H real volume * Sector Screenshot 2025-09-19 at 12.52.34 PM.png Additional views: * **Long-Term ROI**: Metrics like current price, ATH, % down from ATH, 90D price change, 180D price change, 1Y price change, 3Y price change, and 5Y price change. * **Calendar Years ROI**: Current price, current marketcap, YTD price change, and price change metrics for each of the previous 6 years. * **Volume**: Current marketcap, exchanges traded (the exchanges the asset is traded on based on the exchanges Messari tracks data from), 24H real volume, 7D real volume, 30D real volume, YTD real volume, YTD trendline for real volume, and markets (the number of markets the asset is traded in). * **Classifications**: Current price, current marketcap, exchanges traded, asset networks, category, sector, and tags. ### **Investors** The Investors dataset contains data on investors in a Network and its associated projects. Metrics include: * Investor Name * Investment Count * Co-investors * Most Common Investment Type * Most Common Investment Sector * Median Round Amount * Last Investment and Last Investment Date * First Investment and First Investment Date, * LPs ### **Funded Entities** The Funded Entities dataset provides information on network entities that have received funding. Metrics include: * Funded Entity * Total Amount Raised * Latest Round Type and Date * Investors * Category * Sector * Tags # **Sort & Filter Data** ## **Sort** You can sort assets, investors, and funded entities by clicking column headers. By default, the datasets are sorted as follows: * **Assets**: Current Marketcap * **Investors**: Investment Count * **Funded Entities**: Total Amount Raised ## **Filter** Each dataset can be filtered using dropdown filters at the top of the page. You can narrow your results further by using the search bar to look for specific assets, investors, or entities. * **Assets** filters: Category, Sector, Tag, Exchange, Marketcap, 24H Volume. * **Investors** filters: Type, Country, Most Common Investment Type. * **Funded Entities** filters: Category, Sector, Tag, Round Type. # **Learn More About an Asset, Investor, or Funded Entity** Click on an asset, investor, or funded entity in the dataset to open its preview panel. Use the `^` `⌵` icons to scroll through assets, investors, or entities without having to close the preview panel, or click on `View Asset Page` or `View Fundraising Page` to open its associated [Project page](https://docs.messari.io/user-guides/messari-features/project-page) or [Fundraising page](https://docs.messari.io/user-guides/fundraising/funding-rounds) in an adjacent tab. ## **Assets** An asset's preview panel includes links to its asset project page, and also includes a TradingView chart integration, a brief project summary, and links to external resources. Enterprise users can overlay Key Developments to see the price reaction on the price chart. Click on the event link to learn more about it. Learn more about Notable Events [here.](https://docs.messari.io/user-guides/intel/key-developments) ## **Investors** The investor preview panel provides a brief description, as well as data on publicly available information such as Investment Count, Most Common Stage, and Median Round Amount. Scroll down to view recent closed rounds, and use the links at the top for access to the investor's website and socials. ## **Entities** The preview panel for funded entities displays a brief description and information such as Latest Round, Total Amount Raised, Sector, and Industry. Scroll down to see recent closed rounds, and use the links at the top for access to the entity's website and socials. # **Share & Download Ecosystem Data** ## **Share** In the preview panel for assets, you can share a link to the asset's Project Page by clicking the `Share` icon in the right-hand corner. ## **Download** Enterprise users can export datasets for assets, investors, and/or funded entities by clicking the `Download` icon in the right-hand corner. # **Hot Tips & Best Practices** * Messari's Screener tool offers the most advanced filtering capabilities. Use it to create custom filters by network, then set up customized columns and views for further exploration. Check out Messari's [Asset Screener](https://docs.messari.io/user-guides/messari-features/asset-screener) and [Fundraising Screener](https://messari.io/screener/funding-round) to learn more. * Reference the [Messari Classification System](/glossary/classification-system) to better understand how categories, sectors, and tags are classified. * Keyboard Shortcuts in preview panel: * Previous asset/investor/entity `K` * Next asset/investor/entity `J` * Close preview panel `Esc` # Exchanges Source: https://docs.messari.io/user-guides/datasets/exchanges # **Exchanges Dataset Overview** Explore crypto exchanges and their markets with Messari's Exchanges Dataset. All of the centralized and decentralized exchanges that Messari tracks trading data from can be seen and filtered for. You can learn more about how we process trading data on our [Market Data Methodology](https://docs.messari.io/glossary/data-metrics/market-data-service) page. This page includes a step-by-step guide on getting the most from Messari's **Exchanges Dataset**. # **Access Exchanges** To view the full list of centralized (CEXes) and decentralized exchanges (DEXes) that Messari tracks, navigate to the `Datasets` tab and select `Exchanges`. Screenshot 2025-09-19 at 12.36.10 PM.png To view a specific exchange's Exchange Page, click on its name throughout the platform, or go to the `Exchanges` section of a Project page. learn more about Project pages [here](https://docs.messari.io/user-guides/messari-features/project-page). You can also view a specific asset's markets directly from its Project page by clicking on the `Markets` section in the left-side navigation menu. This allows you to see all the exchanges where the asset is traded or to filter for a specific exchange. # **Pre-Built Views** The Exchanges dataset offers 3 views for easy viewing of **Decentralized** exchanges (DEXes), **Centralized** exchanges (CEXes), and **All** exchanges (default view). These views are accessed using the left-side navigation menu. At the top, users will find specific metrics such as the total number of centralized and decentralized exchanges tracked, total 24H trading volume, and % change in 24H trading volume compared to the previous 24 hours. **Note:** Decentralized Exchanges are split by protocol, and one DEX project (ex: Uniswap) can contain several distinct exchanges (ex: Uniswap v2, Uniswap v3). For DEXes, swaps in both directions are normalized to a single base/quote pair. # **Sort & Filter for Exchanges** The Exchanges dataset includes the following metrics: * 24H Total Spot Volume across all markets that Messari tracks (sorted by default) * % Change in 24H Volume * Markets: Unique asset pairs listed on exchange and tracked by Messari * Assets: Unique assets supported by exchange and tracked by Messari * 24H Total Spot Volume (Time-series) * Market Share: % of total crypto spot volume tracked by Messari * Country: Country of incorporation for Centralized Exchanges * Region: Geographic region * Type: Centralized/Decentralized * First Trade: Date of earliest recorded trade on exchange as tracked by Messari Sort the dataset using the columns above. Filter the list of exchanges using the Search Bar and dropdown filters at the top of the table. # **Learn More About An Exchange** ## **Exchange Page** Messari's Exchange Page (or Exchange Overview) provides a deep-dive view on a specific exchange. Click on an exchange's name throughout the platform to navigate to its Exchange Page. The Exchange Page contains the following information: * Brief summary * Links to external resources * Rankings in terms of volume among exchanges Messari tracks * Sector marketshare heatmap with customizable views and timeframes * MessariAI-generated 30-day Exchange Recap * New listings * Unique Asset Pairs and access to the exchange's All Markets page * Related exchanges To learn more about the company behind the exchange, use the left-side navigation menu to explore Investor, Entity, and Asset-related data, if available. Learn more about Project Pages [here](https://docs.messari.io/user-guides/messari-features/project-page). Throughout the Exchange page, users can quickly determine whether a unique asset pair's data is live, stale, or inactive thanks to the `Liveness` icon adjacent to its name: * **Live:** Messari has received trades from this market within the last 10 minutes * **Stale:** Messari has not received a trade from this market over the last 10 minutes, but it has traded over the last 24 hours * **Inactive:** Messari has not received a trade from this market in over 24 hours ### **Exchange Recap** The Exchange Recap provides a Messari AI-generated summary of exchange-related news and events that have taken place over the last 30 days. Click `Full Exchange Recap` to open it, and dive into a 30D Recap Overview, as well as a timeline of events. All Recaps provide links to original sources for further reading. A555dee50fe1e30946eba1976bc2325df591f4c1bf7e39fdf6015c86bd8c9be0 Exchange Page Exchange Recapgif Ezgif Com Video To Gif Converter(2) Gi ### **Sector Marketshare Heatmap** The Sector Marketshare heatmap illustrates the volume of all assets grouped by Sector as a % of total exchange volume. Adjust its timeframe by clicking `Timespan`. Options include 24H, 7D, or 30D (default). You switch the scale from `Linear` to `Logarithmic` at the top of the heatmap. The Linear scale displays sector sizes as a % of total exchange volume, while Logarithmic (base 10) amplifies smaller sectors for better visibility. Learn more about Messari's Classification System, specifically for Sectors, [here](/glossary/classification-system). ### **New Listings** The New Listings section provides the 6 newest trading pairs added to the exchange, starting with the most recent. Information includes: * Token pairs (clicking on a token's ticker will open its associated side bar preview panel) * The pair's total 24H volume (which is continually updated) * Listing date (e.g., "1 day ago") ### **Markets** The Markets section displays unique asset pairs on the exchange. Search for pairs using the search bar at the top of the table. **Note:** For DEXes, swaps in both directions are normalized to provide a single base/quote pair. The following information is provided for each pair: * Unique asset pair (clicking on a token's ticker will open its associated side bar preview panel) * Price: Last traded price of asset pair on the exchange, denominated in USD * 24H Performance Component: Summary of market performance over the past 24 hours (hover over the data to see high, low, opening, current price, and % price change) * 24H Total Spot Volume * Volume on Exchange: % of total exchange volume traded by this asset pair To view all of an exchange's market pairs on the exchange's All Markets page, click `See All Markets` at the bottom of the table. ### **All Markets Page** The Exchange page's All Markets page offers a closer look at all of the pairs trading on an exchange that Messari tracks. In addition to important metrics about the exchange's 24H trading volume, it also offers links to external resources and the ability to quickly copy or share a link to the exchange's Exchange page using the `Share` icon. The exchange's trading pairs are, by default, sorted by 24H Volume. Metrics include: * Unique asset pair (clicking on a token's ticker will open its associated side bar preview panel) * Price: Last traded price of this asset pair on exchange, denominated in USD * 24H Performance Component: Summary of market performance over the past 24 hours (hover over the data to see high, low, opening, current price, and % price change) * 7D Price Graph: Market price time-series over last 7 days * 24H Total Spot Volume (sorted by default) * % Change in 24H Volume * Volume on Exchange: % of total exchange volume traded by this asset pair * Premium/Discount: % difference between the price of the base asset in the asset pair, and the [VWAP asset price](/glossary/data-metrics/asset-metrics-definitions) for the base asset. A Positive number means this market is trading at a premium over the VWAP asset price. A Negative number means this market is trading at a discount * First Trade: Date of earliest recorded trade on exchange as tracked by Messari. “New” markets have a first trade date that is within the last 24 hours * Liveness: Indicates whether a unique asset pair's trading data is live, stale, or inactive * Recently Listed: Indicates asset pairs added to the exchange over the last 7 days You can sort by any of the columns mentioned above. Filter for pairs by asset/ticker name in the search bar, or use the dropdown filters for Liveness, First Trade, and Listed (was it recently listed?) at the top of the table. ### **Related Exchanges** Explore additional exchanges that are also centralized or decentralized using the options in the Related Exchanges section. # **Share & Download Exchange Data** To share exchange data, click the `Share` icon in the top right corner of an exchange's Exchange page or All Markets page. You can copy the link or share it on Reddit, X (formerly Twitter), LinkedIn, or Facebook. Enterprise users can export their dataset by clicking the `Download` icon in the top right corner of the Exchanges Dataset. *** # **Hot Tips & Best Practices** * Review our [Market Data Methodology](https://docs.messari.io/glossary/data-metrics/market-data-service) to understand how Messari defines and tracks market data. * Click on a column or section header's tooltip `i` icon for more information on that metric. 93042a36c517eb807d03c6312cfc6106d03be66a0c5fcf03e569ffa3c35f0411 Screenshot 2024 09 28 At 6 36 14 AM Pn * Quickly learn more about an asset by clicking on its name or ticker throughout the platform. This opens the asset’s preview panel where you can get a quick description, links to external resources, and access to its full [Project page](https://docs.messari.io/user-guides/messari-features/project-page). * View an asset’s or exchange's markets directly from its Project page by clicking on the `Markets` or `Exchanges` section in the left-side navigation menu. For example, see Bitcoin's Markets page [here](https://messari.io/project/bitcoin/markets) and Uniswap V3's Exchange page [here](https://messari.io/exchange/uniswap-v3). Note that DEXes are split by protocol, and one DEX project (ex: [Uniswap](https://messari.io/project/uniswap)) can contain several distinct exchanges (ex: [Uniswap V2](https://messari.io/exchange/uniswap), [Uniswap V3](https://messari.io/exchange/uniswap-v3)). * Keyboard Shortcuts in preview panel: * Close preview panel `Esc` *** # Networks Source: https://docs.messari.io/user-guides/datasets/networks # **Networks Dataset Overview** The Networks Dataset allows users to explore metrics for all of the top networks. Quickly browse metrics in tables, visualize trends in charts, and deep-dive into an individual network to learn more about its on-chain usage, activity, and growth. This page includes a step-by-step guide on getting the most from Messari's **Networks Dataset**. # **Access Networks** To view the full list of the networks Messari tracks data from, go to the `Datasets` tab and select `Networks`. You can also access specific network data directly from the [Project Page](https://docs.messari.io/user-guides/messari-features/project-page) by clicking on `Network Fundamentals` and `Statements` in the left-side navigation menu. Screenshot 2025-09-19 at 12.46.40 PM.png # **Pre-Built Views** ## **Tables & Charts** Messari's Networks Dataset can be viewed in a tabulated (table) or chart format. ### **Table Format** The Networks dataset opens, by default, in the Table format with the pre-built **Key Metrics** view, which includes metrics on such as: * Transactions and transaction fees * Average daily active addresses * Circulating marketcap Screenshot 2025-09-19 at 12.47.50 PM.png Additional views include: * **Usage**: transactions and transaction fees, average daily active addresses, average daily new addresses, and average daily returning addresses * **Contracts**: total contract calls, new contracts deployed, average daily active contracts, average daily new contracts called, average daily returning contracts called, and average daily unique contract callers At the bottom of each table is a **Total** column which provides the total of each column's metric across all tracked networks. Note that **Other Networks** is an aggregated group of networks which Messari doesn't yet fully support. Hover over this group's associated tooltip icon to see which networks are included. ### **Chart Format** Switch to the Chart format by selecting `Charts` in the upper left corner. The Chart format includes the same data as that found in the Table format, divided into sections such as: * **Key Metrics**: circulating marketcap, transaction fees, daily transactions, daily active addresses, TVL, stablecoin marketcap, and DEX volume * **Usage**: new and returning addresses, successful transactions, and unsuccessful transactions * **Contracts**: total contract calls, new contracts deployed, active contracts, new contracts called, returning contracts called, and unique contract callers Hover over the tooltip `i` icons to learn more about the metrics being measured. You can also interact with the charts by highlighting or excluding networks using the chart’s interactive legend. Screenshot 2025-09-19 at 12.48.23 PM.png # **Sort & Filter Networks** ## **Sort** In the Table format, the Networks dataset is sorted by 30D Transaction Fees by default. You can click on column headers to sort by other metrics. ## **Filter** You can filter networks in both the Table and Chart formats using the following methods: ### **Table Format Filters:** * **Search Networks**: Search by network name or use the dropdown menus for assets and watchlists. * **Timespan**: Use the `Span` dropdown to filter data by timespan. It begins on 30D by default. Other options include 7D, 90D, 180D, 1Y, and 3Y. ### **Chart Format Filters:** * **Select Networks**: The charts include 5 networks by default. Add or remove networks using the dropdown or the `x` icon next to a network's name. * **Timespan**: As with the table format, filter data by timespan using the `Span` dropdown. * **Chart-specific filters** Click on a network name in the legend to include or exclude it from a chart. # **Learn More About a Network** In Table format, click on a network’s name to open the preview panel, which includes important 30D change metrics and charts. Use the `^` `⌵` icons to scroll through networks, or click `View Network Page` to open its Networks Fundamentals page in an adjacent tab. Screenshot 2025-09-19 at 12.49.04 PM.png # **Share & Download Network Data** ## **Share** Click the `Share` icon in the right-hand corner of the preview panel to copy or share a link to the network's Networks Fundamentals page. ## **Download** Enterprise users can export their dataset in the Table format by clicking the `Download` icon in the top right corner. *** # **Hot Tips & Best Practices** * Use the tooltip `i` icons next to column headers or chart titles for additional details. * You can access a network’s data from its [Project Page](https://docs.messari.io/user-guides/messari-features/project-page) by clicking on [Network Fundamentals](https://messari.io/project/ethereum/network-metrics) and [Statements](https://messari.io/project/ethereum/statements). * The average or total sum for each metric is provided in the last row in the Table format. * **Other Networks** includes networks that Messari does not fully support. Hover over its tooltip `i` icon for more details. * Keyboard shortcuts in preview panel: * Previous asset `K` * Next asset `J` * Close preview panel `Esc` # Token Unlocks Source: https://docs.messari.io/user-guides/datasets/token-unlocks # **Token Unlocks Overview** Messari's Token Unlocks allows users to easily explore, compare, and analyze token unlock data. Key features include initial allocations and vesting schedules, historical unlocks overlayed with a price chart, separate categories for Cliff Unlocks versus Daily Emissions, Messari AI-generated insights, and allocation analysis on top protocols and sectors. Messari provides Token Unlocks data on more than 150 tokens. The team regularly adds new tokens to its list of coverage. This page includes a step-by-step guide on getting the most from Messari's **Token Unlocks**. For asset-specific token unlock deep dives, please visit the [Token Unlocks](https://docs.messari.io/docs/project-page#token-unlocks) section of the asset's Project Page. *** # **Token Unlocks Video**