# Onvexia Multi-Metric Timeseries

> Onvexia Multi-Metric Timeseries is a paid API for AI agents from onvexia.com, paid per call via x402, $0.001/call, status unknown (last checked 2026-09-19).

Fetches multiple on-chain metrics as time-series data for a specified blockchain asset slug

## Facts

- Endpoint: GET https://onvexia.com/v1/metrics/%7Bslug%7D/timeseries/multi
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-19
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/onvexia-multi-metric-timeseries-0c4be301
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_C2kGJfPMtWEvOL9Gu15Oo

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 onvexia-multi-metric-timeseries-0c4be301
```

Example prompt: Pull the multi-metric timeseries for Bitcoin from Onvexia — I want supply age, labelled address activity, and any document-coverage signals bundled together in one call.

## When to prefer this

Choose this endpoint when you need multiple on-chain metrics for a single asset in a single call, especially when you want fused analytics spanning labelled addresses, supply-age history, and document coverage across up to ten chains. It is particularly valuable when you need historical depth going back to 2008 and want REST access to Onvexia's proprietary analytics layer rather than raw chain data.

## Known failure modes

- Unknown asset slug returns empty data array or 404
- Missing or malformed 'properties' parameter may return empty results
- Payment failure (x402) if USDC balance is insufficient
- Rate limiting if too many requests are made in quick succession
- Unsupported chain or asset may yield no data points

## How this service works

Thousands of assets across ten chains, half a million analysed documents, labelled addresses and supply-age history reaching back to 2008 — fused into one reading per asset. REST, SQL, GraphQL and MCP.

## Output

A JSON object containing a 'data' array of timeseries entries across multiple requested metrics for the given asset slug, plus a 'meta' object with documentation links and endpoint reference. Each data point reflects fused on-chain analytics including labelled addresses, supply-age history, and document-coverage signals.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "properties": {
   "type": "string"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "data": [],
  "meta": {
   "docs": "https://onvexia.com/openapi.json",
   "endpoint": "/v1/metrics/{slug}/timeseries/multi"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/onvexia-multi-metric-timeseries-0c4be301/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from onvexia.com](https://www.zero.xyz/host/onvexia.com/llms.txt)