# Messari Network Metrics Daily Time-Series

> Messari Network Metrics Daily Time-Series is a paid API for AI agents from api.messari.io, paid per call via x402, $0.15/call, status unknown (last checked 2026-09-15).

Returns daily historical time-series data for a specified blockchain network metric, enabling trend analysis and long-horizon agent memory.

## Facts

- Endpoint: GET https://api.messari.io/metrics/v2/networks/*/metrics/*/time-series
- Price: $0.15/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/messari-network-metrics-daily-time-series-3c0e4f6a
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Em7_qJ1lIDD4_GNRD7GzG

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability messari-network-metrics-daily-time-series-3c0e4f6a
```

Example prompt: Pull the daily transaction count history for Ethereum from Messari from January 1 2024 to June 30 2024 — I want to see the full trend over that six-month window.

## When to prefer this

Use this endpoint when you need long-horizon, daily-granularity on-chain metrics for a blockchain network (e.g. Ethereum, Solana, Bitcoin) for trend analysis, backtesting, or building agent memory. Prefer this over the hourly or sub-hourly variants when you need historical breadth rather than intraday precision, and over asset/stablecoin endpoints when the subject is a network rather than a token.

## Known failure modes

- Unknown entityIdentifier returns 404 or empty data
- Invalid or unsupported datasetSlug returns an error or empty series
- Date range outside available history returns partial or empty data
- Missing required fields (entityIdentifier or datasetSlug) returns 400 validation error
- Payment failure (x402) blocks the request before data is returned
- Unsupported granularity value returns an error

## How this service works

Get daily blockchain network metric history for trend analysis and agent memory.

## Output

An array of timestamped data points, each containing a UTC timestamp (ISO-8601) and a numeric metric value, covering the requested date range at daily (1d) granularity for the specified blockchain network and metric slug.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "entityIdentifier",
  "datasetSlug"
 ],
 "properties": {
  "end": {
   "type": "string",
   "description": "ISO-8601 or YYYY-MM-DD end time."
  },
  "start": {
   "type": "string",
   "description": "ISO-8601 or YYYY-MM-DD start time."
  },
  "datasetSlug": {
   "type": "string",
   "description": "Metric dataset slug to fetch (for example \"tx_count\"); available slugs come from GET /metrics/v2/networks/metrics."
  },
  "granularity": {
   "type": "string",
   "description": "Sampling interval for the timeseries route variant; priced granularities are 1d, 1h, 15m, and 5m."
  },
  "entityIdentifier": {
   "type": "string",
   "description": "Network identifier to query timeseries for (use the same id or slug format accepted by Metrics V2, for example \"ethereum\")."
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "example": {
  "data": [
   {
    "value": 0,
    "timestamp": "2025-01-01T00:00:00Z"
   }
  ]
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/messari-network-metrics-daily-time-series-3c0e4f6a/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.messari.io](https://www.zero.xyz/host/api.messari.io/llms.txt)