# Onvexia Asset Category Lookup

> Onvexia Asset Category Lookup 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 a list of blockchain assets belonging to a specified category, drawn from Onvexia's multi-chain analytics dataset

## Facts

- Endpoint: GET https://onvexia.com/v1/assets/category/%7Bcategory%7D
- 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-category-lookup-32996bc1
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_fzyUchiZoDarKn0OeYQAi

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-category-lookup-32996bc1
```

Example prompt: Can you pull all the DeFi assets from Onvexia's analytics database for that category and show me what's covered across their ten-chain dataset?

## When to prefer this

Choose this endpoint when you need to enumerate or browse blockchain assets by category across multiple chains using Onvexia's proprietary analytics coverage, especially when you want fused per-asset readings that combine on-chain data, labelled addresses, supply-age history, and document analysis. Prefer this over generic token list APIs when breadth of coverage (ten chains, back to 2008) and analytical enrichment matter more than raw price data.

## Known failure modes

- Invalid or unrecognised category slug returns an empty data array
- Malformed category path parameter may return a 400 or 404 error
- Payment not received (x402 flow incomplete) results in a 402 Payment Required response
- Rate limiting or quota exceeded may return a 429 error
- Empty results if no assets are tagged with the given category in the current dataset

## 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 assets belonging to the requested category, plus a `meta` object with documentation links and the endpoint path. Each asset entry likely includes identifiers, chain associations, and analytics metadata drawn from Onvexia's coverage of thousands of assets across ten chains.

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

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/onvexia-asset-category-lookup-32996bc1/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)