# Onvexia Alert Deliveries

> Onvexia Alert Deliveries 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).

Retrieves the delivery history and status records for a specific blockchain analytics alert by its ID

## Facts

- Endpoint: GET https://onvexia.com/v1/alerts/%7Bid%7D/deliveries
- 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-alert-deliveries-5a5f5e32
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_uME6AzScQpchNeNju-VNM

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-deliveries-5a5f5e32
```

Example prompt: Pull the delivery history for my Onvexia alert with ID alert_12345 — I want to see every time it fired and whether the notifications were successfully sent.

## When to prefer this

Use this endpoint when you need to audit, debug, or verify the notification delivery history for a specific named alert ID on the Onvexia platform. It is the appropriate choice when you already have an alert configured and want to inspect its firing and delivery records rather than create new alerts or query raw blockchain data directly.

## Known failure modes

- Invalid or non-existent alert ID returns an empty data array or 404 error
- Malformed request body due to loose input schema may result in unexpected behavior
- Alert with no deliveries returns an empty data array
- Authentication or payment failure (x402) returns a 402 Payment Required response
- Rate limiting may return a 429 error for excessive calls

## 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 containing a data array of delivery records for the specified alert, each entry capturing delivery metadata such as timestamps, delivery status, and destination details, plus a meta object with documentation and endpoint references.

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

## More

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