# Onvexia Asset Revisions

> Onvexia Asset Revisions 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 historical revision log of fused blockchain analytics readings for a specific crypto asset symbol

## Facts

- Endpoint: GET https://onvexia.com/v1/assets/%7Bsymbol%7D/revisions
- 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-asset-revisions-58c7bede
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_vG_qKKLhRy4PKPpFmF_bH

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-revisions-58c7bede
```

Example prompt: Can you pull up the full revision history for ETH on Onvexia — I want to see every time their fused analytics reading was updated, including supply-age and labeled address changes?

## When to prefer this

Use this endpoint when you need to audit the provenance and change history of Onvexia's analytics data for a specific crypto asset — for example, to verify data freshness, trace when a fused reading last changed, or understand how labeled addresses or supply-age data evolved over time. Prefer it over a general asset lookup endpoint when historical versioning and data lineage matter, not just the current reading.

## Known failure modes

- Unknown asset symbol returns an empty data array rather than an error
- Malformed symbol path parameter may return a 404 or empty result
- Sparse input schema makes it unclear which query parameters are supported, potentially returning all revisions with no filtering
- Service may return empty data array for assets with no revision history yet
- Payment failure (x402) will block the response before any data is returned

## 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 array of revision records for the specified asset symbol, each entry representing a historical version of Onvexia's fused analytics reading. Entries may include timestamps, revision identifiers, and metadata about what changed (e.g. updated document analysis, label changes, supply-age history). The meta field provides API documentation links and the endpoint path.

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

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/onvexia-asset-revisions-58c7bede/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)