# Onvexia Alert History

> Onvexia Alert History is a paid API for AI agents from onvexia.com, paid per call via x402, $0.01/call, status unknown (last checked 2026-09-17).

Retrieves the historical trigger log for a specific blockchain analytics alert by its ID

## Facts

- Endpoint: GET https://onvexia.com/v1/alerts/%7Bid%7D/history
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-17
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/onvexia-alert-history-a1030e76
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_SlAziMJoVA4DcGH6vPJCA

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-alert-history-a1030e76
```

Example prompt: Pull up the full trigger history for my Onvexia alert ID abc-123 — I want to see every time it fired and what triggered it.

## When to prefer this

Use this endpoint when you need to audit, review, or debug the historical trigger log of a specific pre-configured Onvexia blockchain alert. It is the right choice when you already have an alert ID and want to understand when and why that alert fired in the past, rather than querying live asset data or creating new alerts.

## Known failure modes

- Alert ID not found — returns empty data array or 404-equivalent
- Malformed or missing alert ID parameter — request fails with validation error
- Payment not processed — x402 payment required before data is returned
- Alert has no history yet — returns empty data array with valid meta
- Rate limit or access restriction — endpoint returns error if quota exceeded

## 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 historical trigger records for the specified alert, and a 'meta' object with documentation links and the endpoint path. Each record in the data array represents a past alert event including timestamps and trigger context.

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

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/onvexia-alert-history-a1030e76/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)