# Onvexia Watchlist Address Events

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

Retrieves blockchain events associated with a specific watched address from Onvexia's analytics platform

## Facts

- Endpoint: GET https://onvexia.com/v1/watchlists/addresses/%7Bid%7D/events
- 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-watchlist-address-events-726c7da8
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_V6UlrX8hkTeBe-09joF7f

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-address-events-726c7da8
```

Example prompt: Pull the latest on-chain events for the address I've been watching — its watchlist ID is addr_7f3a92 — and tell me if there's been any unusual activity.

## When to prefer this

Choose this endpoint when you need to retrieve historical or recent on-chain events for a specific address that has already been added to a watchlist, particularly when you want Onvexia's labelled address context and multi-chain analytics fused with the event stream. Prefer this over raw blockchain node queries when enriched, pre-labelled event data is needed.

## Known failure modes

- Invalid or non-existent watchlist address ID returns empty data array
- Payment failure (402) if x402 micropayment of $0.001 USDC is not included
- Unauthorized access if the watchlist address belongs to another account
- Rate limiting if too many requests are made in quick succession
- Malformed ID path parameter returns 400 or empty result

## 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 of blockchain events associated with the specified watchlist address (transactions, transfers, contract interactions, etc.) and a 'meta' object containing documentation links and the endpoint path. Events leverage Onvexia's labelled address data and multi-chain coverage.

## 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/{id}/events"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/onvexia-watchlist-address-events-726c7da8/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)