# Onvexia Asset Holders Endpoint

> Onvexia Asset Holders Endpoint is a paid API for AI agents from onvexia.com, paid per call via x402, $0.001/call, status unknown (last checked 2026-09-17).

Returns the holder distribution and address-level holder data for a specified blockchain asset symbol

## Facts

- Endpoint: GET https://onvexia.com/v1/assets/%7Bsymbol%7D/holders
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-17
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/onvexia-asset-holders-endpoint-cc7714d0
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_2pMNLlqbNZRngUEtHCauM

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-asset-holders-endpoint-cc7714d0
```

Example prompt: Pull up the current holder distribution for ETH — I want to see which addresses are holding the most and whether any labelled wallets like exchanges or funds show up.

## When to prefer this

Choose this endpoint when you need on-chain holder distribution data for a specific asset and want labelled address context (e.g. exchange wallets, known funds) rather than raw address lists. Onvexia covers thousands of assets across ten chains with historical data back to 2008, making it preferable to generic block explorers when you need fused, annotated holder intelligence in a single REST call.

## Known failure modes

- Unknown or unsupported symbol returns empty data array
- Symbol for a chain not among the ten supported chains returns no results
- Malformed symbol path parameter may return 400 or empty response
- Payment failure (x402) if USDC balance is insufficient
- Rate limiting if called excessively without payment
- Response may lag for assets with very large holder sets

## 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 response containing an array of holder records for the requested asset symbol, including wallet addresses (some labelled as known entities like exchanges, funds, or custodians), their balances, percentage of total supply, and associated metadata. The meta field includes a link 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/assets/{symbol}/holders"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/onvexia-asset-holders-endpoint-cc7714d0/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)