# Onvexia Watchlist Addresses

> Onvexia Watchlist Addresses 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).

Retrieve a watchlist of labelled blockchain addresses with analytics metadata across multiple chains

## Facts

- Endpoint: GET https://onvexia.com/v1/watchlists/addresses
- 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-2e047843
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_hZYBv6t3iyTpagx-0l4Pf

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-2e047843
```

Example prompt: Pull all the addresses from my Onvexia watchlist — I want to see the labelled entries across chains so I can review which wallets I'm currently tracking.

## When to prefer this

Choose this endpoint when you need to retrieve a curated, persistent list of tracked or labelled blockchain addresses from Onvexia's watchlist system, especially for compliance monitoring, DeFi wallet surveillance, or cross-chain address auditing. Prefer it over general blockchain explorers when you want pre-labelled, analytically enriched address records tied to a personal or organisational watchlist.

## Known failure modes

- Empty data array if no addresses have been added to the watchlist
- Authentication failure if x402 payment is not processed correctly
- Invalid filter properties returning no results
- Rate limiting if called excessively without payment
- Malformed properties parameter returning 400 error

## 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 watchlisted blockchain addresses and their associated metadata (labels, chain info, properties), plus a meta object with documentation URL and endpoint path reference.

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

## More

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