Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.messari.io/llms.txt

Use this file to discover all available pages before exploring further.

​
Monitoring Overview

Messari’s Monitoring product allows you to create custom views over Messari’s universe of crypto developments and receive alerts when new developments match your criteria. Unlike the standard Key Developments feed, Monitoring views are fully customizable: you can scope them by specific assets, watchlists, ecosystems, sectors, categories, importance levels, and more. Each monitoring view can have one or more alert policies attached to it. Alert policies control how and when you are notified when new developments match the view. This page provides an overview of the Monitoring product and how to use it.

​
Creating a Monitoring View

A monitoring view is defined by a set of predicates that determine which developments match the view. Available predicates include:
  • Assets: filter to specific assets
  • Asset Watchlist: match developments tied to any asset in a watchlist
  • Asset Sectors / Sub-sectors: filter by asset sector classification
  • Ecosystem Networks: match developments for assets in specific ecosystems
  • Pre-TGE: filter for assets that have not yet had a token generation event
  • Categories / Sub-categories: filter by the development’s classification taxonomy
  • Importance: filter by the development’s importance level (low, medium, high)
  • Actionable: filter to only actionable developments
A development matches a view if it satisfies all active predicates on the view.

​
Alert Policies

An alert policy attaches a delivery configuration to a monitoring view. Each policy specifies:
  • View: which monitoring view to subscribe to
  • Cadence: how often to deliver alerts
    • immediately — fire as soon as a matching development is detected
    • daily — batch matching developments into a daily digest
    • weekly — batch matching developments into a weekly digest
  • Delivery Types: one or more of:
    • email — sent to your account email
    • slack — posted to a configured Slack channel
    • web_push — pushed to a registered browser/device
    • webhook — POSTed to an HTTP endpoint you control (see Webhooks)
A single policy can fan out to multiple delivery channels at once. For example, you can create one policy that sends alerts to both an email address and a webhook endpoint.

​
How Alerts Are Delivered

When a new development is published and classified, Messari evaluates it against every active monitoring view. For each view that matches, every active alert policy on that view fires according to its cadence. For immediately cadence, alerts are typically delivered within seconds of a development being matched. For daily and weekly cadences, alerts are batched and sent at the configured digest time. Each delivery attempt is recorded in an audit log so you can verify whether alerts were sent successfully.

​
Deep Dives

Webhooks

Receive monitoring alerts as HTTP POST requests to your own endpoint, with HMAC signature verification and automatic retries.