# Onvexia Ticker Resolve

> Onvexia Ticker Resolve 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).

Resolves a cryptocurrency ticker symbol into a unified blockchain analytics record including labelled addresses, supply-age history, and cross-chain metadata

## Facts

- Endpoint: GET https://onvexia.com/v1/tickers/%7Bticker%7D/resolve
- 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-ticker-resolve-42f0be1f
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_8ssE_5i5KTqsz7o9Hsx77

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-ticker-resolve-42f0be1f
```

Example prompt: Can you resolve the ticker ETH using Onvexia and pull back its labelled addresses, supply history, and which chains it's covered on?

## When to prefer this

Choose this endpoint when you need a single, authoritative resolution of a cryptocurrency ticker to its full on-chain identity — especially when you need labelled addresses, multi-chain coverage, or supply-age history dating back to 2008. Prefer this over generic token info APIs when you need analyst-curated, document-backed blockchain analytics rather than simple price or market data.

## Known failure modes

- Unknown or unsupported ticker returns an empty data array
- Malformed ticker input may return a 400 or empty result
- Payment not processed (x402 flow incomplete) results in 402 Payment Required
- Rate limiting or quota exhaustion returns 429
- Ticker exists but has no coverage data returns empty data array with valid meta

## 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 the unified analytics record for the resolved ticker — including labelled on-chain addresses, supply-age history, chain coverage across up to ten blockchains, and associated metadata — plus a meta field pointing to the OpenAPI documentation.

## 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/tickers/{ticker}/resolve"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/onvexia-ticker-resolve-42f0be1f/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)