# Onvexia Watchlist Addresses Coverage

> Onvexia Watchlist Addresses Coverage 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 coverage metadata for a watchlist of blockchain addresses, indicating which addresses have analytics data available across Onvexia's multi-chain dataset.

## Facts

- Endpoint: GET https://onvexia.com/v1/watchlists/addresses/coverage
- 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-watchlist-addresses-coverage-3bd32b63
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Pm4oQF_PxQLLSmvaJedlm

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-watchlist-addresses-coverage-3bd32b63
```

Example prompt: Can you check which of the addresses in my Onvexia watchlist actually have analytics coverage — I want to know before I pull deeper on-chain data on them?

## When to prefer this

Choose this endpoint when you need to quickly assess whether a set of blockchain addresses in your watchlist have corresponding analytics coverage in Onvexia's dataset before committing to deeper queries. It is ideal as a pre-flight check before running heavier analytics calls, and is most useful when working with multiple chains or large address sets where coverage gaps are expected.

## Known failure modes

- Empty data array returned if no addresses in watchlist have coverage
- Malformed or missing 'properties' query parameter may return an error or empty result
- Payment not processed (x402 flow failure) results in 402 response before data is returned
- Address not found in Onvexia's labelled dataset returns no coverage entry
- Rate limiting or invalid API credentials result in 4xx errors

## 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

Returns a JSON object with a 'data' array containing coverage records for the queried addresses, and a 'meta' object pointing to the full OpenAPI documentation. The data array indicates which watchlisted addresses have analytics coverage within Onvexia's dataset spanning ten chains and historical data back to 2008.

## 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/watchlists/addresses/coverage"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/onvexia-watchlist-addresses-coverage-3bd32b63/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)