Which legacy endpoints provide Basic research reports?

Basic research has dedicated report-list and report-by-ID operations in the legacy API. The separate Research group includes report retrieval and report-tag operations. These groups distinguish the research content that the operations address. Their presence in the documentation does not establish that a Basic account includes every research endpoint or Enterprise research content.

Are fundraising CSV exports automatic with API access?

Enterprise fundraising CSV exports are available on request. The pricing comparison lists the Fundraising API separately as a custom API package. A requested export and programmatic API access are different delivery methods, so an export allowance does not establish access to the API. For API-key access, the package determines the included operations; selected legacy Fundraising endpoints also offer x402 access.

Does every legacy protocol metric also appear in the application?

The legacy Protocols API includes data that the documentation identifies as unavailable in the application interface. Its examples include total value locked, active addresses, deposits or borrows and trading volume. This describes a difference in coverage between the API and interface. Access to those API measurements still follows the applicable data package.

How can applications retrieve bulk datasets from the legacy API?

The Bulk API provides operations to list available datasets and download a dataset. This differs from requesting an individual asset record or time series. The dataset listing identifies what that API offers. It does not establish unrestricted access to every dataset or replace the access conditions that apply to the relevant package.

Can an AI assistant connect to Messari data through MCP?

Messari provides hosted and self-hosted MCP options for connecting data to AI assistants. Its developer tooling also lists agent skills. MCP describes an integration method; it does not determine which datasets a subscription includes. When a connection uses the legacy API underneath, that service's maintenance boundary remains relevant to the integration.

Messari API supports existing integrations in maintenance mode

Messari API remains available in maintenance mode for existing integrations that retrieve crypto data. New builds should use the Blockworks API, while the legacy service receives no new endpoints, datasets or features. Its documented families cover market data, onchain metrics, research, news and monitoring. Legacy access depends on API-key permissions or x402 support for the requested endpoint. Existing connections and new projects therefore have different development paths, even when they need similar information about the same asset or protocol.

Updated: Monday 19 October 2026

What does maintenance mode mean for existing integrations?

The legacy API remains supported for existing integrations. Maintenance mode closes development of new endpoints, datasets and features. An established application can retain its connection within that support policy. A requirement for additional capabilities calls for assessing the replacement API.

Messari's transition notice says existing accounts and subscriptions will carry over unchanged to the Blockworks application. It does not establish that legacy API credentials, endpoint addresses or response formats transfer to the replacement.

API keys and x402 provide different access routes

Enterprise users can generate API keys for market data, metrics and asset profiles through their dashboard. Assets & Market Data, Exchanges and Markets also form the legacy API's Enterprise-included families. For API-key access, send the credential in the x-messari-api-key request header; the package determines which data products the subscription includes. A 401 response indicates a missing or invalid key; 403 indicates insufficient permissions. Global and service-specific rate limits both apply. A 429 response indicates rate limiting; retry with exponential backoff.

News, Signals, Diligence, Research, Fundraising, Token Unlocks and the Copilot AI API appear as custom API packages in the pricing comparison. Additional APIs are available as add-ons. Selected legacy endpoints also support x402 payments in USDC on Base Mainnet or Solana Mainnet without a Messari account or API key. For x402, endpoint choice and supported granularity affect the per-request price, while request count affects total API charges. Endpoint support and prices can change. An HTTP 402 response supplies payment options before authorization, including the amount, network and recipient. Keep the required data families explicit when assessing access and cost. An Enterprise website subscription and an additional API package can cover different product scopes. Neither the presence of a feature in the application nor a general statement about API access establishes the price of that additional package.

Which datasets does the legacy service expose?

The legacy API spans market and onchain measurements alongside research, event data and other qualitative records. Asset & Market Data includes asset listings, asset details, metric discovery, all-time highs, return-on-investment data and asset time series. Exchange endpoints cover exchange records and metric time series. Their documented measurements include spot trading volume, futures trading volume and futures open interest. Market endpoints separately cover market records and their time series. These families answer related questions at different levels: an asset, an exchange and a market are distinct objects.

Network endpoints provide network metrics and time series; the Protocols family provides protocol-level measurements. Documented examples include transaction fees and active addresses for networks, plus total value locked, deposits or borrows and trading volume for protocols. Stablecoin endpoints include listings, metric discovery and metric time series. Each family has its own coverage. The measurements available for a network do not establish which fields exist for a particular protocol or stablecoin.

Other families cover research reports, aggregated news, topics, fundraising records and social signals. Signals includes mindshare and sentiment, while fundraising includes funding rounds, mergers and acquisitions, entities and funds. Token Unlocks separates allocations, event records, individual unlocks and vesting schedules. AI endpoints cover Copilot, agents and Deep Research. A scheduled unlock, a funding round and a research report remain different record types when an application combines their information.

Monitoring replaces the earlier Intel interface

Monitoring is the documented replacement for Intel, with separate developments, events and saved monitoring views. Views can use simple filters or prompt-based agentic criteria. Their API operations include listing views and retrieving developments or events that match a view. Intel remains a separate legacy API family. Event status also carries meaning: important events receive analyst verification before publication, while developing events can arrive earlier with underlying source evidence.

Intel event listing has a deprecated GET form and a documented POST alternative.

Time series need the metric and observation period

Time-series queries describe an asset or another supported object through a selected metric over time. The legacy API includes metric discovery and time-series operations, with network and Signals endpoints that explicitly distinguish granularity. Price, trading volume, active addresses and transaction fees measure different things. Their units and observation periods remain part of their meaning when values enter a chart or calculation. Data coverage also belongs to the specific endpoint family. Broad asset coverage does not establish that every asset has every onchain series, research report or monitoring event.

View image file

Request methods distinguish reads from watchlist changes

Watchlist endpoints include retrieval operations and separate methods for creating, updating or deleting a collection. The watchlist API separates GET retrieval, POST creation, PATCH updates and watchlist deletion. Separate update operations address watchlist details and the assets inside the watchlist. Read requests and changes therefore have different effects on stored collections. Version labels matter independently of those methods: the asset documentation also distinguishes an older v1 legacy group. Neither a shared object name nor a familiar HTTP verb makes different API versions interchangeable.

Where should new integration work begin?

New integration work should begin with the Blockworks API. Continued legacy support serves applications that already depend on the earlier interface.

An existing application can retain its legacy connection or evaluate the replacement before changing production requests. Both options need to satisfy the same data requirements under the applicable access conditions. For subscription access, the required data families and any additional API packages affect the access cost. The decision can remain reversible while production requests continue using the existing connection.

Retain the legacy connection when the task uses existing supported operations.
Evaluate the replacement when the application needs new endpoints, datasets or features.
For legacy endpoints beyond included Enterprise data, compare add-ons with x402 where supported.
Keep the production connection unchanged while comparing the required records and field meanings.
Commit to the replacement after its responses meet the data requirements and its access conditions cover the required API families.

Responses containing the required records, with matching units and observation periods, confirm the data side of that choice. The chosen access route must also cover the required endpoints. Retaining the legacy connection preserves the established integration during evaluation; selecting the replacement follows the development path for new integrations.

What readers ask about Messari API

Which legacy endpoints provide Basic research reports?: Basic research has dedicated report-list and report-by-ID operations in the legacy API. The separate Research group includes report retrieval and report-tag operations. These groups distinguish the research content that the operations address. Their presence in the documentation does not establish that a Basic account includes every research endpoint or Enterprise research content.
Are fundraising CSV exports automatic with API access?: Enterprise fundraising CSV exports are available on request. The pricing comparison lists the Fundraising API separately as a custom API package. A requested export and programmatic API access are different delivery methods, so an export allowance does not establish access to the API. For API-key access, the package determines the included operations; selected legacy Fundraising endpoints also offer x402 access.
Does every legacy protocol metric also appear in the application?: The legacy Protocols API includes data that the documentation identifies as unavailable in the application interface. Its examples include total value locked, active addresses, deposits or borrows and trading volume. This describes a difference in coverage between the API and interface. Access to those API measurements still follows the applicable data package.
How can applications retrieve bulk datasets from the legacy API?: The Bulk API provides operations to list available datasets and download a dataset. This differs from requesting an individual asset record or time series. The dataset listing identifies what that API offers. It does not establish unrestricted access to every dataset or replace the access conditions that apply to the relevant package.
Can an AI assistant connect to Messari data through MCP?: Messari provides hosted and self-hosted MCP options for connecting data to AI assistants. Its developer tooling also lists agent skills. MCP describes an integration method; it does not determine which datasets a subscription includes. When a connection uses the legacy API underneath, that service's maintenance boundary remains relevant to the integration.