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.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.
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
primaryorsecondary), and a nestedeventreference 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 aggregatedevelopmentCount/documentCount. - Monitoring View. A saved filter over the stream.
simpleviews are deterministic predicates (assets, categories, importance).agenticviews 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 asummary 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./monitoring/v1/*(legacy). Byte-for-byte drop-in replacement for/intel/v1/*. Same paths, parameters, and response shapes under the/monitoringbase. Use only if you are migrating an existing Intel integration and can’t yet adopt v2.
v1 endpoints (legacy)
- Get Assets. Assets that have appeared on at least one intel event.
- Get Event Details. Event with update history.
- List Events. POST form for paginated events with filters.
Use cases
- Risk & response. Feed verified
security_and_hacksdevelopments 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=mediumdevelopments 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=truedevelopments across assets your DAO or treasury cares about.

