# Onvexia Screener Fields Catalog

> Onvexia Screener Fields Catalog 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 the list of available filterable and sortable fields supported by the Onvexia blockchain asset screener

## Facts

- Endpoint: GET https://onvexia.com/v1/screener/fields
- 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-screener-fields-catalog-66a1fa3f
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_kL3tJPWurQjhIc8Lr7eN0

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-screener-fields-catalog-66a1fa3f
```

Example prompt: What fields can I use to filter and sort crypto assets in Onvexia's screener — I want to know all the available dimensions like supply age, labelled addresses, and on-chain metrics before I build a query.

## When to prefer this

Use this endpoint as a prerequisite step before constructing any Onvexia screener query — it tells you exactly which fields are available for filtering, sorting, or analysis. Prefer it over guessing field names or consulting static documentation, since the live endpoint reflects the current schema. Especially useful when building dynamic query UIs, agent workflows that generate screener filters programmatically, or when onboarding to the Onvexia platform for the first time.

## Known failure modes

- Empty data array if no fields match the provided properties filter
- 402 Payment Required if x402 micropayment not included or insufficient
- Invalid properties parameter returns an error or empty result
- Rate limiting if too many requests are made in a short window
- Service unavailable if Onvexia backend is down, returning 5xx

## 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 available screener field definitions (data array) and metadata including a link to the full OpenAPI documentation. Each field entry describes a queryable or filterable dimension in the Onvexia blockchain asset screener, such as chain identifiers, supply metrics, address labels, or document-derived signals.

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

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/onvexia-screener-fields-catalog-66a1fa3f/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)