# Onvexia Batch Metrics

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

Retrieves batch blockchain analytics metrics — including on-chain data, labelled addresses, supply-age history, and document-derived signals — for multiple crypto assets in a single call

## Facts

- Endpoint: GET https://onvexia.com/v1/metrics/batch
- 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-batch-metrics-f34fe8f3
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_1tO7wjAs1Lc4ZVEp836gA

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-batch-metrics-f34fe8f3
```

Example prompt: Pull the batch on-chain metrics from Onvexia for BTC, ETH, and SOL — I want their supply-age history and labelled address data fused into one reading per asset.

## When to prefer this

Choose this endpoint when you need analytics for multiple crypto assets in a single round-trip, especially when you want fused readings that combine on-chain data, labelled addresses, supply-age history, and document-derived signals across up to ten chains. Prefer it over single-asset endpoints when batch efficiency matters, and over generic blockchain explorers when you need higher-level analytics rather than raw transaction data.

## Known failure modes

- Empty data array returned if no valid asset identifiers are matched
- Malformed or missing `properties` parameter returns an empty or error response
- Rate limit or payment failure (x402) if USDC payment is not properly attached
- Upstream data gaps for newly listed or obscure assets on less-covered chains
- Partial results if some assets are on unsupported chains

## 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 with a `data` array containing one fused analytics reading per requested asset — covering on-chain metrics, labelled addresses, supply-age history, and document-derived signals — plus a `meta` object pointing to the full OpenAPI spec.

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

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/onvexia-batch-metrics-f34fe8f3/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)