# Onvexia Category Rankings

> Onvexia Category Rankings 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 ranked list of crypto assets within a specified category, combining on-chain analytics, document analysis, and labelled address data across ten blockchains.

## Facts

- Endpoint: GET https://onvexia.com/v1/categories/%7Bcategory%7D/rankings
- 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-category-rankings-922a0f37
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_khQLBsYlQwj_F1iKzHtXu

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-category-rankings-922a0f37
```

Example prompt: Can you pull the current Onvexia rankings for the DeFi category — I want to see which assets are scoring highest based on their on-chain analytics and document coverage?

## When to prefer this

Choose this endpoint when you need a ranked, analytics-backed comparison of crypto assets within a specific category or sector (e.g. DeFi, gaming, L2), particularly when you want rankings informed by on-chain data, labelled addresses, and document-level research across multiple chains reaching back to 2008 — rather than simple price or market-cap ordering from a generic data aggregator.

## Known failure modes

- Unknown or misspelled category slug returns empty data array
- Invalid category path parameter returns 4xx error
- Payment failure (x402) if USDC not provided blocks access
- Rate limiting if call volume exceeds plan limits
- Stale data if category has not been recently 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 object with a 'data' array containing ranked assets within the requested category, along with 'meta' information including docs URL and the endpoint path. Asset entries likely include scores, chain data, labelled address information, and analytics derived from half a million analysed documents.

## 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/categories/{category}/rankings"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/onvexia-category-rankings-922a0f37/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)