# Onvexia Blockchain Analytics Listings

> Onvexia Blockchain Analytics Listings 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 a list of crypto assets tracked by Onvexia, covering thousands of assets across ten chains with fused analytics including labelled addresses, supply-age history, and document coverage metadata.

## Facts

- Endpoint: GET https://onvexia.com/v1/listings
- 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-analytics-listings-e72335b3
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_VAJaF3H0a-M3IWWlO87aa

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-analytics-listings-e72335b3
```

Example prompt: Show me all the crypto assets Onvexia covers — I want to see which tokens across their supported chains have labelled addresses and supply-age history available.

## When to prefer this

Choose this endpoint when you need to discover or enumerate the full catalogue of crypto assets that Onvexia covers, especially when you want to verify coverage before making per-asset analytics calls. Prefer it over generic token lists when you need assets that specifically have labelled addresses, multi-document analysis, or supply-age history going back to 2008 across ten chains. It is the starting point for any workflow that depends on Onvexia's fused analytics.

## Known failure modes

- Empty data array if no assets match the properties filter
- 402 Payment Required if USDC micropayment is not included or fails
- Invalid properties parameter returns an error or empty result
- Rate limiting if called excessively without valid payment
- Stale or incomplete data for newly listed assets not yet fully indexed

## 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 with a `data` array of asset listing objects and a `meta` object containing documentation URL and endpoint path. Each listing likely includes asset identifiers, supported chain references, document analysis counts, labelled address availability, and supply-age history metadata. The exact fields per listing are detailed in the OpenAPI spec at onvexia.com/openapi.json.

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

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/onvexia-blockchain-analytics-listings-e72335b3/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)