# Onvexia Blockchain Asset Metrics Timeseries

> Onvexia Blockchain Asset Metrics 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).

Returns historical timeseries data for a specific blockchain asset's on-chain metrics, covering price, supply, age, and analytics signals over time.

## Facts

- Endpoint: GET https://onvexia.com/v1/metrics/%7Bslug%7D/timeseries
- 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-blockchain-asset-metrics-timeseries-0cacbd50
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_piNZv_tIrUQl0aSMzGkh_

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-blockchain-asset-metrics-timeseries-0cacbd50
```

Example prompt: Pull the historical on-chain metrics timeseries for Bitcoin from Onvexia — I want to see how its supply and age distribution have changed over time.

## When to prefer this

Choose this endpoint when you need structured historical timeseries data for a specific blockchain asset's on-chain metrics, especially when you require deep historical coverage (back to 2008), multi-chain support across ten networks, labelled address data, or supply-age history. Prefer over generic price APIs when on-chain analytics depth matters. The x402 micropayment model at $0.001 per call makes it cost-effective for per-asset lookups.

## Known failure modes

- Invalid or unknown asset slug returns empty data array
- Missing required slug path parameter returns 400 or 404
- Payment failure (x402) returns 402 Payment Required if USDC microtransaction not completed
- Rate limiting may occur for high-frequency calls
- Chain not in the supported ten-chain set returns no data
- Extremely early dates pre-asset-genesis return empty timeseries

## 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 timestamped metric values for the requested asset slug, plus a 'meta' object with documentation URL and endpoint reference. The timeseries spans historical data potentially reaching back to 2008, covering on-chain signals such as supply, age distribution, and labelled address activity.

## 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"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/onvexia-blockchain-asset-metrics-timeseries-0cacbd50/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)