# Messari API — Daily Blockchain Network Metric Time-Series (1d)

> Messari API — Daily Blockchain Network Metric Time-Series (1d) 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 (e.g. transaction count, active addresses) over a user-defined date range.

## Facts

- Endpoint: GET https://api.messari.io/metrics/v2/networks/*/metrics/*/time-series/1d
- 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-api-daily-blockchain-network-metric-time-series-1d-1251fb48
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_HUmgbiw3f9pUvVC0K2KxF

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-api-daily-blockchain-network-metric-time-series-1d-1251fb48
```

Example prompt: Pull the daily transaction count history for Ethereum from Messari from January 1 2024 to March 31 2024 — use the tx_count metric slug.

## When to prefer this

Use this endpoint when you need daily-granularity on-chain network metrics for trend analysis, backtesting, or agent memory over multi-day to multi-year horizons. Prefer the 1d route over the generic time-series endpoint when you explicitly want daily data without ambiguity about granularity. Choose this over the 1h, 15m, or 5m sibling endpoints when intraday resolution is unnecessary and cost efficiency matters.

## Known failure modes

- Invalid or unsupported entityIdentifier returns a 404 or empty dataset
- Unknown datasetSlug returns an error or no data — caller should first query the available slugs endpoint
- Date range with no available data returns an empty array
- Malformed ISO-8601 date strings cause a 400 bad request
- Payment not processed (x402) results in a 402 Payment Required response
- Rate limiting or quota exceeded returns a 429 error

## How this service works

Get daily blockchain network metric history via the explicit 1d route.

## Output

An array of daily data points, each containing a UTC timestamp and a numeric metric value, representing the requested blockchain network metric at 1-day granularity over the specified date range.

## 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-api-daily-blockchain-network-metric-time-series-1d-1251fb48/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)